<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Cambria;
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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Cambria","serif";}
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
{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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Cambria","serif";}
p.headlinemeta, li.headlinemeta, div.headlinemeta
{mso-style-name:headlinemeta;
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.apple-style-span
{mso-style-name:apple-style-span;}
span.author
{mso-style-name:author;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:231699984;
mso-list-template-ids:1117956924;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:550465535;
mso-list-template-ids:-1207541686;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:1770157041;
mso-list-type:hybrid;
mso-list-template-ids:-1897877170 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
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=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear all,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Just wanted to express my support for Berry’s definition
of a Single Registrant TLD. In my opinion this is a simple enough (and probably
the only feasible) way to define such a thing. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>BR,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-jr<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>ext
Berry Cobb<br>
<b>Sent:</b> 28. tammikuuta 2011 2:12<br>
<b>To:</b> 'bc - GNSO list'<br>
<b>Subject:</b> RE: [bc-gnso] pressing the BC recommendations for dot-brand
TLDs<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thank you Steve for updating the BC. Adding to
Steve’s points......<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The reason ICANN Staff, experienced Registry Operators, &
some other stakeholders will not sign on for “carve outs” is
because there is NO BRIGHT LINE DEFINTION FOR A BRAND. In the context of
TLDs what is a BRAND? Is it because they are Fortune 1000 company?
Do they own Trademarks in the USA or Europe? Do they earn over $2 billion
dollars a year in revenue? Where do we start to draw the line? If
some sort of bright line exists, then please share. If it exists then I
doubt we would see the pushback experienced today or during the VI WG.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In my opinion, if the BC and IPC ever expect any headway
regarding the “dot-brand” concept, then we MUST stop using
“DOT-BRAND.” Within my short ICANN career, one thing
I’ve noticed is that a BRAND is a loaded and charged word among the
community. If the BC supports “carve outs,” then the case
must be presented very specifically and using BRAND is not the way
forward. Framing this concept should embrace the use of “Single
Registrant” only. Notice how Single User & Multiple User is
omitted? The main reason SRSU gained support during VI is only because of
the Single Registrant component and it’s limitations in how domains were
registered and used. Anything beyond SRSU was poking a stick at a
tiger. I remind everyone the reasoning for SRSU & SRMU is only
because BRAND could not be defined.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The following is how I view the possible scope of a
“Single Registrant” TLD:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Any 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup>,5<sup>th</sup>
level domains registered are owned and operated only the by the entity that
owns the TLD<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>All WHOIS information for registered 2<sup>nd</sup> level
domains reflect the entity that owns the TLD<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If the entity chooses to deploy content or allow use by others
external to them, the entity is still responsible or liable for that domain and
its content<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The entity may register its own domains without equivalent
access to other Registrars (RAA concepts should still be used, but ZERO
registration fees to ICANN)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The entity may deploy and use its 2<sup>nd</sup> level domains
how it sees fit and the Reserve Names list no longer applies<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The entity can ”warehouse” domains because it owns
the domains<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The entity is required to provide Zone File Access for
monitoring and compliance<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I am sure there are other elements to define the boundary
here….<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Therefore, much of the Code of Conduct is meaningless to a
“Single Registrant” TLD<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So, using the Cannon example from Steve below, the above
“Single Registrant” concepts can satisfy the “carve
outs” defined by the BC. If Cannon chose to register 2<sup>nd</sup>
level domains to their customers, partners & vendors, but it is still
designated as the Registrant, then the Single Registrant carve outs still
apply. What about the Facebook use case? The one batted around most
often is berrycobb.facebook. If Facebook chooses to register and supply
me a domain and the defined “Registrant” remains as Facebook and
Facebook is willing to take on the risk for the content I deploy on
berrycobb.facebook, then I imagine the stakeholders listed above will probably
not have much issue with “Single Registrant carve outs.” This
is the essence to “Single Registrant, Single User” concept.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Conversely, any hope for consensus in VI quickly broke down with
a use case for “Single Registrant Multiple Users.” Using
Facebook as an example again…..if FB chose to allow me to register
berrycobb.facebook, but instead I am designated as the Registrant, Facebook now
competes head to head with other Registrars & Registries in the domain
registration business. This is the crux of the debate. Where does
one draw the line as Facebook being a social media “BRAND” vs.
Facebook a social media “BRAND” that also chooses to register
domains and compete in the domain market. If any exceptions or carve outs
are given to FB because they are designated a “BRAND”, then
wouldn’t other entities competing for the same registration dollar be at
a competitive disadvantage because they are bound by the full extent of the
Code of Conduct? <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Most will recall that I did not support the sections of the BC
Position that called for these SR exceptions, because it did not provide a
bright line solution for the community. Rather, it called for nebulous,
self-serving, carve outs that only provided confusion. I hope we do not
repeat the same mistake for future BC position statements. I’m
starting to believe that no position is better than a half-baked one.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>With all this said however, I CAN support a “Single
Registrant” concept, just not as we have it defined in our position
today. There is no doubt that without some sort of designation for single
registrant TLDs the Code of Conduct will certainly interfere with operations
and may in fact deter some applications. The challenge is that the
“Single Registrant” type of TLD is NOT defined in the
Guidebook. Until it is, then any exceptions will not make the next
AGB. I am willing to join a team of BC members to develop a specific
proposal that not only benefits the BC, but benefits the entire community by
relieving confusion.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If we expect any momentum, the BC must come together and define
a reasonable solution that ICANN Staff and Community can embrace. I am
sure my fast-run scope definition above has several holes. So I welcome
contributions to fill them. Gripes, complaints, & moans are also
welcome if you feel I am way off base.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thank you, B<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Berry Cobb<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Infinity Portals LLC<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>berrycobb@infinityportals.com<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>http://infinityportals.com<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>720.839.5735<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>Steve
DelBianco<br>
<b>Sent:</b> Thursday, January 27, 2011 12:11 PM<br>
<b>To:</b> 'bc - GNSO list'<br>
<b>Subject:</b> [bc-gnso] pressing the BC recommendations for dot-brand TLDs<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>To: BC Members<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>Re: ICANN Con call today regarding Registry Contracts<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>I joined a large con call today hosted by ICANN, to discuss new
gTLD registy agreement. (see description at bottom of this note)<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>Berry Cobb and Jon Nevett were also on the call.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>When we got to the Registry <b>Code of Conduct</b>, ICANN staff
mentioned they had received many comments on how this would or would not work
for dot-brand registries. <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>At that point I brought up the BC concerns expressed in our
Guidebook comments filed 6-Dec in Cartagena.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>I used the example of Canon, since they have said they may pursue
a dot-brand. <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>I said Canon might want to operate its own Registrar and restrict
registrations to its own operating divisions, like copiers.canon
and cameras.canon <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>And Canon might want to manage a big sub-domain of photographers
using Canon cameras, like [name].photos.canon<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>I said The Code of Conduct should not restrict dot-brands from
using an owned or closely affiliated registrar to register and manage names
that it controls. (e.g., for divisions, product lines, <span
class=apple-style-span>locations, customers, affiliates, etc. )</span></span><span
style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:black'>I gave the BC
recommendation to insert this clause into the Registry Code of Conduct:</span></span><span
style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:black'> </span></span><span
style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0cm;
margin-bottom:5.0pt'>
<div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>4. Nothing set forth in articles 1, 2, or 3 shall apply to a
single-registrant ('dot brand') Registry Operator acting with respect to user
data that is under its ownership and control, or with respect to conduct
reasonably necessary for the management, operations and purpose of the TLD.</span></b><span
style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
</blockquote>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>An experienced registry operator on the call said our 'carve out'
would allow 'gaming' and abuse. (they say that a lot).<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>ICANN Staff is very resistant to any 'carve-out' for
dot-brands. They oppose any exception (or even a definition) for
dot-brand. <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>Craig Schwartz said ICANN didn't want to get in the business of
monitoring Canon's copier business. ( I think that was the point of our
recommendation — we don't want ICANN getting involved in how a dot-brand
allocates registrations to entities it owns or controls)<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>Will discuss more on our Monday call, I hope.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>-- <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>Steve DelBianco<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>Executive Director<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>NetChoice<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><a href="http://www.NetChoice.org">http://www.NetChoice.org</a>
and <a href="http://blog.netchoice.org">http://blog.netchoice.org</a> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'>+1.202.420.7482 <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-width:initial;border-color:initial'>
<p class=MsoNormal><span class=apple-style-span><b><span style='font-size:12.5pt;
font-family:"Calibri","sans-serif";color:black'><a
href="http://blog.icann.org/2011/01/temporary-drafting-group-work-session-on-new-gtld-base-registry-agreement-issues-%e2%80%93-to-be-held-27-january-2011/"
title="Permanent Link to Temporary Drafting Group Work Session on New gTLD Base Registry Agreement Issues – To Be Held 27 January 2011">Temporary
Drafting Group Work Session on New gTLD Base Registry Agreement Issues –
To Be Held 27 January 2011</a></span></b></span><span style='font-family:"Times New Roman","serif";
color:black'><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=headlinemeta><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";
color:black'>by <span class=author>Craig Schwartz</span> on January
14, 2011</span><span style='color:black'><o:p></o:p></span></p>
<p><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";color:black'>The
Temporary Drafting Group will hold a teleconference on 27 January 2011. The
issues open for drafting/discussion during the call will include:</span><span
style='color:black'><o:p></o:p></span></p>
<ul style='margin-top:0cm' type=disc>
<li class=MsoNormal style='color:black;mso-list:l1 level1 lfo5'><span
style='font-size:8.5pt;font-family:"Calibri","sans-serif"'>Suggestions for
additional language for Specification 9 (the Registry Code of Conduct)</span><span
style='font-family:"Times New Roman","serif"'><o:p></o:p></span></li>
<li class=MsoNormal style='color:black;mso-list:l1 level1 lfo5'><span
style='font-size:8.5pt;font-family:"Calibri","sans-serif"'>Proposed
modifications to conditions related to the termination of a registry
services agreement</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></li>
<li class=MsoNormal style='color:black;mso-list:l1 level1 lfo5'><span
style='font-size:8.5pt;font-family:"Calibri","sans-serif"'>Suggestions for
clarifications to provision requiring advance notice of registry price
increases</span><span style='font-family:"Times New Roman","serif"'><o:p></o:p></span></li>
<li class=MsoNormal style='color:black;mso-list:l1 level1 lfo5'><span
style='font-size:8.5pt;font-family:"Calibri","sans-serif"'>Concepts for
continued registry operations instrument to provide continuity of services</span><span
style='font-family:"Times New Roman","serif"'><o:p></o:p></span></li>
</ul>
<p><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";color:black'>Results:</span><span
style='color:black'><o:p></o:p></span></p>
<p><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";color:black'>This
is not a formal public consultation, but is intended to inform drafting which
might make up a later public consultation. Any results from the Temporary
Drafting Group will be included in documents that will be posted for public
comment. No results from the Group will necessarily be used in any agreement
drafts, but inputs from the Group will be considered by the ICANN Staff in
making recommendations relating to questions discussed or posed to the Group.</span><span
style='color:black'><o:p></o:p></span></p>
<p><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";color:black'>Session:</span><span
style='color:black'><o:p></o:p></span></p>
<p><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";color:black'>This
third Temporary Drafting Group session will be held via teleconference on 27
January 2011 at 18.00 UTC (<a href="http://timeanddate.com/s/1xxz">http://timeanddate.com/s/1xxz</a>),
and is scheduled to last for 120 minutes.</span><span style='color:black'><o:p></o:p></span></p>
<p><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";color:black'>Participation:</span><span
style='color:black'><o:p></o:p></span></p>
<p><span style='font-size:8.5pt;font-family:"Calibri","sans-serif";color:black'>The
Temporary Drafting Group was formed in early 2010 and announced in a 28 April
2010 <a
href="http://blog.icann.org/2010/04/temporary-drafting-group-work-session-on-new-gtld-implementation-issues-%E2%80%93-to-be-held-3-may-2010/">blog</a> post.
If you would like to participate, please submit your name to <a
href="mailto:TDG-Legal@ICANN.org">TDG-Legal@ICANN.org</a>, and we will provide
you with information for the call.</span><span style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif";
color:black'> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>