<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18999">
<STYLE>@font-face {
        font-family: Wingdings;
}
@font-face {
        font-family: Cambria Math;
}
@font-face {
        font-family: Cambria;
}
@font-face {
        font-family: Calibri;
}
@font-face {
        font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
        MARGIN: 0in 0in 0pt; FONT-FAMILY: "Cambria","serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
        MARGIN: 0in 0in 0pt; FONT-FAMILY: "Cambria","serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
        MARGIN: 0in 0in 0pt; FONT-FAMILY: "Cambria","serif"; FONT-SIZE: 12pt
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
        FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 12pt; MARGIN-RIGHT: 0in; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
P.MsoListParagraph {
        MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Cambria","serif"; FONT-SIZE: 12pt; mso-style-priority: 34
}
LI.MsoListParagraph {
        MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Cambria","serif"; FONT-SIZE: 12pt; mso-style-priority: 34
}
DIV.MsoListParagraph {
        MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Cambria","serif"; FONT-SIZE: 12pt; mso-style-priority: 34
}
P.headlinemeta {
        FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 12pt; MARGIN-RIGHT: 0in; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-style-name: headlinemeta
}
LI.headlinemeta {
        FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 12pt; MARGIN-RIGHT: 0in; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-style-name: headlinemeta
}
DIV.headlinemeta {
        FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 12pt; MARGIN-RIGHT: 0in; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-style-name: headlinemeta
}
SPAN.apple-style-span {
        mso-style-name: apple-style-span
}
SPAN.author {
        mso-style-name: author
}
SPAN.EmailStyle22 {
        FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle23 {
        FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle24 {
        FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
        FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
        page: WordSection1
}
OL {
        MARGIN-BOTTOM: 0in
}
UL {
        MARGIN-BOTTOM: 0in
}
</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 dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><FONT
color=#000000><FONT face="Times New Roman"><FONT size=4><SPAN
class=586060519-28012011><FONT color=#0000ff>I'd like to differ on a couple of
points. I don't think it's difficult to determine what is a
brand. Brands are trademarks. Ownership of a federal
trademark registration and other global trademark registrations
are not only proof of a "brand" but confer nationwide exclusive rights to
use that mark for the goods and services in the application. However,
I would distinguish that the "brand" be a trademark that is registered and used
for goods and services unrelated to registry services. The
mark should be used in commerce for unrelated goods and services well
before that brand ever gets awarded a TLD. It's my
understanding that the BC has long opposed the idea that a TLD alone can become
a brand -- only an existing trademark, such as CANON for cameras could
be recognized as a brand
TLD. </FONT></SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><FONT
color=#000000><FONT face="Times New Roman"><FONT size=4><SPAN
class=586060519-28012011><FONT
color=#0000ff></FONT></SPAN></FONT></FONT></FONT></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><FONT
color=#000000><FONT face="Times New Roman"><FONT size=4><SPAN
class=586060519-28012011><FONT color=#0000ff>BTW, it's my understanding
that certain TLD applicants are inappropriately trying to lock up
trademark rights in their "brands" at the PTO before ICANN has even awarded
them a contract to operate the TLD. Whether ICANN awards
them a contract or not, the PTO has rule that in the Trademark
Manual of Examining Procedure confirming that registry services alone are not
registrable as trademarks. When you apply for a trademark registration,
you need to sign a declaration under penalty of perjury that you either have a
bona fide intent to use the mark or have rights to use the mark in
commerce. I don't see how anyone can sign this declaration in good faith
given the fact that ICANN has not yet considered their application, several may
be applying for the same TLD and the PTO's rule that such services are
unregistrable. </FONT></SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><FONT
color=#000000><FONT face="Times New Roman"><FONT color=#0000ff size=4><SPAN
class=586060519-28012011></SPAN></FONT></FONT></FONT></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><FONT
color=#000000><FONT face="Times New Roman"><FONT color=#0000ff size=4><SPAN
class=586060519-28012011></SPAN></FONT></FONT></FONT></FONT><FONT color=#0000ff
size=2 face=Arial><FONT color=#000000><FONT face="Times New Roman"><FONT
color=#0000ff size=4><SPAN
class=586060519-28012011></SPAN></FONT></FONT></FONT></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><FONT
color=#000000><FONT face="Times New Roman"><FONT color=#0000ff size=4><SPAN
class=586060519-28012011>Sarah</SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV align=left><FONT size=2 face=Arial><BR><BR><FONT color=#000080>Sarah B.
Deutsch <BR>Vice President & Associate General Counsel <BR>Verizon
Communications <BR>Phone: 703-351-3044 <BR>Fax: 703-351-3670
</FONT><BR></FONT></DIV>
<DIV> </DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> owner-bc-gnso@icann.org
[mailto:owner-bc-gnso@icann.org] <B>On Behalf Of </B>Mike
Rodenbaugh<BR><B>Sent:</B> Friday, January 28, 2011 12:27 PM<BR><B>To:</B>
bc-gnso@icann.org<BR><B>Subject:</B> RE: [bc-gnso] pressing the BC
recommendations for dot-brand TLDs<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I
generally support Berry’s comments too. I appreciate the effort to devise
clear rules. I offer a few more thoughts fwiw.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I
have argued that all TLDs are in fact brands of their registries, as by
definition they are indicators of source of the registry service. Also I
can envision lots of companies, including current registrars and registries, who
might benefit from the SRSU model as Berry exemplifies it. I envision that
many of them who essentially will allow use of domains to the public (i.e. to
all Facebook members, in Berry’s example) would have robust content-monitoring
systems, and would see benefit to exercising quality control over how all
domains within the TLD are used. The ‘types’ of TLDs that could employ
models like this may extend well beyond what we think of ‘dotBrands’ today (i.e.
.canon and .facebook). So long as the TLD operator is ultimately
responsible as the registrant as well as the ‘registration authority’, from the
BC’s perspective these models should be encouraged. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">But
these models may be disruptive to the status quo in ICANNland, and so did not
get very far in the Vertical Integration working group. With the Board’s
resolution on VI, it seemed that the SRSU and other innovative models were being
encouraged. Yet now some elements of the “Code of Conduct” are being
proposed as a tool to essentially restrict business models like SRSU, in favor
of the incumbent ICANN contracting parties and those who have designed their TLD
models around the status quo. The BC should fight against that, as our
support of the newTLD program has always been founded on the innovative,
competitive new uses of the DNS that are envisioned (and those that have not
been envisioned).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Best,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Mike<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Mike
Rodenbaugh<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">RODENBAUGH
LAW<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">tel/fax:
+1 (415) 738-8087<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><A
href="http://rodenbaugh.com/"><SPAN
style="COLOR: blue">http://rodenbaugh.com</SPAN></A><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <B>On Behalf Of
</B>jarkko.ruuska@nokia.com<BR><B>Sent:</B> Friday, January 28, 2011 5:30
AM<BR><B>To:</B> berrycobb@infinityportals.com;
bc-gnso@icann.org<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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Dear
all,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">BR,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">-jr<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Thank
you Steve for updating the BC. Adding to Steve’s
points......<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The
following is how I view the possible scope of a “Single Registrant”
TLD:<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The
entity can ”warehouse” domains because it owns the domains<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The
entity is required to provide Zone File Access for monitoring and
compliance<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I
am sure there are other elements to define the boundary
here….<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l1 level1 lfo2"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d; FONT-SIZE: 11pt"><SPAN
style="mso-list: Ignore">·<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Thank
you, B<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Berry
Cobb<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Infinity
Portals LLC<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">berrycobb@infinityportals.com<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">http://infinityportals.com<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">720.839.5735<o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">To:
BC Members<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Re:
ICANN Con call today regarding Registry
Contracts<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Berry
Cobb and Jon Nevett were also on the call.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN class=apple-style-span><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">I gave
the BC recommendation to insert this clause into the Registry Code of
Conduct:</SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN class=apple-style-span><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"> </SPAN></SPAN><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p></o:p></SPAN></P></DIV>
<BLOCKQUOTE style="MARGIN: 5pt 0in 5pt 30pt">
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV></BLOCKQUOTE>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Will
discuss more on our Monday call, I hope.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">--
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Steve
DelBianco<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Executive
Director<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">NetChoice<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">+1.202.420.7482
<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><SPAN class=apple-style-span><B><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 12.5pt"><A
title="Permanent Link to Temporary Drafting Group Work Session on New gTLD Base Registry Agreement Issues – To Be Held 27 January 2011"
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/">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">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: 0in" type=disc>
<LI style="COLOR: black; mso-list: l0 level1 lfo5" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 8.5pt">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 style="COLOR: black; mso-list: l0 level1 lfo5" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 8.5pt">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 style="COLOR: black; mso-list: l0 level1 lfo5" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 8.5pt">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 style="COLOR: black; mso-list: l0 level1 lfo5" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 8.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">Results:</SPAN><SPAN
style="COLOR: black"><o:p></o:p></SPAN></P>
<P><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">Session:</SPAN><SPAN
style="COLOR: black"><o:p></o:p></SPAN></P>
<P><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">Participation:</SPAN><SPAN
style="COLOR: black"><o:p></o:p></SPAN></P>
<P><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 8.5pt">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-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P></DIV></DIV></DIV></DIV></DIV></BODY></HTML>