Changes

Jump to navigation Jump to search

Root Server System Advisory Committee (view source)

Revision as of 15:53, 17 February 2021

621 bytes added ,  3 years ago
m
removed Category:Glossary using HotCat
Line 91: Line 91:  
|31 December 2023
 
|31 December 2023
 
|[[Hiro Hotta]]
 
|[[Hiro Hotta]]
−
|}
  −
  −
===Partner Member Representatives===
  −
The RSSAC includes two non-voting representatives from the organizations responsible for the maintenance of the authoritative [[root zone]]:
  −
  −
{| class="wikitable"
  −
!Partner Representative
  −
!Name
  −
!Affiliation
  −
|-
  −
|[[IANA Functions Stewardship Transition|IANA Functions Operator]]
  −
|[[James Mitchell]]
  −
|[[PTI]]
  −
|-
  −
|[[Root Zone|Root Zone Maintainer]]
  −
|[[Duane Wessels]]
  −
|[[Verisign]]
   
|}
 
|}
   Line 115: Line 98:  
! Organization || Liaison
 
! Organization || Liaison
 
|-
 
|-
−
| [[IANA]] || James Mitchell
+
| [[IANA]] || [[James Mitchell]]
 
|-
 
|-
−
| [[Root Zone]] Maintainer ([[Verisign]]) || Duane Wessels
+
| [[Root Zone|Root Zone Maintainer]] ([[Verisign]]) || [[Duane Wessels]]
 
|-
 
|-
−
| Internet Architecture Board ([[IAB]]) || Daniel Migault
+
| Internet Architecture Board ([[IAB]]) || [[Daniel Migault]]
 
|-
 
|-
−
| [[SSAC]] || Russ Mundy
+
| [[SSAC]] || [[Russ Mundy]]
    
|}
 
|}
   −
===RSSAC Liaisons to Other Organizations===
+
===Liaisons from RSSAC to Other Organizations===
 
RSSAC appoints liaisons to other groups and organizations to coordinate or communicate matters of common interest, as required by the [[RSSAC Operational Procedures]]
 
RSSAC appoints liaisons to other groups and organizations to coordinate or communicate matters of common interest, as required by the [[RSSAC Operational Procedures]]
 
{| class="wikitable"
 
{| class="wikitable"
Line 134: Line 117:  
|[[ICANN Board|ICANN Board of Directors]]
 
|[[ICANN Board|ICANN Board of Directors]]
 
|[[Kaveh Ranjbar]]
 
|[[Kaveh Ranjbar]]
−
|RIPE NCC
+
|[[RIPE NCC]]
 
|-
 
|-
 
|[[Customer Standing Committee]]
 
|[[Customer Standing Committee]]
 
|[[Lars-Johan Liman]]
 
|[[Lars-Johan Liman]]
−
|
+
|[[Netnod]]
 
|-
 
|-
 
|[[Root Zone Evolution Review Committee]]
 
|[[Root Zone Evolution Review Committee]]
 
|[[Daniel Migault]]
 
|[[Daniel Migault]]
−
|
+
|[[IAB]]
 
|-
 
|-
 
|[[NomCom|ICANN Nominating Committee]]
 
|[[NomCom|ICANN Nominating Committee]]
 
|[[Amir Qayyum]]
 
|[[Amir Qayyum]]
−
|
+
|[[ICANN]]
 +
|}
 +
 
 +
===Other Appointments===
 +
{| class="wikitable"
 +
| '''Team/Committee''' || '''RSSAC Rep'''
 +
|-
 +
|Second Security, Stability, and Resiliency Review Team ([[SSR2]]) || [[Eric Osterweil]]
 +
|-
 +
| ICANN [[Fellowship Program]] Selection Committee || [[Amir Qayyum]]
 +
|-
 +
| ICANN [[Fellowship Program]] Mentoring Committee || [[Rao Naveed Bin Rais]]
 +
|-
 +
| [[IANA]] Naming Function Review Team ([[IFRT]]) || [[Suzanne Woolf]]
 +
|-
 +
| [[NextGen@ICANN]] Selection Committee || [[Abdulkarim Oloyede]]
 +
|-
 +
| [[NextGen@ICANN]] Mentoring Committee || [[Dessalegn Yehuala]]
 
|}
 
|}
   −
==RSSAC Working Group==
+
===RSSAC Working Group===
 
The RSSAC Working Group is composed of:
 
The RSSAC Working Group is composed of:
 
* [[Harald Alvestrand]]
 
* [[Harald Alvestrand]]
 
* [[Steve Crocker]]
 
* [[Steve Crocker]]
 
* [[Bruce Tonkin]]
 
* [[Bruce Tonkin]]
 +
 +
===Previous Leaders===
 +
{| class="wikitable"
 +
! RSSAC Rep || Dates
 +
|-
 +
| [[Jun Murai]], Chair || January 1999 - December 2014
 +
|-
 +
| [[Matt Larson]], Vice Chair || August 2006 - July 2013
 +
|-
 +
| [[Lars-Johan Liman]], Co-Chair || July 2013 - December 2015
 +
|-
 +
| [[Tripti Sinha]], Co-Chair || January 2015 - October 2018
 +
|-
 +
| [[Brad Verd]], Co-Chair || January 2016 - October 2019
 +
|-
 +
| [[Fred Baker]], Co-Chair || October 2018 - October 2019
 +
|}
    
==RSSAC Projects==
 
==RSSAC Projects==
 
Since its inception, the committee continuously performs projects under a Cooperative Research and Development Agreement (CRADA)<ref>[http://www.icann.org/en/committees/dns-root/crada.htm CRADA]</ref> between [[ICANN]], the [[NIST|National Institute for Standards and Technology]] (NIST), and [[NTIA|National Telecommunications and Information Administration]] (NTIA), to conduct a collaborative study to address the operational and technical requirements of the root name servers to be able to establish a more robust and secure management of the Internet [[DNS]] root server system.<ref>[http://www.icann.org/en/committees/dns-root/ www.icann.org]</ref>
 
Since its inception, the committee continuously performs projects under a Cooperative Research and Development Agreement (CRADA)<ref>[http://www.icann.org/en/committees/dns-root/crada.htm CRADA]</ref> between [[ICANN]], the [[NIST|National Institute for Standards and Technology]] (NIST), and [[NTIA|National Telecommunications and Information Administration]] (NTIA), to conduct a collaborative study to address the operational and technical requirements of the root name servers to be able to establish a more robust and secure management of the Internet [[DNS]] root server system.<ref>[http://www.icann.org/en/committees/dns-root/ www.icann.org]</ref>
   −
The RSSAC was also involved in the Y2K Project between 1999 to 2000. Its objective was to make sure that the operations of the root nameserver system is in compliance with Y2K protocol by conducting administrative services and testing.<ref>[http://www.icann.org/en/committees/dns-root/y2k-statement.htm RSSAC Statement on Root Nameserver Year 2000 Status]</ref>
+
The RSSAC was also involved in the Y2K Project between 1999 to 2000. Its objective was to make sure that the operations of the root nameserver system are in compliance with the Y2K protocol by conducting administrative services and testing.<ref>[http://www.icann.org/en/committees/dns-root/y2k-statement.htm RSSAC Statement on Root Nameserver Year 2000 Status]</ref>
    
The committee is also conducting new technical developments on [[IPv6]], [[DNSSEC]], [[IDN]], and their effects to the root nameserver system.
 
The committee is also conducting new technical developments on [[IPv6]], [[DNSSEC]], [[IDN]], and their effects to the root nameserver system.
Line 164: Line 181:  
== 2008-9 Independent Review of RSSAC by Westlake Consulting Limited==
 
== 2008-9 Independent Review of RSSAC by Westlake Consulting Limited==
 
Article IV, Section 4, Paragraph 1 of the ICANN Bylaws stipulated that a review on the performance and operations of the RSSAC by an independent organization is required to determine if the committee is still serving its purpose in the ICANN structure and if certain changes in the structure or operations are necessary to improve its functions.<ref>
 
Article IV, Section 4, Paragraph 1 of the ICANN Bylaws stipulated that a review on the performance and operations of the RSSAC by an independent organization is required to determine if the committee is still serving its purpose in the ICANN structure and if certain changes in the structure or operations are necessary to improve its functions.<ref>
−
[http://www.icann.org/en/general/archive-bylaws/bylaws-15dec02.htm#IV ICANN Bylaws 2002]</ref> To be able to comply with the Bylaws, the [[ICANN Board]] issued a Request For Proposal and Terms of Reference to conduct and independent review on the RSSAC in July, 2008.<ref>[http://192.0.43.22/en/reviews/rssac/rfp-tor-request-11jul08-en.htm Request For Proposals]</ref> ICANN selected [[Westlake Consulting Limited]], and in November of 2008, the company started performing face to face interviews with some individuals during the ICANN Meeting in Cairo and during the IETF meeting in Minnesota regarding RSSAC. WCL also conducted telephone interviews and accessed all available written-records regarding the committee. <ref>[http://192.0.43.22/en/reviews/rssac/ RSSAC Review]</ref>
+
[http://www.icann.org/en/general/archive-bylaws/bylaws-15dec02.htm#IV ICANN Bylaws 2002]</ref> To be able to comply with the Bylaws, the [[ICANN Board]] issued a Request For Proposal and Terms of Reference to conduct an independent review on the RSSAC in July 2008.<ref>[http://192.0.43.22/en/reviews/rssac/rfp-tor-request-11jul08-en.htm Request For Proposals]</ref> ICANN selected [[Westlake Consulting Limited]], and in November of 2008, the company started performing face to face interviews with some individuals during the ICANN Meeting in Cairo and during the IETF meeting in Minnesota regarding RSSAC. WCL also conducted telephone interviews and accessed all available written-records regarding the committee. <ref>[http://192.0.43.22/en/reviews/rssac/ RSSAC Review]</ref>
    
===Findings===
 
===Findings===
Line 173: Line 190:  
* The records of the RSSAC meetings are poor and incomplete.
 
* The records of the RSSAC meetings are poor and incomplete.
 
* The election process of the members of the committee and its chairman is not clear.
 
* The election process of the members of the committee and its chairman is not clear.
−
* The Root Server Operators believed that some of the functions of RSSAC identified in the Bylaws of ICANN are their responsibility, and because of that the committee's reported little of its responsibilities.
+
* The Root Server Operators believed that some of the functions of RSSAC identified in the Bylaws of ICANN are their responsibility, and because of that, the committee reported little of its responsibilities.
−
* Interaction between RSSAC and the different organization within ICANN is limited because most of the committee's members do not or seldom participate in [[ICANN Meetings]]. RSSAC committee members frequently attend or conduct their meeting in conjunction with the meetings of the [[IETF]].
+
* Interaction between RSSAC and the different organizations within ICANN is limited because most of the committee's members do not or seldom participate in [[ICANN Meetings]]. RSSAC committee members frequently attend or conduct their meetings in conjunction with the meetings of the [[IETF]].
    
===Recommendations===
 
===Recommendations===
 
Based on its final report, WCL recommended the following to improve the operational functions of RSSAC:<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-mar09-en.pdf Final Report Independent Review on RSSAC]</ref>
 
Based on its final report, WCL recommended the following to improve the operational functions of RSSAC:<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-mar09-en.pdf Final Report Independent Review on RSSAC]</ref>
 
* Re-establish RSSAC as a strategy group which will be jointly supervised by ICANN and Root Server Operators.
 
* Re-establish RSSAC as a strategy group which will be jointly supervised by ICANN and Root Server Operators.
−
* Amend the Terms of Reference of the ICANN Bylaws and set out a new role for RSSAC to "provide a source of unbiased strategic advice to ICANN, the Root Server Operators and the Internet Community about the best way ahead for the Root Server System."  
+
* Amend the Terms of Reference of the ICANN Bylaws and set out a new role for RSSAC to "provide a source of unbiased strategic advice to ICANN, the Root Server Operators, and the Internet community about the best way ahead for the Root Server System."  
 
* Reconstitute RSSAC's membership with 9 initial members who have strong technical backgrounds. The committee should be composed of 4 Root Server Operators, 1 appointed by [[IANA]]; and 4 appointed by the  ICANN Board/[[NomCom|Nominating Committee]].
 
* Reconstitute RSSAC's membership with 9 initial members who have strong technical backgrounds. The committee should be composed of 4 Root Server Operators, 1 appointed by [[IANA]]; and 4 appointed by the  ICANN Board/[[NomCom|Nominating Committee]].
−
* The Chairman of the committee shall be appointed by its members with a two year term, with a limited three consecutive 2-years terms.
+
* The Chairman of the committee shall be appointed by its members with a two-year term, with a limited three consecutive 2-years terms.
−
* Appoint non-voting liaison members, which include Outward liaison from the RSSAC to the ICANN Board and the [[SSAC]] and an Inward liaison to the RSSAC from [[IETF]]/[[IAB]].
+
* Appoint non-voting liaison members, which include an Outward liaison from the RSSAC to the ICANN Board and the [[SSAC]] and an Inward liaison to the RSSAC from [[IETF]]/[[IAB]].
 
* RSSAC should meet in conjunction with ICANN meetings and may be able to hold additional meetings as necessary; meetings shall be open for public participation and hold a closed meeting if necessary; Root Server Operators and members of the ICANN Board should be invited to the meeting even during closed sessions and shall be given the right to speak under the RSSAC Chairman's discretion.
 
* RSSAC should meet in conjunction with ICANN meetings and may be able to hold additional meetings as necessary; meetings shall be open for public participation and hold a closed meeting if necessary; Root Server Operators and members of the ICANN Board should be invited to the meeting even during closed sessions and shall be given the right to speak under the RSSAC Chairman's discretion.
    
===RSSAC Working Group Review on WCL Report===
 
===RSSAC Working Group Review on WCL Report===
−
In June, 2010, the RSSAC Working Group submitted its final report regarding the findings of WCL's independent review. The Working Group acknowledged that the committee was not able to fully serve its purpose in the ICANN structure because of lack of regular communication between ICANN and RSSAC, the committee has insufficient knowledge about ICANN  and vice versa, the role and responsibilities of RSSAC as stipulated in the ICANN Bylaws need amendment and the shared understanding between the RSSAC role, Root Server Operators responsibilities and the ICANN mission is not clear. The Working Group recommended that the full cooperation of the Root Server Operators is necessary to implement structural and operational changes to improve the operations of RSSAC.<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-report-08jun10-en.pdf RSSAC Working Group Final Report]</ref>
+
In June 2010, the RSSAC Working Group submitted its final report regarding the findings of WCL's independent review. The Working Group acknowledged that the committee was not able to fully serve its purpose in the ICANN structure because of lack of regular communication between ICANN and RSSAC, the committee has insufficient knowledge about ICANN  and vice versa, the role and responsibilities of RSSAC as stipulated in the ICANN Bylaws need amendment and the shared understanding between the RSSAC role, Root Server Operators responsibilities and the ICANN mission is not clear. The Working Group recommended that the full cooperation of the Root Server Operators is necessary to implement structural and operational changes to improve the operations of RSSAC.<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-report-08jun10-en.pdf RSSAC Working Group Final Report]</ref>
    
===Advisories===
 
===Advisories===
 
At its regular meeting in November 2014, the RSSAC formally approved RSSAC001 and RSSAC002, the first two formal advisories produced under its reorganized structure.  
 
At its regular meeting in November 2014, the RSSAC formally approved RSSAC001 and RSSAC002, the first two formal advisories produced under its reorganized structure.  
−
RSSAC001 defines the best practice service to be provided by root servers and defines the operational expectations that users might reasonably anticipate of both that service and the root server operators. This document highlights that a diversity of approach is desirable in the root server system.<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>
+
RSSAC001 defines the best practice service to be provided by root servers and defines the operational expectations that users might reasonably anticipate of both that service and the root server operators. This document highlights that a diversity of approaches is desirable in the root server system.<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>
   −
RSSAC002 "identifies and recommends an initial set of parameters that would be useful to monitor for establishing a baseline and trends for the root server system. The implementation of these measurements (and future refinements to them) by root server operators will form an early warning system that will assist in detecting and mitigating any effects (or the absence of such effects) associated with growing size of the root zone."<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>
+
RSSAC002 "identifies and recommends an initial set of parameters that would be useful to monitor for establishing a baseline and trends for the root server system. The implementation of these measurements (and future refinements to them) by root server operators will form an early warning system that will assist in detecting and mitigating any effects (or the absence of such effects) associated with the growing size of the root zone."<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>
    
==2017-19 Independent Review of RSSAC by Interisle Consulting Group, LLC==
 
==2017-19 Independent Review of RSSAC by Interisle Consulting Group, LLC==
Line 218: Line 235:  
* Interisle's "own extensive knowledge of ICANN, the RSSAC, and the DNS root server system."<ref name="finalreport2" />  
 
* Interisle's "own extensive knowledge of ICANN, the RSSAC, and the DNS root server system."<ref name="finalreport2" />  
   −
Interisle subjected this data to a structured qualitative analysis<ref>For a primer on structured qualitative analysis, see [https://www.qualitative-research.net/index.php/fqs/article/view/2092/3904 Herz, Peters, & Truschkat: "How to Do Qualitative Structural Analysis: The Qualitative Interpretation of Network Maps and Narrative Interviews;" Forum: Qualitative Social Research, Vol. 16 No. 1, January 2015]</ref> and presented its findings in an initial Assessment Report to ICANN.<ref>[https://www.icann.org/news/announcement-2018-02-27-en RSSAC2 Review: Assessment Report Published - ICANN announcement, February 27, 2018]</ref> The draft assessment report was the topic of meetings between members of RSSAC's Review Work Party and Interisle's consultants.<ref>[https://participate.icann.org/p2zrcgd41jl/ Recording of RSSAC Review2 Work Party, February 15, 2018]</ref><ref>[https://community.icann.org/display/ACCRSSAC/RSSAC+Work+Party+Meetings The RSSAC Work Party Meetings Archive] lists a meeting on February 20, intended to cover feedback provided by the RWP. However, a recording is presently not available.</ref>
+
Interisle subjected this data to a structured qualitative analysis<ref>For a primer on structured qualitative analysis, see [https://www.qualitative-research.net/index.php/fqs/article/view/2092/3904 Herz, Peters, & Truschkat: "How to Do Qualitative Structural Analysis: The Qualitative Interpretation of Network Maps and Narrative Interviews;" Forum: Qualitative Social Research, Vol. 16 No. 1, January 2015]</ref> and presented its findings in an Initial Assessment Report to ICANN.<ref>[https://www.icann.org/news/announcement-2018-02-27-en RSSAC2 Review: Assessment Report Published - ICANN announcement, February 27, 2018]</ref> The draft assessment report was the topic of meetings between members of RSSAC's Review Work Party and Interisle's consultants.<ref>[https://participate.icann.org/p2zrcgd41jl/ Recording of RSSAC Review2 Work Party, February 15, 2018]</ref><ref>[https://community.icann.org/display/ACCRSSAC/RSSAC+Work+Party+Meetings The RSSAC Work Party Meetings Archive] lists a meeting on February 20, intended to cover feedback provided by the RWP. However, a recording is presently not available.</ref>
    
The Assessment Report listed a total of forty-two findings in response to the issues and questions posed by ICANN.<ref name="assessment">[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-22feb18-en.pdf RSSAC Review - Assessment Report for Public Consultation]</ref> Of these, Interisle identified eight principal findings, which they highlighted in the report and its executive summary<ref>[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-exec-summary-22feb18-en.pdf]</ref> of the assessment:
 
The Assessment Report listed a total of forty-two findings in response to the issues and questions posed by ICANN.<ref name="assessment">[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-22feb18-en.pdf RSSAC Review - Assessment Report for Public Consultation]</ref> Of these, Interisle identified eight principal findings, which they highlighted in the report and its executive summary<ref>[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-exec-summary-22feb18-en.pdf]</ref> of the assessment:
Line 274: Line 291:     
__FORCETOC__
 
__FORCETOC__
−
[[Category:Glossary]]
   
[[Category: ICANN Bodies]]
 
[[Category: ICANN Bodies]]
Jessica
Bureaucrats, Check users, lookupuser, Administrators, translator
14,927

edits

Retrieved from "https://icannwiki.org/Special:MobileDiff/1302669...1305510"

Navigation menu