<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" 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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Noto Sans Symbols";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:769200161;
mso-list-template-ids:-233927662;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Noto Sans Symbols";
mso-fareast-font-family:"Noto Sans Symbols";
mso-hansi-font-family:"Noto Sans Symbols";
mso-bidi-font-family:"Noto Sans Symbols";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Courier New";
mso-fareast-font-family:"Courier New";
mso-hansi-font-family:"Courier New";
mso-bidi-font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:▪;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Noto Sans Symbols";
mso-fareast-font-family:"Noto Sans Symbols";
mso-hansi-font-family:"Noto Sans Symbols";
mso-bidi-font-family:"Noto Sans Symbols";}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Noto Sans Symbols";
mso-fareast-font-family:"Noto Sans Symbols";
mso-hansi-font-family:"Noto Sans Symbols";
mso-bidi-font-family:"Noto Sans Symbols";}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Courier New";
mso-fareast-font-family:"Courier New";
mso-hansi-font-family:"Courier New";
mso-bidi-font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:▪;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Noto Sans Symbols";
mso-fareast-font-family:"Noto Sans Symbols";
mso-hansi-font-family:"Noto Sans Symbols";
mso-bidi-font-family:"Noto Sans Symbols";}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:●;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Noto Sans Symbols";
mso-fareast-font-family:"Noto Sans Symbols";
mso-hansi-font-family:"Noto Sans Symbols";
mso-bidi-font-family:"Noto Sans Symbols";}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Courier New";
mso-fareast-font-family:"Courier New";
mso-hansi-font-family:"Courier New";
mso-bidi-font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:▪;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ascii-font-family:"Noto Sans Symbols";
mso-fareast-font-family:"Noto Sans Symbols";
mso-hansi-font-family:"Noto Sans Symbols";
mso-bidi-font-family:"Noto Sans Symbols";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As per the action item of yesterday’s meeting, please find attached the presentation that was provided by Becky Burr to the GNSO Council during its Strategic Planning Session that took place in January of
this year. Below you will also find the notes from this session that have been excerpted from GNSO Council Strategic Planning Meeting Report.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Caitlin, Berry and Marika<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">===================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From the GNSO Council Strategic Planning Meeting Report</span></b><span style="font-size:11.0pt"> (see
<a href="http://mm.icann.org/pipermail/council/attachments/20180307/1b480812/GNSOCouncilSPSMeetingReport29-31January2018-FINAL.pdf">
http://mm.icann.org/pipermail/council/attachments/20180307/1b480812/GNSOCouncilSPSMeetingReport29-31January2018-FINAL.pdf</a>).
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt">Objective</span></i></b><i><span style="font-size:11.0pt">: Explain the “picket fence” and ICANN SO/AC structure in the context of history of the organization and how this impacts on the GNSO’s role
and function within ICANN<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt">High level notes</span></i></b><i><span style="font-size:11.0pt">:<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">See presentation provided by Becky Burr (<u><span style="color:blue"><a href="https://gnso.icann.org/en/picket-fence-concept-overview-29jan18-en.pdf">https://gnso.icann.org/en/picket-fence-concept-overview-29jan18-en.pdf</a></span></u>).
<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt"><o:p> </o:p></span></i></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">ICANN’s picket fence – what is it and where did it come from?<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">In October 1998 agreement to transition from Verisign as sole registry and registrar for .com, .net and .org, followed by naming of competing registrars in April
1999. <o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">First registry agreement and registrar accreditation agreement signed on 10 November 1999.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">ICANN needed the ability to uniformly enforce obligations, including the ability to add additional obligations without contractual negotiations. As part of that
discussion, there was a need to identify the areas in which such additional contractual obligations could be added, tied to ICANN’s mission as well as a process by which such additional contractual obligations could be developed.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">The “picket fence” characterized this area that would delineate the topics for which ICANN could enforce additional contractual obligations that would have gone
through an agreed upon process; anything outside of that area would need to be the subject of contract negotiations.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">Registry and registrar agreements cover the picket fence in slightly divergent ways. A number of examples were included in the agreements to provide an illustration
of what topics would be considered within the picket fence. <o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">Picket fence incorporated into the post-transition Bylaws:<o:p></o:p></span></i>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level2 lfo1"><i><span style="font-size:11.0pt">The mission of the Internet Corporation for Assigned Names and Numbers (“ICANN”) is to ensure the stable and secure operation of the Internet’s unique identifier
systems … (the “Mission”). Specifically, ICANN:<o:p></o:p></span></i>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level3 lfo1"><i><span style="font-size:11.0pt">Coordinates the allocation and assignment of names in the root zone of the Domain Name System (“DNS”) and coordinates the development and implementation of policies
concerning the registration of second-level domain names in generic top-level domains (“gTLDs”). In this role, ICANN’s scope is to coordinate the development and implementation of policies:
<o:p></o:p></span></i>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level4 lfo1"><i><span style="font-size:11.0pt">For which uniform or coordinated resolution is reasonably necessary to facilitate the openness, interoperability, resilience, security and/or stability of the
DNS including, with respect to gTLD registrars and registries, policies in the areas described in Annex G-1 and Annex G-2; and
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level4 lfo1"><i><span style="font-size:11.0pt">That are developed through a bottom-up consensus-based multistakeholder process and designed to ensure the stable and secure operation of the Internet’s unique
names systems. <o:p></o:p></span></i></li></ul>
</li></ul>
</li></ul>
</li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">Annex G-2 (Registry specification):<o:p></o:p></span></i>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level2 lfo1"><i><span style="font-size:11.0pt">The topics, issues, policies, procedures and principles referenced in Section 1.1(a)(i) with respect to gTLD registries are:<o:p></o:p></span></i>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level3 lfo1"><i><span style="font-size:11.0pt">Issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, security and/or stability of the Internet or DNS;
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level3 lfo1"><i><span style="font-size:11.0pt"> functional and performance specifications for the provision of registry services;
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level3 lfo1"><i><span style="font-size:11.0pt"> security and stability of the registry database for a TLD;
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level3 lfo1"><i><span style="font-size:11.0pt"> registry policies reasonably necessary to implement Consensus Policies relating to registry operations or registrars;
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level3 lfo1"><i><span style="font-size:11.0pt">resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names); or
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level3 lfo1"><i><span style="font-size:11.0pt"> restrictions on cross-ownership of registry operators and registrars or registrar resellers and regulations and restrictions with respect to registry operations
and the use of registry and registrar data in the event that a registry operator and a registrar or registrar reseller are affiliated.
<o:p></o:p></span></i></li></ul>
</li></ul>
</li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">Registrar specification (G-1) only differs with regards to domain name use.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">As a result of the transition-related work, namely the CCWG-Accountability recommendations, the picket fence was incorporated into the Bylaws as part of ICANN’s
mission. The mission is now clarified to include the constraints that are in place with regards to ICANN’s authority and ability to enforce contractual obligations on the topics as outlined in the Bylaws.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">It was necessary from a contracted parties’ perspective to balance out ICANN’s need to develop policies and impose them on contracted parties, where those policies
are necessary for security and stability reasons. Incorporating the picket fence into ICANN’s mission provides some measure of predictability and stability that businesses like contracted parties need. This sets up a unique situation whereby a contracting
party is legally bound to terms which may not be consented to. <o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">Picket fence circumscribes ICANN’s authority with regards to names.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">Effective policy-making requires that affected stakeholders be able to participate, hence the structure of the GNSO Council.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">In addition to examples of what is within the picket fence, the base registry and registrar agreements also contain certain examples of matters outside of the
picket fence, such as pricing, fees paid to ICANN, etc. <o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">Picket fence concept is inherently based on consensus-driven process. There is more predictability in the sense that there is more discussion and understanding
of the different positions, that you may not get in a voting model. Consensus provides balance against capture. It is also the tradition by which decisions are made in the technical community.
<o:p></o:p></span></i></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo1"><i><span style="font-size:11.0pt">ICANN Board has committed to tying decisions and actions explicitly to relevant Bylaws provisions that empower the Board to act or not act for any decisions going
forward. SO/ACs will be encouraged to adopt this approach going forward.<o:p></o:p></span></i></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt">Marika Konings<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Email: <a href="mailto:marika.konings@icann.org">
<span style="color:#0563C1">marika.konings@icann.org</span></a> <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt"> <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Follow the GNSO via Twitter @ICANN_GNSO<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Find out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso"><span style="color:#0563C1">interactive courses</span></a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers"><span style="color:#0563C1">GNSO
Newcomer pages</span></a>. <o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>