Page History
Work Products | Date | Update: 14December 2016 10:30 EST |
| |||||||
Administrative Items |
|
|
| |||||||
RSSAC Meetings | Ongoing | Last The most recent RSSAC Meeting teleconference was on May 07, 2015. Action items are:
01 December 2016. Open Action Items from This Meeting
Previous Teleconference(s)
Agenda Items:
|
| |||||||
RSSAC Caucus Meetings | Ongoing | Last RSSAC Caucus Meeting was on March 22, 2015 (IETF 92). Minutes and notes are prepared. ACTION Item(s): Liman and Tripti to provide feedback on how to handle the minutes and notes given that RSSAC caucus list is open.[Done]
|
| 06 November 2016 at ICANN 57 in Hyderabad, India. The next RSSAC Caucus Meeting is in Chicago, IL at IETF. |
| |||||
RSSAC at ICANN Meetings | Ongoing | The most recent RSSAC Meeting at ICANN was on 04 November 2016 in Hyderabad, India Action Items:
| RSSAC Mtgs at ICANN Mtgs | Ongoing | ICANN 53 is in Buenos Aires, Argentina: 21-25 June.
Status: Carlos and Kathy started planning for the RSSAC sessions, the feedback given by RSSAC Chairs are: 1) the number of meetings are good enough, 2) RSSAC meetings with external parties should be consolidated together into one block of time. [Ongoing] Action Items: |
| ||||
RSSAC Travel Support | Ongoing | For FY15FY17, RSSAC requested has 6 slots (2 co-chair + 3 chairs and 4 RSSAC members travel to each ) for ICANN meetings.
Action items: Carlos to check how other SO/ACs do with the traveler support Travel Support requests for ICANN58 are in the process. |
Update: April 29: Marc Blanchet reached out to Steve and Carlos asking whether there is funding for IAB liaison to RSSAC to travel to ICANN meetings. How should we respond? [Liman and Tripti to discuss] |
| ||||||
FY16 Special Budget Requests |
| FY16 Special Budget Requests – RSSAC IETF Meetings, RSSAC Workshop, RSSAC travel funding for ICANN meetings (2 co-chairs + 3 members).
Status: Tripti submitted the budget request to ICANN on 24 February 2015, waiting to hear back from ICANN. [Special requests granted]
|
| |||||||
RSSAC 2015 Workshop |
| CR to set up a planning phone call for the week of 18 May 2015. |
| |||||||
Public Comments/Input |
|
|
| |||||||
RSSAC Workshop 2016 | Open | THE date for the 2016 RSSAC Workshop will be on May 2,3,4 in Reston, VA.
| ||||||||
Public Comments/Input | Closed |
|
| |||||||
CCWG Proposal on Enhancing ICANN Accountability | Ongoing |
| CWG Proposal For IANA Stewardship Transition |
| The proposal is out for public comment on 23 April 2015. Suzanne raised in an email to RSSAC saying that RSSAC should provide comment to the proposal. LL to raise during RSSAC Teleconference on 7 May 2015
| |||||
Work Parties/Committees |
|
| ||||||||
Membership Committee | Ongoing | 2015 Caucus membership committee are: Paul Vixie, Tripti Sinha, and Kaveh Ranjbar. Staff support: Carlos Reyes.
Status: On 2 April, the Membership Committee submitted six candidates (Adiel Akplogan, Bobby Cates, Wes Hardaker, Keith Mitchell, Gerry Sneeringer, and William Sotomayor) for approval. The RSSAC approved these.
Action Items: 1) Tripti to follow up on the SOI of Karl Reuss. [Open] 2) Carlos / Kathy to publish the Caucus SOIs as well as update the ICANN website. [Done] 3) A communication to RSSAC is needed. [CR to notify Caucus] |
| Kaveh Ranjbar announced his intent to step down at ICANN55. Matt Weinberg will replace Kaveh. Jim Martin will remain on the Membership Committee (It is not required to be an RSSAC member to serve on the Membership Committee.) |
| |||||
Root Server System Naming Scheme | Ongoing | Shepherd: Suzanne Woolf Leader: John Bond Work Party held a meeting at IETF95. John Bond has replaced Joe Abley as work party leader. Work continues. 12/14/2016 - The work party produced final reports | ||||||||
Anycast Instances | New | Steve Sheng sent the updated statement of work for review by Daniel Karrenberg on 3/15/2016. ACTION ITEM: Daniel K to review and revise the updated statement of work. | ||||||||
History of Root Server System | Closed | 12/14/2016: The document is published. 3/16/2016: The caucus review has finished. The RSSAC shepherd group will revise the document. ACTION: Tripti to incorporate Ashley's input and revise the document. | ||||||||
RSSAC002 v3 | Closed. | The work party working on v3 of RSSAC002 continues to have meetings. On track for delivery by 1 June 2016 to the RSSAC. 6/6/2016 - The document is published. https://www.icann.org/en/system/files/files/rssac-002-measurements-root-06jun16-en.pdf | ||||||||
Publications | ||||||||||
RSSAC000 v2 | Ongoing | Kevin Jones is leading an effort to revise the RSSAC operational procedures. Carlos Reyes is providing staff support. | ||||||||
RSSAC001 v1 | Closed | RSSAC001 has been approved by RSSAC | RSSAC 001 |
| RSSAC001 is approved by SSAC and available at: https://www.icann.org/en/system/files/files/rssac-001-draft-20nov14-en.pdf. | It is waiting on draft-iab-2870bis-02 to be published together.
| ||||
Root Zone TTL |
| Work Party members: Duane Wessels (leader), Warren Kumari, Jaap Akkerhuis, Shumon Huque, Brian Dickson, John Bond, Joe Abley, Alejandro Acosta, Akira Kato and Matt Thomas. Staff Support: Steve Sheng.
The Work Party is meeting biweekly, the next meeting is April 23, 3:00pm EDT.
| ||||||||
Evolution of Root Server System |
| The RSSAC will focus this topic in its annual workshop. To prepare for the workshop, a background document to be produced on historical information about root server operational transitions.
Action: Lars-Johan Liman to encourage RSSAC members to send historical information about root server operational transitions to Steve Sheng. Also specify what additional historical information needs to be shared.
|
| |||||||
IANA Stewardship Transition |
|
|
| |||||||
PROPOSED: Signing (or not) the root-servers.net zone |
| Action item: Wes Hardaker and Steve Sheng to work on a statement of work. |
| |||||||
Implementation Follow up |
| |||||||||
RSSAC 001 Implementation |
|
Currently in holding pattern, waiting for RFC2870bis to be published.
| ||||||||
RSSAC 002 Implementation |
| RSSAC002 Rec. 2: “RSSAC should monitor the progress of the implementation of these measures.”
Status:
| ||||||||
RFC7720 has been published as well: https://www.rfc-editor.org/info/rfc7720 | ||||||||||
RSSAC002 v2 | Closed
| RSSAC002v2 has been approved by RSSAC and available at: https://www.icann.org/en/system/files/files/rssac-002-measurements-root-07jan16-en.pdf Deployment of statistics is being tracked and updated as of Q3 2016. | ||||||||
RSSAC003 v1 | Open | IANA is studying the advice and to make a recommendation to ICANN Board. | ||||||||
Possible Work Items Pending RSSAC discussion / | resources resource availability |
| ||||||||
As Proposed at the RSSAC Caucus Kick Off Meeting on 22 March 2015:. - Test bed for RSSAC-001RSSAC001/RFC2870" compliance. - Writing easy-to-read, easy-to-find document about root servers. Incl. how to approach/reach the operators. - TCP/UCP counter not aligned in RSSAC-002Action Item: Lars-Johan Liman to ask DNS-OARC about public compliance of a test bed for RSSAC001/RFC2870bis. - Expand DITL to better see trends and avoid spikes. - Finding metrics deciding where to deploy anycast instances. (Incl: how to define "underserved area"). - Including more parties in root service.
As Proposed on RSSAC Caucus Mailing Lists Risks and Benefits of new naming scheme for root servers (Joe Abley, 19 May 2015)Action Item: Lars-Johan Liman to ask DNS-OARC about expanding DITL to better see trends and avoid spikes.
|
|