Hi Andrew,

I have reviewed the FAQ and would like to propose the following updates and additions for consideration:

Questions to Consider Adding:

1. ZONEMD Implementation Progress:

   • Question: "What is the current status of ZONEMD implementation across root server operations?"
   • Reason: ZONEMD is a key RSSAC focus area, and including an FAQ ensures community awareness of progress and timelines.
   • Draft Answer:
     ZONEMD (Zone Message Digest) is a new technology designed to enhance the integrity verification of DNS zone data. While ZONEMD is not yet fully implemented across all root server operations, RSSAC continues to monitor its development and adoption. Current efforts include testing ZONEMD in real-world scenarios, analyzing its performance impact, and addressing operational challenges. RSSAC is also working with the community to ensure compatibility and seamless integration into existing systems. Updates on ZONEMD implementation are shared through RSSAC publications and ICANN public meetings.  

2. RSSAC Caucus Contributions:

   • Question: "How does the RSSAC Caucus contribute to the development of RSSAC publications and recommendations?"
   • Reason: Provides clarity on the Caucus’s role, encouraging greater participation.

   • Draft Answer:
     The RSSAC Caucus is a group of volunteer subject matter experts who provide advice, draft documents, and offer technical input to RSSAC. Members of the Caucus work collaboratively on publications, such as advisories, reports, and technical assessments. These contributions are integral to RSSAC's mission of ensuring the stability and security of the root server system. The Caucus meets regularly to discuss ongoing projects and provide input on topics such as DNS technology, root server operations, and emerging threats. Interested community members can apply to join the Caucus and contribute to this important work.

3. Emerging Threats to Root Server Operations:

   • Question: "What are the primary emerging threats to root server operations, and how is RSSAC addressing them?"
   • Reason: Addresses growing concerns in cybersecurity and resilience, demonstrating RSSAC’s proactive stance.
   • Draft Answer:
     Emerging threats to root server operations include Distributed Denial-of-Service (DDoS) attacks, advances in quantum computing, and the need to adapt to evolving internet protocols. Additionally, geopolitical tensions and regulatory changes may impact operations. RSSAC actively monitors these threats and develops recommendations to mitigate their risks. For example, RSSAC supports the adoption of DNSSEC and other cryptographic measures to protect the integrity of DNS data. Collaboration with stakeholders, ongoing research, and advisory publications are key components of RSSAC’s approach to addressing these challenges.  

4. Community Involvement:

   • Question: "How can individuals or organizations provide feedback or engage with RSSAC?"
   • Reason: Encourages ICANN community members to participate and provide input, aligning with RSSAC’s transparency goals.

   • Draft Answer:
     RSSAC encourages feedback and engagement from the broader ICANN community. Individuals and organizations can participate in public meetings, provide comments on draft publications during public consultation periods, or join the RSSAC Caucus as subject matter experts. Regular updates on RSSAC activities are available on the ICANN website, and community members can contact RSSAC directly through the ICANN support team. This open engagement process ensures that RSSAC's work remains inclusive and responsive to stakeholder needs.

5. RSSAC’s Role in ICANN Policy Development:

   • Question: "What is RSSAC’s role in ICANN’s overall policy development process?"
   • Reason: Clarifies the scope and influence of RSSAC in broader ICANN processes.
   • Draft Answer:
     RSSAC serves as an advisory body within ICANN, focusing specifically on issues related to the operational stability, reliability, and security of the root server system. While RSSAC does not directly develop ICANN policies, it provides technical expertise and recommendations to inform policy discussions. For example, RSSAC offers advice on the implementation of new technologies and their potential impact on the root server system. These contributions help ensure that ICANN’s policies align with best practices for DNS operations and security.  

Answers to Consider Changing:

1. Technical Details:

   • Existing Answers: Answers that reference specific RFCs, technical processes (e.g., DNSSEC), or project statuses should be reviewed to ensure they reflect the latest updates.
   • Reason: RSSAC FAQs must remain authoritative and current, given the rapid evolution of DNS technologies.

2. Simplification of Language:

   • Existing Answers: Responses targeting non-technical audiences may need simplification to ensure accessibility.
   • Example: Break down complex concepts like DNSSEC, ZONEMD, or root server operations with plain-language summaries or diagrams.

3. Future Planning/Timelines:

   • Existing Answers: Update responses about ongoing or future initiatives (e.g., ZONEMD, root server system governance evolution).
   • Reason: Timelines may have shifted, or newer developments might need highlighting.

4. Clarifications:

• Existing Answers: Responses to questions about RSSAC’s relationship with other ICANN groups (e.g., SSAC, GNSO) should clarify boundaries and collaboration.
• Reason: Ensures accurate portrayal of RSSAC’s unique responsibilities within ICANN.