ICANN Root Name Server System Advisory Committee

1
ICANN Root Name Server System Advisory Committee

• March 2, 1999
• SUNTEC Convention Center
• Singapore

2
Agenda

• Introduction
• Background/Charter
• Members
• Issues/Tasks
• Future schedule
• Open meeting planning

3
RSSAC

• Root Server System issues have been addressed
• in the Green Paper and White Paper process
• in the formation of ICANN.
• Root Server System Advisory Committee(RSSAC)
• in ICANN bylaws
• JP left.

4
Why RSSAC?

• Changes in the root server system have been
  discussed inside and outside of the government
  for over two years. As part of the Green Paper
  and White Paper process, it was agreed that the
  entire system would be reviewed and revised as
  part of the formation of ICANN.
• Consequently, a specific provision for a Root
  Server System Advisory Committee(RSSAC) was
  included in the bylaws from the beginning.
• JP left.

5
Meeting Summary of RSSAC

• March 2, 1999 1000-1500 _at_room208
• 15 participants
• Root server operators group
• IETF/IAB
• IEPG
• IANA
• Mike Roberts

6
(No Transcript)
7
Extract from ICANN Bylaws

• "(b) There shall be a DNS Root Server System
  Advisory Committee. The initial chairman of the
  DNS Root Server System Advisory Committee shall
  be appointed by the Board subsequent chairs
  shall be elected by the members of the DNS Root
  Server System Advisory Committee pursuant to
  procedures adopted by the members. The
  responsibility of the Root Server System Advisory
  Committee shall be to advise the Board about the
  operation of the root name servers of the domain
  name system. The Root Server System Advisory
  Committee should consider and provide advice on
  the operational requirements of root name
  servers, including host hardware capacities,
  operating systems and name server software
  versions, network connectivity and physical
  environment. The Root Server System Advisory
  Committee should examine and advise on the
  security aspects of the root name server system.
  Further, the Root Server System Advisory
  Committee should review the number, location, and
  distribution of root name servers considering the
  total system performance, robustness, and
  reliability."

8
Extracts from ICANN Bylaws

• To advise the Board about the operation of the
  root name servers of the domain name system.
• To advise the Board on the operational
  requirements of root name servers, including host
  hardware capacities, operating systems and name
  server software versions, network connectivity
  and physical environment.
• To examine and to advise on the security aspects
  of the root name server system.
• To review the number, location, and distribution
  of root name servers considering the total system
  performance, robustness, and reliability.

9
Extracts from the Dept of Commerce - ICANN
MOU/JPA related to the root servers and system(1)

• "In the DNS Project, the Parties will jointly
  design, develop, and test the mechanisms,
  methods, and procedures to carry out the
  following DNS management functions
• Establishment of policy for and direction of the
  allocation of IP number blocks
• Oversight of the operation of the authoritative
  root server system
• Oversight of the policy for coordination of the
  DNS, including determining the circumstances
  under which new top level domains would be added
  to the root system and
• Coordination of the assignment of other Internet
  technical parameters as needed to maintain
  universal connectivity on the Internet.

10
Extracts from the Dept of Commerce - ICANN
MOU/JPA related to the root servers and system(2)

• Collaborate on a study on the design,
  development, and testing of a process for making
  the management of the root server system more
  robust and secure. This aspect of the DNS
  Project will address
• Operational requirements of root name servers,
  including host hardware capacities, operating
  system and name server software versions, network
  connectivity, and physical environment.
• Examination of the security aspects of the root
  name server system and review of the number,
  location, and distribution of root name servers
  considering the total system performance,
  robustness, and reliability.
• Development of operational procedures for the
  root server system, including formalization of
  contractual relationships under which root
  servers throughout the world are operated.

11
Extracts from the Dept of Commerce - ICANN
MOU/JPA related to the root servers and system(3)

• Collaborate on written technical procedures for
  operation of the primary root server including
  procedures that permit modifications, additions
  or deletions to the root zone file.
• Collaborate on a study and process for making the
  management of the root server system more robust
  and secure. This aspect of the plan will
  address
• Operational requirements of root name servers,
  including host hardware capacities, operating
  system and name server software versions, network
  connectivity, and physical environment.
• Examination of the security aspects of the root
  name server system and review of the number,
  location, and distribution of root name servers
  considering the total system performance,
  robustness, and reliability.
• Development of operational procedures for the
  root server system, including formalization of
  contractual relationships under which root
  servers throughout the world are operated.
• Collaborate on the design, development, and
  testing of a plan for creating a process that
  will consider the possible expansion of the
  number of gTLDs. The designed process should
  consider and take into account the following
• The potential impact of new gTLDs on the Internet
  root server system and Internet stability."

12
Work Items

• To write technical procedures for operation of
  the primary root server including procedures that
  permit modifications, additions or deletions to
  the root zone file.
• To make the management of the root server system
  more robust and secure
• Operational requirements of root name servers,
  including host hardware capacities, operating
  system and name server software versions, network
  connectivity, and physical environment.
• Examination of the security aspects of the root
  name server system and review of the number,
  location, and distribution of root name servers
  considering the total system performance,
  robustness, and reliability.
• Development of operational procedures for the
  root server system, including formalization of
  contractual relationships under which root
  servers throughout the world are operated.
• To design, develop, and test a plan for the
  possible expansion of the number of gTLDs. The
  designed process should consider and take into
  account the following
• New gTLDs
• IPv6

13
Other Issues discussed

• Future Relationship with other groups
• IETF related WG
• RFC2010 revise
• ASO/DNSO/etc.
• Y2K problems
• Risk Management

14
Membership

• The ICANN Board is responsible for appointing the
  initial chairman of the RSSAC, which it did at
  its meeting of 1/17/99 by appointing Jun Murai.
• It is anticipated that the chairman will nominate
  an initial slate of members for the RSSAC.
• It is not required that the committee have a
  specific number of members, nor that the full
  complement of members be appointed immediately.
• Root ops, DNS, and Topology area technical
  experts.

15
Schedules

• The second meeting of RSSAC
• During IETF/Minneapolis (March 15-19)
• Tentatively, on Tuesday, March 18.
• Expected initial output draft after the second
  meeting
• Say, March 31, 1999(?)
• Mailing list
• rssac_at_icann.org (?)

16
Open part of this meeting

• Introduction/background
• Work Items
• Members
• Hearing requirements
• Discussions
• Announcement of the 2nd meeting