<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:18.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Calibri","sans-serif";
font-weight:bold;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1673490508;
mso-list-template-ids:-547732630;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=FR link=blue vlink=purple>
<div class=Section1>
<p style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:7.5pt;
margin-left:0cm'><span style='font-family:"Arial","sans-serif"'><a
href="http://www.icann.org/en/announcements/announcement-24may10-en.htm">http://www.icann.org/en/announcements/announcement-24may10-en.htm</a></span><span
style='color:#1F497D'><o:p></o:p></span></p>
<h2 style='margin-bottom:0cm;margin-bottom:.0001pt'><span style='font-family:
"Arial","sans-serif"'>Public Comment: April 2010 DNS-CERT Operational
Requirements & Collaboration Analysis</span><o:p></o:p></h2>
<p style='mso-margin-top-alt:11.25pt;margin-right:0cm;margin-bottom:0cm;
margin-left:0cm;margin-bottom:.0001pt'><span style='font-family:"Arial","sans-serif"'>24
May 2010</span><o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>ICANN is today opening a
public comment period on the <a
href="http://www.icann.org/en/topics/ssr/dns-cert-collaboration-analysis-24may10-en.pdf">April
2010 DNS-CERT Operational Requirements and Collaboration Analysis Workshop Report</a>
(with Minority Statement). In advance of the ICANN Brussels meeting, ICANN is
seeking comments on the potential requirements identified in the workshop
report, DNS Security response gaps.</span><o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>In addition, ICANN is
publishing the <a
href="http://www.icann.org/en/public-comment/summary-analysis-strategic-ssr-initiatives-and-dns-cert-business-case-24may10-en.pdf">Summary
& Analysis of Comments on the Security Strategic Initiatives and Global
DNS-CERT Business Case papers</a>, and the <a
href="http://www.icann.org/en/topics/ssr/dns-cert-consultation-record-24may10-en.pdf">DNS-CERT
Consultation record</a>. The consultation record is included for transparency
on the formation of the DNS-CERT concept and consultations that have occurred
in parallel with the public comment period on the Security Strategic
Initiatives papers.</span><o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>The DNS-CERT Operational
Requirements and Collaboration Analysis Workshop report was prepared by Jose
Nazario, Arbor Networks, Roy Arends, Nominet, and Chris Morrow, Google, and is
the output from a tabletop workshop conducted 6-7 April 2010 in Washington DC.
Participants identified several requirements for responding to Internet and DNS
security events, many of which are under-met or ignored by existing DNS
security capabilities. They are:</span><o:p></o:p></p>
<ul style='margin-top:0cm' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>A trusted communications channel, or multiple
channels, for use during event response that is usable by the appropriate
parties.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>Standing incident coordination and response
functions, which enable consistent and professional incident handling
efforts.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>Incident status tracking through to completion, with
communication to the necessary parties.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>Trusted guidance on issues with knowledge and
experience with the various and varied areas of Internet and DNS security.
Respect of these voices by the areas of the Internet and DNS communities
with which they speak is important.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>A trust broker / introduction service across
traditional communities boundaries, recognizing that the community
identifying threats to Internet and DNS operations is often far-flung and
sometimes outside the knowledge of the Internet and DNS operator and
vendor communities.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>Analysis capabilities, including data such as DNS
traffic, software vulnerabilities and attack traffic, to validate
incidents and identify next steps as quickly as possible.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>Institutional memory in the form of reports,
recommendations, and best practices, which can inform the various Internet
and DNS security communities, support future successful incident
responses, and help evolve incident response capabilities.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>Outreach and education functions to share best
practices for securing Internet and DNS operations, secure registration
functions, implementing DNSSEC, and other key DNS and security factors.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>The ability to act quickly, and to be prepared to
act with necessary resources in response to threats to the DNS of a global
nature in a timely and sustained manner.</span><o:p></o:p></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1'><span style='font-family:
"Arial","sans-serif"'>A sensitivity to the complexity of the international
nature of the DNS, understanding the capabilities and limitations of the
global DNS community.</span><o:p></o:p></li>
</ul>
<p><span style='font-family:"Arial","sans-serif"'>Workshop participants noted
many of these functions are addressed by various groups, either standing or
ad-hoc. Some participants expressed concern that only a few of the existing
organizations are DNS-specific. The report includes a <a
href="http://www.icann.org/en/topics/ssr/dns-cert-collaboration-analysis-minority-statement-18may10-en.pdf">Minority
Statement</a> from Kathy Kleiman, Public Interest Registry, and Greg Aaron,
Afilias.</span><o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>Comments on the Operational
Requirements and Collaboration Analysis Report submitted to <a
href="mailto:dns-collab-analysis@icann.org">dns-collab-analysis@icann.org</a>
will be considered until 2 Jul 2010 23:59 UTC. Comments may be viewed at <a
href="http://forum.icann.org/lists/dns-collab-analysis/">http://forum.icann.org/lists/dns-collab-analysis/.</a></span><o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>A consultation session will
be held at the ICANN meeting in Brussels on the Security Strategic Initiatives
(DNS-CERT and system-wide DNS Risk Assessment and exercises), with a date and
time soon to be included in the Brussels meeting schedule.</span><o:p></o:p></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'>Glen
de Saint Géry<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'>GNSO
Secretariat<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US style='font-size:12.0pt;font-family:
"Arial","sans-serif"'><a href="mailto:gnso.secretariat@gnso.icann.org"><span
lang=FR>gnso.secretariat@gnso.icann.org</span></a></span><span
style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US style='font-size:12.0pt;font-family:
"Arial","sans-serif"'><a href="http://gnso.icann.org">http://gnso.icann.org</a><o:p></o:p></span></p>
<p align=center style='text-align:center'><o:p> </o:p></p>
</div>
</body>
</html>