- rssac-caucus - lists.icann.org

Curious difference in glue TTL for root servers
by Mukund Sivaraman June 19, 2020

June 19, 2020

There's a difference in the TTL of glue records returned in a priming query from different root servers. There's nothing wrong with a nameserver lowering the TTL in a response [RFC2181], but it's an observable difference in behavior. Perhaps some DNS implementation is clamping the glue to TTLs of the NS records. Both TTLs are observed on multiple root server letters respectively. [muks@jurassic ~]$ dig +nord +short @l.root-servers.net root-servers.net soa a.root-servers.net. nstld.verisign-grs.com. 2020060800 14400 7200 1209600 3600000 [muks@jurassic ~]$ dig +nord @l.root-servers.net . ns ; <<>> DiG 1.1.1.20200608151533.e8a2352e96 <<>> +nord @l.root-servers.net . ns ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26630 ;; flags: qr aa; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 27 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 518400 IN NS a.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS d.root-servers.net. . 518400 IN NS e.root-servers.net. . 518400 IN NS f.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS h.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS m.root-servers.net. ;; ADDITIONAL SECTION: a.root-servers.net. 518400 IN A 198.41.0.4 b.root-servers.net. 518400 IN A 199.9.14.201 c.root-servers.net. 518400 IN A 192.33.4.12 d.root-servers.net. 518400 IN A 199.7.91.13 e.root-servers.net. 518400 IN A 192.203.230.10 f.root-servers.net. 518400 IN A 192.5.5.241 g.root-servers.net. 518400 IN A 192.112.36.4 h.root-servers.net. 518400 IN A 198.97.190.53 i.root-servers.net. 518400 IN A 192.36.148.17 j.root-servers.net. 518400 IN A 192.58.128.30 k.root-servers.net. 518400 IN A 193.0.14.129 l.root-servers.net. 518400 IN A 199.7.83.42 m.root-servers.net. 518400 IN A 202.12.27.33 a.root-servers.net. 518400 IN AAAA 2001:503:ba3e::2:30 b.root-servers.net. 518400 IN AAAA 2001:500:200::b c.root-servers.net. 518400 IN AAAA 2001:500:2::c d.root-servers.net. 518400 IN AAAA 2001:500:2d::d e.root-servers.net. 518400 IN AAAA 2001:500:a8::e f.root-servers.net. 518400 IN AAAA 2001:500:2f::f g.root-servers.net. 518400 IN AAAA 2001:500:12::d0d h.root-servers.net. 518400 IN AAAA 2001:500:1::53 i.root-servers.net. 518400 IN AAAA 2001:7fe::53 j.root-servers.net. 518400 IN AAAA 2001:503:c27::2:30 k.root-servers.net. 518400 IN AAAA 2001:7fd::1 l.root-servers.net. 518400 IN AAAA 2001:500:9f::42 m.root-servers.net. 518400 IN AAAA 2001:dc3::35 ;; Query time: 33 msec ;; SERVER: 199.7.83.42#53(199.7.83.42) ;; WHEN: Fri Jun 19 03:52:09 IST 2020 ;; MSG SIZE rcvd: 811 [muks@jurassic ~]$ dig +nord +short @m.root-servers.net root-servers.net soa a.root-servers.net. nstld.verisign-grs.com. 2020060800 14400 7200 1209600 3600000 [muks@jurassic ~]$ dig +nord @m.root-servers.net . ns ; <<>> DiG 1.1.1.20200608151533.e8a2352e96 <<>> +nord @m.root-servers.net . ns ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45391 ;; flags: qr aa; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 27 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 518400 IN NS d.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS f.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS m.root-servers.net. . 518400 IN NS a.root-servers.net. . 518400 IN NS e.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS h.root-servers.net. ;; ADDITIONAL SECTION: a.root-servers.net. 3600000 IN A 198.41.0.4 b.root-servers.net. 3600000 IN A 199.9.14.201 c.root-servers.net. 3600000 IN A 192.33.4.12 d.root-servers.net. 3600000 IN A 199.7.91.13 e.root-servers.net. 3600000 IN A 192.203.230.10 f.root-servers.net. 3600000 IN A 192.5.5.241 g.root-servers.net. 3600000 IN A 192.112.36.4 h.root-servers.net. 3600000 IN A 198.97.190.53 i.root-servers.net. 3600000 IN A 192.36.148.17 j.root-servers.net. 3600000 IN A 192.58.128.30 k.root-servers.net. 3600000 IN A 193.0.14.129 l.root-servers.net. 3600000 IN A 199.7.83.42 m.root-servers.net. 3600000 IN A 202.12.27.33 a.root-servers.net. 3600000 IN AAAA 2001:503:ba3e::2:30 b.root-servers.net. 3600000 IN AAAA 2001:500:200::b c.root-servers.net. 3600000 IN AAAA 2001:500:2::c d.root-servers.net. 3600000 IN AAAA 2001:500:2d::d e.root-servers.net. 3600000 IN AAAA 2001:500:a8::e f.root-servers.net. 3600000 IN AAAA 2001:500:2f::f g.root-servers.net. 3600000 IN AAAA 2001:500:12::d0d h.root-servers.net. 3600000 IN AAAA 2001:500:1::53 i.root-servers.net. 3600000 IN AAAA 2001:7fe::53 j.root-servers.net. 3600000 IN AAAA 2001:503:c27::2:30 k.root-servers.net. 3600000 IN AAAA 2001:7fd::1 l.root-servers.net. 3600000 IN AAAA 2001:500:9f::42 m.root-servers.net. 3600000 IN AAAA 2001:dc3::35 ;; Query time: 104 msec ;; SERVER: 202.12.27.33#53(202.12.27.33) ;; WHEN: Fri Jun 19 03:51:46 IST 2020 ;; MSG SIZE rcvd: 811 [muks@jurassic ~]$ Mukund

5 9

Translations of the RSSAC FAQ Posted
by Andrew McConachie June 19, 2020

June 19, 2020

Dear RSSAC Caucus Members, The RSSAC has published Arabic, Chinese, French, Russian, and Spanish translations of the RSSAC FAQ. They’re downloadable from the main RSSAC page. <https://www.icann.org/groups/rssac> Thanks, Andrew

2 1

Translations of RSSAC050 Published
by Andrew McConachie June 19, 2020

June 19, 2020

Dear RSSAC Caucus Members, The RSSAC has published Arabic, Chinese, French, Russian, and Spanish translations of RSSAC050. They’re downloadable from the RSSAC publications page. <https://www.icann.org/groups/rssac/documents> Thanks, Andrew

2 1

Nomination Period: RSSAC Liaison to the ICANN Nominating Committee
by Ozan Sahin June 18, 2020

June 18, 2020

Dear RSSAC Caucus Members, It is time to begin the selection process for the Outgoing RSSAC Liaison to the 2021 ICANN Nominating Committee. The role is a one-year term beginning at the conclusion of the Annual General Meeting to be held during ICANN69. Please refer to this page<https://www.icann.org/nomcom2020> for more information about the Nominating Committee. I have also copied below the relevant sections from “RSSAC000v4: Operational Procedures” for your reference. With this notice, a one-month nomination period via this distribution list is now open. Nominations or self-nominations will be accepted and require a second. Nominees must then accept or decline their nomination and may provide a statement with more context for their decision. The nomination period will close at 23:59 UTC on 21 June. The RSSAC will then consider the slate of candidates at its 7 July teleconference. As you may recall, the RSSAC appointed Amir Qayyum to this role in 2019. Amir’s term will expire by ICANN69, the Annual General Meeting. Amir is eligible for re-appointment as per the RSSAC Operational Procedures. The RSSAC Leadership appreciates your consideration. Please do not hesitate to contact the RSSAC Chair and Vice Chair or support staff with any questions or concerns. Best, Ozan Sahin on behalf of Fred Baker, RSSAC Chair Brad Verd, RSSAC Vice Chair 1.2.8.6 Outgoing RSSAC Liaison to the ICANN Nominating Committee The outgoing RSSAC Liaison to the ICANN Nominating Committee is specified in the ICANN Bylaws.3 The term for the outgoing RSSAC Liaison to the ICANN Nominating Committee shall be one year. A person may only serve for three consecutive terms. The eligibility status for a previous liaison is reset one year after having stepped down. The RSSAC must elect the outgoing RSSAC Liaison to the ICANN Nominating Committee according to the outgoing RSSAC liaisons election procedure (Section 1.2.8.9) from the members of the RSSAC Caucus. The outgoing RSSAC Liaison to the ICANN Nominating Committee acts as a conduit between the RSSAC and the ICANN Nominating Committee reporting on matters that need to be coordinated or communicated between the two bodies. The role requires discretion, management skills, and considerable time commitment. 1.2.8.9 Outgoing RSSAC Liaisons Election Procedure One month prior to each election, qualified nominees will be accepted for the outgoing liaison position and announced on the RSSAC distribution list. During the meeting that includes election of an outgoing liaison position on its announced agenda, additional nominations will be accepted, and all nominees will indicate their intentions: to accept or to decline their nomination. In the event that only one candidate is standing for election, the RSSAC may elect the new outgoing liaison by acclamation. In the event that two or more candidates are standing for election, the RSSAC Chair will call for a vote. Members will indicate their selection. A simple majority (half plus one) of the voting members will establish the new liaison. In the event a simple majority is not achieved due to having more than two nominees, the nominee with the least number of votes is eliminated and the voting is repeated with the reduced slate of names. The process is repeated until a nominee achieves a simple majority. In the event of a tie, a runoff election will occur with members indicating their selection. In the event of a second tie, the floor will be opened for discussion followed by a new vote with the simple majority designating the new liaison. The RSSAC Chair will forward the name of the outgoing liaison-elect to the reciprocating body. If a vacancy exists in an outgoing liaison role, the RSSAC will elect a new outgoing liaison through this process.

4 4

RSSAC Caucus Meeting in July 2020
by Ozan Sahin June 18, 2020

June 18, 2020

Dear RSSAC Caucus members, RSSAC Caucus typically meets at ICANN Annual General Meetings and even-numbered IETF meetings. Given that IETF 108 will be held remotely, the next RSSAC Caucus meeting will be held on either Monday, 20 July or Tuesday, 21 July. Please indicate your availability for the next RSSAC Caucus meeting via this doodle poll by the close of business in your time zone on Thursday, 25 June: https://doodle.com/poll/fgendvhpa7ic2uqr Support staff will then send out calendar invitations for this meeting. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0

Publication of RSSAC051
by Andrew McConachie June 8, 2020

June 8, 2020

Dear RSSAC Caucus Members, The RSSAC has recently published RSSAC051: RSSAC Statement on Draft Public Technical Identifiers (PTI) FY21-24 Strategic Plan. RSSAC051 can be found here. <https://www.icann.org/en/system/files/files/rssac-051-02jun20-en.pdf> RSSAC051 has also been submitted to the ICANN Public Comment Proceeding on this topic. Thanks, Andrew

1 0

RSSAC Caucus Rogue RSO WP Teleconference #3 | Tuesday, 30 June | 13:00-14:00 UTC
by Ozan Sahin June 4, 2020

June 4, 2020

Ozan Sahin is inviting you to a scheduled Zoom meeting. Topic: RSSAC Caucus Rogue RSO WP Call #3 Time: Jun 30, 2020 01:00 PM Universal Time UTC Agenda: TBC Work Party Wiki Space: https://community.icann.org/x/IonsBw Join Zoom Meeting https://icann.zoom.us/j/95025748089 Meeting ID: 950 2574 8089 Password: 9Y#sFAj4hX One tap mobile +16699006833,,95025748089#,,1#,653521# US (San Jose) +13462487799,,95025748089#,,1#,653521# US (Houston) Dial by your location +1 669 900 6833 US (San Jose) +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 929 436 2866 US (New York) 888 788 0099 US Toll-free 877 853 5247 US Toll-free Meeting ID: 950 2574 8089 Password: 653521 Find your local number: https://icann.zoom.us/u/abO46Jbf4

1 0

RSSAC Caucus Local Perspective Tool WP Teleconference #3 | Monday, 29 June | 15:00-16:00 UTC
by Ozan Sahin June 4, 2020

June 4, 2020

Ozan Sahin is inviting you to a scheduled Zoom meeting. Topic: RSSAC Caucus Local Perspective Tool WP Call #3 Time: Jun 29, 2020 03:00 PM Universal Time UTC Agenda: TBC Work Party Wiki Space: https://community.icann.org/x/gInsBw Join Zoom Meeting https://icann.zoom.us/j/99674486025 Meeting ID: 996 7448 6025 Password: 8Y&HnhZ&p* One tap mobile +16699006833,,99674486025#,,1#,729929# US (San Jose) +13462487799,,99674486025#,,1#,729929# US (Houston) Dial by your location +1 669 900 6833 US (San Jose) +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 929 436 2866 US (New York) 888 788 0099 US Toll-free 877 853 5247 US Toll-free Meeting ID: 996 7448 6025 Password: 729929 Find your local number: https://icann.zoom.us/u/aAKn4I3QK

1 0

RSSAC Meeting Minutes | 5 May 2020 Meeting
by Ozan Sahin June 3, 2020

June 3, 2020

Dear RSSAC Caucus Members, The meeting minutes from 5 May 2020 RSSAC Meeting have been approved during the RSSAC Meeting on Tuesday, 2 June 2020. The meeting minutes have been posted on the RSSAC Meetings page https://www.icann.org/resources/pages/rssac-meetings-2014-05-06-en. You may also find the meeting minutes attached to this note. Best, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0

Pre-ICANN68 Policy Report now available!
by Ozan Sahin June 2, 2020

June 2, 2020

Dear RSSAC Caucus members, ICANN Policy Development Support Team has published the Pre-ICANN68 Policy Report. If you are interested to read about the policy development and advice activities of various Supporting Organizations and Advisory Committees the report is available here: http://go.icann.org/pre68 Best regards, Ozan Sahin Policy Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +90 212 999 6218 Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 0