Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
2015Post-Workshop teleconferences being scheduled and public report being drafted

Work

Status

Update: 14December 2016 10:30 EST

 

Administrative Items

 

RSSAC Meetings

Ongoing

The most recent RSSAC meeting teleconference was on 3 01 December 20152016.

Open Action Items from Previous Teleconference(s)

  • Carlos Reyes to distribute an updated proposal for the RSSAC schedule at ICANN Meetings A, B, and C for 2016. 
  • Kathy Schnitt and Carlos Reyes to work on transcripts and notes from the Caucus meeting at IETF94.
  • Lars-Johan Liman and Tripti Sinha to draft RSSAC’s input to the CCWG-Accountability third proposal for RSSAC discussion.
  • Elise Gerich to make a recommendation to the ICANN Board of Directors for implementing RSSAC003.
  • Suresh Krishnaswamy and Andrew McConachie to submit a statement of interest to the Membership Committee for joining the Caucus mailing list.

Action Items from This Meeting

  • Lars-Johan Liman and Steve Sheng to incorporate edits to the Workshop 2015 report and re-circulate draft to the RSSAC.
  • Suzanne Woolf to follow-up with Root Servers Naming Scheme Work Party leader on status of its document.
  • Carlos Reyes to follow-up with Elise Gerich on RSSAC003 implementation recommendations.
  • Steve Sheng to track the status of the Root Server System history document.
  • Kevin Jones and Carlos Reyes to track input for RSSAC000 revisions.
  • Steve Sheng to invite Karen Lentz to the next RSSAC teleconference to brief the RSSAC about the Continuous Data-driven Analysis of Root Server System Stability study plan.
  • Kathy Schnitt to draft a calendar of RSSAC teleconferences and meetings for 2016.
    • Staff to publish the minutes from the 4 November 2016 teleconference.
    • Staff to send the published minutes from 4 November 2016 to the RSSAC Caucus.
    • Staff to draft and submit a submission to the Board for the reelection of Tripti Sinha as an RSSAC co-chair.
    • Staff and co-chairs to continue working on finding candidates for RSSAC endorsement for the 2nd Security, Stability and Resiliency of the DNS Review.
    • Co-chairs to create and share a response to CCWG SO/AC accountability sub-group (CCWG-ACCT).
    • Staff to send out a poll for RSSAC Workshop 4 dates.
    • Staff to send an email to RSSAC with links and information on how to respond to current ICANN open public comment periods.
    •  

      The next RSSAC meeting will be January 2017

    Agenda Items:

     

     Next meeting is on 7 January 2015.

     

    RSSAC Caucus Meetings

    Ongoing

    Last Caucus Meeting was on 1 06 November 2015 (at IETF94). Minutes and notes will be posted soon2016 at ICANN 57 in Hyderabad, India. The next RSSAC Caucus Meeting is in Chicago, IL at IETF.

     

    RSSAC at ICANN Meetings

    OngoingICANN56 will be 5-10 March 2016 in Marrakech, Morocco.

    The most recent RSSAC Meeting at ICANN was on 04 November 2016 in Hyderabad, India

    Action Items:

    • Staff to publish minutes from the 06 October 2016 Teleconference (DONE)
    • Staff to send the published minutes from the 06 October 2016 to the RSSAC Caucus (DONE)
    • Staff to publish the History of the Root Server System document (DONE)
    • Staff to publish the Key Technical Elements of Potential Root Server Operators document (DONE)
    • Staff to publish the October 2016 Workshop Report document (DONE)

      ICANN 58 will be from March 11-16 20167 in Copenhagen, Denmark

     

    RSSAC Travel Support

    Ongoing

    For FY16FY17, RSSAC has 5 6 slots (2 co-chairs and 3 4 RSSAC members) for ICANN meetings.

    Travel support Support requests for ICANN55 are being processedICANN58 are in the process.

     

    RSSAC Workshop 2016

    Ongoing

    Open

    THE date for the 2016 RSSAC Workshop will be on May 2,3,4 in Reston, VA.

     

    RSSAC Workshop 2016OpenInitial planning underway. 

    Public Comments/Input

     

    Closed

    Continuous Data-Driven Analysis of Root Server System Stability: https://www.icann.org/public-comments/cdar-study-plan-2015-12-02-en

    FY17 Draft Operating Plan and Budget: https://forum.icann.org/lists/comments-op-budget-fy17-five-year-05mar16/msg00000.html

    CCWG-Principles: Carlos Reyes drafting RSSAC Co-Chairs response to CCWG-Principles Co-Chairs.

    Draft New ICANN Bylaws: https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-enRoot Stability Study

     

    CCWG Proposal on Enhancing ICANN Accountability Ongoing

    CLOSED: RSSAC

    to submit comments on third draft proposal. Co-Chairs to coordinate

    submitted comments on 9 January 2015 and follow-up discussions ensued on proposed ICANN bylaws changes. RSSAC also submitted a congratulatory statement to ICG via Liman on 10 March 2016.

     

    Work Parties/Committees

     

    Membership Committee

    Ongoing

    Members: Paul Vixie, Tripti Sinha, and Kaveh Ranjbar.

    One applicant under consideration for 3 December 2015.

     

    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 SchemeNaming Scheme Work PartyOngoing

    Shepherd: Suzanne Woolf

    Leader: John Bond

    Work Party held a meeting at IETF95. John Bond has replaced Joe Abley Deadline for draft submission (20 November) has passed.as work party leader. Work continues.

    12/14/2016 - The work party produced final reports

     
    Anycast InstancesNew

    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 SystemClosed

    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 v3Closed.

    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

    OpenOngoing

    Kevin Jones is leading an effort to revise the RSSAC operational procedures. Carlos Reyes is providing staff support.

    RSSAC001 v1OpenClosed

    RSSAC001

    is

    has been approved by RSSAC and available at: https://www.icann.org/en/system/files/files/rssac-001-draft-20nov14-en.pdf.

    It will be published in tandem with draft-iab-2870bis-02.

    RFC7720 has been published as well: https://www.rfc-editor.org/info/rfc7720

    RSSAC002 v2

    Closed


    Ongoing

    RSSAC002v1 ImplementationOpen

    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

    Q4 2015.
    RSSAC002v2OpenSteve Sheng working with Duane Wessels on next steps.

    Q3 2016.

    RSSAC003 v1OpenIANA is studying the advice and RSSAC003OpenElise Gerich to make a recommendation to the ICANN Board of Directors for implementing RSSAC003.
    History of Root Server SystemOpenSteve Sheng has distributed the latest draft to the contributors.

    Possible Work Items Pending RSSAC discussion / resource availability

    Proposed at the RSSAC Caucus Meeting on 22 March 2015.

          - Test bed for RSSAC001/RFC2870" compliance. Action 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. Action Item: Lars-Johan Liman to ask DNS-OARC about expanding DITL to better see trends and avoid spikes.       - Finding metrics deciding where to deploy anycast instances. (Incl: how to define "underserved area"). Action Item: RSSAC to explore the need for a work party (after the Workshop) on finding metrics to decide where to deploy anycast instances and how to define 'underserved area'.