<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi,</div><div><br></div><div>Apologies for getting back to you all this late in the discussion. There was a very brief discussion on the introduction of Specification 13 on the NCSG list a few weeks ago, but the NCSG has not reached any formal position on the matter.</div><div><br></div><div>The discussion that did take place is however pretty consistent with most of what has been said here. Although there is some sympathy with the substantive implications of Spec 13, it does seem for all intents and purposes inconsistent with policy recommendation 19 and the existing Registry Agreement (regarding registries’ requirement to not discriminate between ICANN accredited registrars).</div><div><br></div><div>Personally, I do have a question regarding Specification 9; the Registry Operator Code of Conduct. Specification 9 does have a similar requirement stating:</div><div><br></div><div><div style="font-family: TrebuchetMS;"><i style="font-size: 12px;">“1. In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to:</i></div><div style="font-family: TrebuchetMS;"><i style="font-size: 12px;"><br></i></div><div style="font-family: TrebuchetMS; margin: 0px;"><i style="font-size: 12px;">a. directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; …,”</i></div></div><div><br></div><div>There is also a mechanism for registries to be granted exemptions from this point, specifically as an item in the code of conduct. Is this exemption meant to influence considerations on contractual requirements in the entire agreement? I’m honestly not sure what role Specification 9 is meant to play.</div><div><br></div><div>Finally…, if I understood correctly, during the last Council meeting, Alan made a point I personally find to be a pretty good one. If Specification 13 is consistent with previous policy recommendations, it would be unnecessary to introduce it at this point. The apparent need to introduce it now suggests that it is a policy that was either not considered during the process leading up to the GNSO recommendations, or actually inconsistent with the policy recommendations made. In either case (IMHO), I would support a position requiring the appropriate process be followed.</div><div><br></div><div>Thanks.</div><div><br></div><div>Amr</div><br><div><div>On Apr 28, 2014, at 11:08 AM, Volker Greimann <<a href="mailto:vgreimann@key-Systems.net">vgreimann@key-Systems.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
Dear council-members,<br>
<br>
after extensive discussion of the question put before us, the RrSG
has likewise found this excemption to be inconsistent with both the
language as well as with the spirit of the recommendation.<br>
<br>
The question we have been asked is not whether we like the proposed
exemption or can live with it, but rather a very simple one: Is the
proposed incorporation of an ability to restrict nondiscriminatory
registrar access to dotBrand TLDs is not consistent with the intent
and wording of Recommendation 19, or is it not. The recommendation
explicitly states that "Registries (...) may not discriminate among
(ICANN) accredited registrars". In other words, the language of the
Recommendation 19 contradicts the proposed exemption. <br>
<br>
Therefore, to find the additional language to be consistent with the
recommendation requires substantial arguments to that effect that
would allow such an interpretation. To find it consistent because
one likes the result or can live with the result does not fulfill
this requirement. For such cases where implementation would conflict
with existing policy, further policy work adjusting or confirming
the Policy Recommendation is required. The GNSO Council should take
the lead in initiating this policy work.<br>
<br>
Beyond the grammatical inconsistency of the Recommendation, the
intent of the Recommendation also indicates inconsistency.<br>
<br>
As detailed in the final report on the Introduction of New Generic
Top Level Domains, the recommendation was supported by all GNSO
Constituencies and Mrs Doria. According to the recollections of
members of the new gTLD policy committee at the time the
Recommendation was agreed upon, the concept of restricting registrar
access was discussed in the context of community TLDs, which are in
many ways similar to dotBrands. As registries have the ability under
the Registry Agreement to restrict registrar access to their TLDs by
establishing reasonable, nondiscriminatory accreditation criteria,
it was ultimately agreed that discrimintation between registrars
should not be permitted.<br>
<br>
In fact, the only public comment with regard to this recommendation
came from the RyC, which was concerned that small, specialized
registries may not be able to find a registrar to carry them. Note
that this concern deals with a completely different problem. This
concern led to the Vertical Integration Working group and the
subsequent board decision allowing vertical integration. The idea of
allowing only a few registrars does not appear in the Final Report.<br>
<br>
Finally, as registrants, dotBrands are perfectly free to
discriminate between registrars. The Recommendation only deals with
registries. By establishing certain registration requirements and
policies, registries can further eliminate the ability of registrars
to provide registry services beyond the eligible circle of
registrants. <br>
<br>
Best regards,<br>
<br>
Volker Greimann<br>
<br>
<div class="moz-cite-prefix">Am 26.04.2014 16:54, schrieb Bret
Fausett:<br>
</div>
<blockquote cite="mid:5AE5CF8A-2C2A-4771-9861-BE79B5FC3CE7@nic.sexy" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Feedback:
<div><br>
</div>
<div>What we have been asked by the Board is to "advise ICANN as
to whether the GNSO Council believes that this additional
provision is inconsistent with the letter and intent
of GNSO Policy Recommendation 19 on the Introduction of New
Generic Top-Level Domains.”</div>
<div><br>
</div>
<div>Policy Recommendation 19 reads: "Registries must use only
ICANN accredited registrars in registering domain names and may
not discriminate among such accredited registrars.” <a moz-do-not-send="true" href="http://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm">http://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm</a>
The discussion section of this policy recommendation does not
make for any exceptions for brands.</div>
<div><br>
</div>
<div>Plainly, as I read the provisions of the .BRAND Specification
13, it is “inconsistent with the letter and intent of GNSO
Policy Recommendation 19.” </div>
<div><br>
</div>
<div>Now, I personally happen to think that the draft
Specification 13 for .BRAND TLDs is a tightly drafted,
well-considered exception for a specialized type of TLD that was
not being considered carefully when Recommendation 19 was
prepared. BUT, it is definitely inconsistent with the policy
recommendation we made in August, 2007. </div>
<div><br>
</div>
<div>Let’s think about what this means.</div>
<div><br>
<div apple-content-edited="true">
<div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">--<br>
Bret Fausett, Esq. • General Counsel, Uniregistry, Inc. <br>
12025 Waterfront Drive, Suite 200 • Playa Vista, CA
90094-2536<br>
310-496-5755 (T) • 310-985-1351 (M) • <a moz-do-not-send="true" href="mailto:bret@uniregistry.com">bret@uniregistry.com</a><br>
— — — — — <br>
<br>
<br>
<br>
</div>
</div>
<br>
<div>
<div>On Apr 26, 2014, at 5:14 AM, Thomas Rickert <<a moz-do-not-send="true" href="mailto:rickert@anwaelte.de">rickert@anwaelte.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;">Jonathan,
<div>I do hope to get more feedback. So far, I do not
really have information to act on, but I am standing by
to do what is necessary to meet the deadline.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Thomas</div>
<div><br>
<div>
<div>Am 26.04.2014 um 10:29 schrieb Jonathan Robinson
<<a moz-do-not-send="true" href="mailto:jrobinson@afilias.info" style="color:
purple; text-decoration: underline;">jrobinson@afilias.info</a>>:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div link="blue" vlink="purple" lang="EN-GB">
<div class="WordSection1" style="page:
WordSection1;">
<div style="margin: 0cm 0cm 0.0001pt; font-size:
12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family:
Calibri, sans-serif; color: rgb(31, 73,
125);">Thanks Thomas,<o:p></o:p></span></div><p class="MsoNormal" style="margin: 0cm 0cm
0.0001pt; font-size: 12pt; font-family: 'Times
New Roman', serif;"><span style="font-size:
11pt; font-family: Calibri, sans-serif;
color: rgb(31, 73, 125);"> </span></p>
<div style="margin: 0cm 0cm 0.0001pt; font-size:
12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family:
Calibri, sans-serif; color: rgb(31, 73,
125);">You will have seen that the motion
deadline is Monday 28<sup>th</sup><span class="Apple-converted-space"> </span>23h59
UTC so, assuming we will meet the 45 day
deadline, we will need a motion on Monday.<o:p></o:p></span></div><p class="MsoNormal" style="margin: 0cm 0cm
0.0001pt; font-size: 12pt; font-family: 'Times
New Roman', serif;"><span style="font-size:
11pt; font-family: Calibri, sans-serif;
color: rgb(31, 73, 125);"> </span></p>
<div style="margin: 0cm 0cm 0.0001pt; font-size:
12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family:
Calibri, sans-serif; color: rgb(31, 73,
125);">Let’s hope we can do that in such a
way as to reflect the feedback you have and
retain flexibility to modify (if necessary)
as we receive further feedback.<o:p></o:p></span></div><p class="MsoNormal" style="margin: 0cm 0cm
0.0001pt; font-size: 12pt; font-family: 'Times
New Roman', serif;"><span style="font-size:
11pt; font-family: Calibri, sans-serif;
color: rgb(31, 73, 125);"> </span></p>
<div style="margin: 0cm 0cm 0.0001pt; font-size:
12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family:
Calibri, sans-serif; color: rgb(31, 73,
125);">Let’s you and I talk on Monday.<o:p></o:p></span></div><p class="MsoNormal" style="margin: 0cm 0cm
0.0001pt; font-size: 12pt; font-family: 'Times
New Roman', serif;"><span style="font-size:
11pt; font-family: Calibri, sans-serif;
color: rgb(31, 73, 125);"> </span></p>
<div style="margin: 0cm 0cm 0.0001pt; font-size:
12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family:
Calibri, sans-serif; color: rgb(31, 73,
125);">Jonathan<o:p></o:p></span></div><p class="MsoNormal" style="margin: 0cm 0cm
0.0001pt; font-size: 12pt; font-family: 'Times
New Roman', serif;"><span style="font-size:
11pt; font-family: Calibri, sans-serif;
color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border-style: solid none none;
border-top-color: rgb(181, 196, 223);
border-top-width: 1pt; padding: 3pt 0cm
0cm;">
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><b><span style="font-size:
10pt; font-family: Tahoma,
sans-serif;" lang="EN-US">From:</span></b><span style="font-size: 10pt; font-family:
Tahoma, sans-serif;" lang="EN-US"><span class="Apple-converted-space"> </span>Thomas
Rickert [<a moz-do-not-send="true" href="mailto:rickert@anwaelte.de" style="color: purple; text-decoration:
underline;">mailto:rickert@anwaelte.de</a>]<span class="Apple-converted-space"> </span><br>
<b>Sent:</b><span class="Apple-converted-space"> </span>25
April 2014 20:38<br>
<b>To:</b><span class="Apple-converted-space"> </span>GNSO
Council List<br>
<b>Subject:</b><span class="Apple-converted-space"> </span>Fwd:
[council] A way forward on the
Specification 13 question<o:p></o:p></span></div>
</div>
</div>
<div style="margin: 0cm 0cm 0.0001pt; font-size:
12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div>
<div style="margin: 0cm 0cm 0.0001pt; font-size:
12pt; font-family: 'Times New Roman', serif;">All,<o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;">this is a gentle reminder to
provide me with preliminary feedback. The
motions and documents deadline is
approaching rapidly and I have only received
one response from the registrars so far. <o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;">Also, I have reached out to
Marilyn Cade (CBUC), Tony Holmes (ISPC),
Kristina Rosette (IPC), Robin Gross (NCUC),
Bruce Tonkin (Registrars) and Ken Stubbs
(Registries) as they were listed in the
final report of the PDP to cover their
respective groups and since they hopefully
have first-hand information on the
discussions at the time. More people such as
Avri, Bret and Alan are still here - please
to chime in and respond. <o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;">Thanks and kind regards,<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;">Thomas <o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><o:p> </o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;">Anfang der
weitergeleiteten Nachricht:<o:p></o:p></div>
</div><p class="MsoNormal" style="margin: 0cm 0cm
12pt; font-size: 12pt; font-family: 'Times
New Roman', serif;"><o:p> </o:p></p>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><b><span style="font-family: Helvetica,
sans-serif;">Von:<span class="Apple-converted-space"> </span></span></b><span style="font-family: Helvetica,
sans-serif;">Thomas Rickert <<a moz-do-not-send="true" href="mailto:rickert@anwaelte.de" style="color: purple;
text-decoration: underline;">rickert@anwaelte.de</a>></span><o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><b><span style="font-family: Helvetica,
sans-serif;">Betreff: Aw: [council]
A way forward on the Specification
13 question</span></b><o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><b><span style="font-family: Helvetica,
sans-serif;">Datum:<span class="Apple-converted-space"> </span></span></b><span style="font-family: Helvetica,
sans-serif;">22. April 2014 14:40:58
MESZ</span><o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><b><span style="font-family: Helvetica,
sans-serif;">An:<span class="Apple-converted-space"> </span></span></b><span style="font-family: Helvetica,
sans-serif;"><a moz-do-not-send="true" href="mailto:jrobinson@afilias.info" style="color: purple;
text-decoration: underline;">jrobinson@afilias.info</a></span><o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><b><span style="font-family: Helvetica,
sans-serif;">Kopie:<span class="Apple-converted-space"> </span></span></b><span style="font-family: Helvetica,
sans-serif;">GNSO Council List <<a moz-do-not-send="true" href="mailto:council@gnso.icann.org" style="color: purple;
text-decoration: underline;">council@gnso.icann.org</a>></span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;"><o:p> </o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times New
Roman', serif;">All,<o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;">thanks to Jonathan
for putting together and sending out
the below message. <o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;"><o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;">I am more than
happy to assist with making sure we
get an answer prepared in time. <o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;"><o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;">Can I ask
Councillors to get back to me offlist
(in order not to swamp the list) with
a status of the discussions with your
respective groups? Certainly, one
response per group is sufficient. <o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;"><o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;">If there is
anything I can help with to facilitate
your discussions, please let me know. <o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;"><o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;">The earlier I am
provided with information on what
direction your answers will take, the
sooner I will be able to draft a
motion and a letter to the NGPC for
your review.<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;"><o:p> </o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;">Thanks,<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;">Thomas<o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm 0.0001pt;
font-size: 12pt; font-family: 'Times
New Roman', serif;"><o:p> </o:p></div>
<div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;">Am 10.04.2014 um 19:10
schrieb Jonathan Robinson <<a moz-do-not-send="true" href="mailto:jrobinson@afilias.info" style="color: purple;
text-decoration: underline;">jrobinson@afilias.info</a>>:<o:p></o:p></div>
</div><p class="MsoNormal" style="margin:
0cm 0cm 12pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><o:p> </o:p></p>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">All,</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">Following on from
previous dialogue and the
Council meeting today, it seems
to me that the way forward is to
focus as closely as possible on
the question being asked and to
make every attempt to respond in
a timely and effective manner.</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">This means that,
assuming it is required, a
motion to be voted on needs to
be submitted to the Council by
28 April for consideration at
the 8 May 2014 meeting.</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">We are being asked
(full letter attached for
reference) to</span><o:p></o:p></div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"> <o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt
20.25pt; font-size: 11pt;
font-family: Calibri, sans-serif;
text-indent: -18pt;"><span>1.<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span>…
advise ICANN as to whether the
GNSO Council believes that this
additional provision is
inconsistent with the letter and
intent of GNSO Policy
Recommendation 19 on the
Introduction of New Generic
Top-Level Domains;<span class="Apple-converted-space"> </span><br>
or<o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt
20.25pt; font-size: 11pt;
font-family: Calibri, sans-serif;
text-indent: -18pt;"><span>2.<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span>advise
ICANN that the GNSO Council needs
additional time for review,
including an explanation as to why
additional time is required.<o:p></o:p></div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 11pt;
font-family: Calibri, sans-serif;"> <o:p></o:p></div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">I believe that the
question to take to your
respective stakeholder groups /
constituencies is therefore:</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">Is this additional
provision inconsistent with the
letter and intent of GNSO Policy
Recommendation 19?</span><o:p></o:p></div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">It will be helpful
to have as clear as possible an
answer as soon as possible along
the following lines:</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm 0.0001pt
36pt; font-size: 12pt;
font-family: 'Times New Roman',
serif; text-indent: -18pt;"><span style="font-family: Symbol;"><span>·<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">No. It is not
inconsistent (… with the letter
and intent …).<br>
and</span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt
36pt; font-size: 12pt;
font-family: 'Times New Roman',
serif; text-indent: -18pt;"><span style="font-family: Symbol;"><span>·<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">Possibly, an
explanation as to why it is not
inconsistent.<br>
and</span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt
36pt; font-size: 12pt;
font-family: 'Times New Roman',
serif; text-indent: -18pt;"><span style="font-family: Symbol;"><span>·<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">Are there any other
qualifying points that the
Council should make in its
response to the NGPC?</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">OR</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm 0.0001pt
36pt; font-size: 12pt;
font-family: 'Times New Roman',
serif; text-indent: -18pt;"><span style="font-family: Symbol;"><span>·<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">Yes. It is
inconsistent ( … with the letter
and intent … ).<br>
and</span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt
36pt; font-size: 12pt;
font-family: 'Times New Roman',
serif; text-indent: -18pt;"><span style="font-family: Symbol;"><span>·<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">Possibly, an
explanation as to why it is
inconsistent.<br>
and</span><o:p></o:p></div>
<div style="margin: 0cm 0cm 0.0001pt
36pt; font-size: 12pt;
font-family: 'Times New Roman',
serif; text-indent: -18pt;"><span style="font-family: Symbol;"><span>·<span style="font-style: normal;
font-variant: normal;
font-weight: normal;
font-size: 7pt; line-height:
normal; font-family: 'Times
New Roman';"> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">Is there a process
by which the Council could
assist the NGPC in resolving
this issue and in what time
frame?</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><b><u><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">Please can you
all act as quickly as
possible to provide an
answer to the above. The
timing is very tight.</span></u></b><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">We already have an
indication of where the BC &
the IPC stand on this i.e. no,
it is not inconsistent.</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">Someone will need
to lead on drafting a motion
(for submission to the Council
on or before 28 April) and an
associated letter to the NGPC.</span><o:p></o:p></div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">Given the time
constraints, this should
probably take place in parallel
with the consultation work.</span><o:p></o:p></div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><b><u><span style="font-size: 11pt;
font-family: Calibri,
sans-serif;">Can we please
have a volunteer to lead
this effort and ensure it
gets done? Thomas?</span></u></b><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">I have tried to
simplify and focus the problem
here in the interest of
providing a representative,
timely and effective response.</span><o:p></o:p></div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">I trust that in
doing so I have not discounted
any material points in the
discussion to date. Please
correct me if I have.</span><o:p></o:p></div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;"> </span><o:p></o:p></div>
</div>
<div style="margin: 0cm 0cm
0.0001pt; font-size: 12pt;
font-family: 'Times New Roman',
serif;"><span style="font-size:
11pt; font-family: Calibri,
sans-serif;">Jonathan</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<br>
<div apple-content-edited="true">
<div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">--<br>
Bret Fausett, Esq. • General Counsel, Uniregistry, Inc. <br>
12025 Waterfront Drive, Suite 200 • Playa Vista, CA 90094-2536<br>
310-496-5755 (T) • 310-985-1351 (M) • <a moz-do-not-send="true" href="mailto:bret@uniregistry.com">bret@uniregistry.com</a><br>
— — — — — <br>
<br>
<br>
<br>
</div>
</div>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net/">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.rrpproxy.net/">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com/">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.brandshelter.com/">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu/">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net/">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.rrpproxy.net/">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com/">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.brandshelter.com/">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu/">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</div>
</blockquote></div><br></body></html>