1 / 12

ICANN Security and Stability Advisory Committee

ICANN Security and Stability Advisory Committee. ICANN Meetings Rio de Janeiro March 26, 2003. Steve Crocker, Chair Alain Aina Jaap Akkerhuis Doug Barton Steven M. Bellovin Rob Blokzijl David R. Conrad Mark Kosters Allison Mankin Ram Mohan. Russ Mundy Jun Murai

trent
Download Presentation

ICANN Security and Stability Advisory Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICANN Security and StabilityAdvisory Committee ICANN Meetings Rio de Janeiro March 26, 2003

  2. Steve Crocker, Chair Alain Aina Jaap Akkerhuis Doug Barton Steven M. Bellovin Rob Blokzijl David R. Conrad Mark Kosters Allison Mankin Ram Mohan Russ Mundy Jun Murai Frederico A.C. Neves Ray Plzak Doron Shikmoni Ken Silva Bruce Tonkin Paul Vixie Rick Wesson Johan Ihren (observer) Committee Staff support: Jim Galvin

  3. Committee Strengths • Root Server Operators • gTLD Operators • ccTLD Operators • Name Space Registries • Regional Internet Registries (RIRs) • Registrars • Internet Security No policy or political members(!)

  4. Roles • Respond to board queries and tasks • Choose topics to probe • Report to board and to larger community • Build and maintain a perspective on Internet security

  5. CERT ICANNSecurity and StabilityAdvisory Committee AUCERT NANOG IETF IAB

  6. Process • Respond to queries from the board • Select tasks for coordination and advice • Publish short and long documents as available • Work closely with other groups, e.g. RSSAC, ccTLD group, GAC, etc. • Liaisons, regular reporting • Focus on content, not territory or limelight

  7. Activities • Securing the Edge • WHOIS recommendation • ccTLD name transfer procedure • VGRS advice • DNSSEC assessment • Overall security assessment • IPv6 transition assessment

  8. SAC comments on gTLD Whois • To ICANN • Last verified date • Privacy is needed • Standard format be developed • To IANA • Publicly available list of WHOIS servers

  9. ccTLD Nameserver Change • "Procedures for Handling Requests by ccTLD Managers to Change Nameservers" now posted at www.iana.org/cctld/nameserver-change-procedures-19mar03.htm • Joint effort of IANA, ccTLD, SECSAC

  10. ccTLD Follow-up • Revision of procedures as experience is gained • Reduce ambiguity • Understand and codify exception handling • Work with parties on automation of process including authentication

  11. Communications • Response to board • Public reports • Informal interaction with anyone • Tasks and reports with other groups • ccTLD, Whois, GAC • Documents

  12. SECSAC Documents www.icann.org/committees/security [SAC004] - Securing the Edge (17 October 2003) www.icann.org/committees/security/sac004.pdf [SAC003] - WHOIS Recommendation (1 December 2002) www.icann.org/committees/security/sac003.pdf [SAC002] - ICANN DNS Security Update (4 January 2002) www.icann.org/committees/security/sac002.htm [SAC001] - DNS Security Reading List (November 2001) www.icann.org/committees/security/sac001.htm

More Related