- rssac-caucus - lists.icann.org

[rssac-caucus] A DNSSEC issue during KSK rollover
by Davey Song Oct. 26, 2016

Oct. 26, 2016

Hi folks, For your information, there is a article I put down to describe the issue we found during Yeti KSK rollover. Hope it help. http://yeti-dns.org/yeti/blog/2016/10/26/A-DNSSEC-issue-during-Yeti-KSK-rol… Best regards, Davey

1 0

[rssac-caucus] RSSAC Caucus Meeting at ICANN 57
by Andrew Mcconachie Oct. 20, 2016

Oct. 20, 2016

Dear RSSAC Caucus Members, Attached please find the draft agenda for the RSSAC Caucus meeting at ICANN 57. The meeting will be held on November 6, in Hall 5 at 15:15 - 16:45 IST(local time), 9:45 - 21:15 UTC. Please send in any agenda items you would like to see discussed. A separate meeting invite email will be sent closer to the date. Thanks, Andrew

1 0

[rssac-caucus] NSID support on the root-servers
by Ondřej Surý Oct. 18, 2016

Oct. 18, 2016

Hi, I just did a quick test (after seeing yet another "we are using CH TXT") for NSID support at root level and only 6 out of 13 of letters did support NSID. Is this something worth enough for RSSAC to look into? Ideally it would be great to have NSID support at all root-server instances. Cheers, -- Ondřej Surý -- Technical Fellow -------------------------------------------- CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC Milesovska 5, 130 00 Praha 3, Czech Republic mailto:ondrej.sury@nic.cz https://nic.cz/ --------------------------------------------

7 15

[rssac-caucus] REMINDER: CALL FOR VOLUNTEERS: new Caucus Work Party on anycast
by Kathy Schnitt Oct. 17, 2016

Oct. 17, 2016

Dear RSSAC Caucus, REMINDER: The RSSAC wishes to investigate best practices to optimize the distribution of root server instances in order to maximize root service resiliency, and to reduce the Round-Trip Time (RTT) between recursive servers and root servers. It requests Kaveh Ranjbar to lead a Caucus work party to produce a report, with adherence to RSSAC Caucus procedures. The work party is asked to consider a number of issues related to the distribution of anycast instances of the root name service, including: * Given the state of current internet technology, what is the maximum latency a relying party should experience when transacting with the DNS root service as opposed to with a single "root server?" * Will adding more instances in more topologically diverse locations make the system more resilient to Denial Of Service (DOS) attacks? * If root operators were to coordinate their deployments of anycast instances, what considerations should be contemplated? * Are there any regional or global technological risks (or benefits) if only a subset of operators (versus all or the majority of root operators) deploy anycast instances? REMINDER: If you are interested in this topic and would like to join this work party, please email Kathy Schnitt kathy.schnitt(a)icann.org<mailto:kathy.schnitt@icann.org> by close of business 19 October 2016. A list of interested parties I have so far are Marc Blanchet, Ondrej Sury, Suresh Krishnaswamy, Shane Kerr, Abby Pan and Ray Bellis. Best regards, Kathy and Steve

1 0

[rssac-caucus] FOR REVIEW: Elements of Potential Root Operators v3
by Andrew Mcconachie Oct. 14, 2016

Oct. 14, 2016

Dear RSSAC Caucus, Please find Key Technical Elements of Potential Root Operators version 3. Redline and clean versions are attached. Duane and I worked to include the feedback we've received on this mailing list into this version. Changes since version 2.2: - Incorporated Warren’s suggestions on wording in the Introduction, and the change of 3.4.8’s Title to Access Segregation. - Lowercased all instances of RFC 2119 language and removed the paragraph on RFC 2119 in the Introduction. - Deleted paragragh in section 3.3.7 on RPKI. Thanks, Andrew

1 0

[rssac-caucus] CALL FOR VOLUNTEERS: new Caucus Work Party on anycast
by Steve Sheng Oct. 12, 2016

Oct. 12, 2016

Dear RSSAC Caucus, The RSSAC wishes to investigate best practices to optimize the distribution of root server instances in order to maximize root service resiliency, and to reduce the Round-Trip Time (RTT) between recursive servers and root servers. It requests Kaveh Ranjbar to lead a Caucus work party to produce a report, with adherence to RSSAC Caucus procedures. The work party is asked to consider a number of issues related to the distribution of anycast instances of the root name service, including: * Given the state of current internet technology, what is the maximum latency a relying party should experience when transacting with the DNS root service as opposed to with a single “root server?” * Will adding more instances in more topologically diverse locations make the system more resilient to Denial Of Service (DOS) attacks? * If root operators were to coordinate their deployments of anycast instances, what considerations should be contemplated? * Are there any regional or global technological risks (or benefits) if only a subset of operators (versus all or the majority of root operators) deploy anycast instances? If you are interested in this topic and would like to join this work party, please email Kathy Schnitt kathy.schnitt(a)icann.org<mailto:kathy.schnitt@icann.org> by close of business 19 October 2016. Best Steve

1 0

[rssac-caucus] Reminders
by Carlos Reyes Oct. 12, 2016

Oct. 12, 2016

Dear RSSAC Caucus, The minutes from the 1 September RSSAC meeting have been published: Webpage | File The RSSAC Caucus will meet on Sunday, 6 November, 15:15-16:45 India Standard Time, in Hall 5 at the Hyderabad International Convention Center during ICANN57. The agenda will be similar to the recent meeting at IETF96 in Berlin, Germany, but agenda items are certainly welcome. Please propose agenda items on the list. In addition to ICANN Annual General Meetings (“C” meetings in the new rotation, the third/last meeting of every year), the RSSAC Caucus will continue to meet at every other IETF meeting. The next RSSAC Caucus meeting will be in March 2017 at IETF98 in Chicago, USA. Thank you, Carlos Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006

1 0

[rssac-caucus] Pre-ICANN 57 Policy Update Webinar Announcement
by Kathy Schnitt Oct. 5, 2016

Oct. 5, 2016

Dear RSSAC, The following announcement may be of interest. Best regards, Kathy Kathy Schnitt, Secretariat Services Coordinator for RSSAC and SSAC https://www.icann.org/news/announcement-2016-10-05-en Please RSVP via this form<https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> by 14 October 2016. Remote participation details will be sent the week of 17 October 2016. The ICANN Policy Development Support Team will provide a Policy Update Webinar on Thursday, 20 October 2016 at 10:00 UTC and 19:00 UTC, in preparation for the upcoming ICANN Annual General Meeting in Hyderabad. The purpose of the webinar is to summarize policy activities across the ICANNpolicy development community and briefing the community on the Cross-Community sessions taking place in Hyderabad. Cross-Community Sessions Briefings: * New generic Top Level Domain Auction Proceeds Drafting Team * Cross-Community Working Group for Framework of Cross-Community Working Group Principles * Cross-Community Working Group on Use of Country/Territory Names as Top Level Domains Community Engagement Team Update: * Community Recognition at ICANN57 and Multistakeholder Ethos Award 2017 Process Launch * Supporting Organizations/Advisory Committees Work Effort Inventory/Snapshot Update * Policy Staff Support in Community Charter Amendment Processes Supporting Organizations & Advisory Committee Updates: * Address Supporting Organization (ASO) and Regional Internet Registries (RIR) Policy Development * Country Code Names Supporting Organization (ccNSO) Update * Generic Names Supporting Organization (GNSO) * New generic Top Level Domain (gTLD) Subsequent Procedures Policy Development Process (PDP) * Review of all Rights Protection Mechanisms in all Generic Top Level Domains (gTLDs) Policy Development Process (PDP) * Next-Generation Generic Top Level Domain (gTLD) Registration Directory Services to Replace WHOIS Policy Development Process (PDP) * IGO/INGO Access to Curative Rights Mechanisms Policy Development Process (PDP) * At-Large Advisory Committee (ALAC) and At-Large Community Update * Government Advisory Committee (GAC) * Adaptation of Government Advisory Committee (GAC) Processes to the new ICANN Bylaws * Government Advisory Committee Vice-Chairs Elections taking place in Hyderabad * Capacity Building Session for the Asia Pacific Region organized by the Government Advisory Committee (GAC) Working Group for Underserved Regions * The Government Advisory Committee developing further input for ongoing Policy Development Processes on Registration Directory Services and Future new generic Top Level Domains (gTLDs) * Root Server System Advisory Committee (RSSAC) Update * Security and Stability Advisory Committee (SSAC) Update The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs for 90 minutes and will be run in English. The webinar will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may be submitted using the chat function in Adobe Connect. Recordings of the webinars will be made available here<https://www.icann.org/resources/pages/presentations-2012-08-27-en>. The Policy Development Support Team is always available to answer any questions via email at policyinfo(a)icann.org<mailto:policyinfo@icann.org>. Please RSVP via this form<https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> by 14 October 2016. Remote participation details will be sent the week of 17 October 2016.

1 0

[rssac-caucus] FOR REVIEW: Elements of Potential Root Operators v2.
by Andrew Mcconachie Oct. 5, 2016

Oct. 5, 2016

Dear RSSAC Caucus, On behalf of the work party for RSSAC Workshop 2 Statement 4, attached please find Key Technical Elements of Potential Root Operators version 2.2. Redline and clean versions in both pdf and MS Word are attached. Duane and I worked to include the feedback we received from the two conference calls we had on this document. Three things that we feel should be highlighted: 1. Section 3.3.7(Address Registries) has been largely rewritten. 2. Section 3.6.4(Openness and Participation) has been removed. A single sentence referencing DNS-OARC and DITL collection has been added to section 3.6.1(Data & Measurement). 3. We would like to request more feedback on the usage of RFC 2119 language(e.g., SHOULD, MUST, MAY). Please discuss on the list. Thanks, Andrew

10 11

[rssac-caucus] FW: Call for Participation- Seoul Yeti DNS Workshop- 12th November
by songlinjian＠gmail.com Sept. 29, 2016

Sept. 29, 2016

Hi folks , I would like to forward this CFP to this mailing list. http://yeti-dns.org/yeti/blog/2016/09/26/CFP-Yeti-DNS-Workshop.html --Davey songlinjian(a)gmail.com

1 0