<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] A way forward on the Specification 13 question
- To: "Winterfeldt, Brian J." <brian.winterfeldt@xxxxxxxxxxxxx>, "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
- Subject: Re: [council] A way forward on the Specification 13 question
- From: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
- Date: Tue, 29 Apr 2014 10:17:56 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=key-systems.net; h=content-type:content-type:in-reply-to:references:subject :subject:to:mime-version:user-agent:from:from:date:date :message-id; s=dkim; t=1398759493; x=1399623493; bh=wSKR3ID3w+uj 1mz9dcR5YmWKWY9r8AKAHuNBGwtI7X0=; b=nAg+8Zb6WX5AllwIxiNswO4MWH37 MEgbQa7vaxZrENe1bd90ZPT6ziNzVZrutXVnzAJdqytpCxMOxyBAYawLRDuu0taV 43BKr90sok9wgZoSh/xrPQZeF/9yAOSa3/KBCrOQm8vfEP0habahB8uM0FY2quBE 2bPIqZ5yfICs8QY=
- In-reply-to: <670C6FC1C06021418D398DFA9BA0FE5901A2EDD8@WAS-US-MAIL-1B.us.kmz.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <670C6FC1C06021418D398DFA9BA0FE5901A2EDD8@WAS-US-MAIL-1B.us.kmz.com>
- Sender: owner-council@xxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Brian,<br>
<br>
I think you misunderstand. We do not assume a Single User-Single
Registrant model in our statements. We are fuly aware that the
Specification allows registrations also to affiliates and certain
licensees. However, by crafting registration policies and
accreditation rules carefully, dotBrand owners can differentiate.
Just look at .WED for a registry almost no registrar is currently
interested in carrying. Further, they can discriminate freely on the
registrant level. <br>
<br>
Therefore, on a purely outcome-oriented level, it is our opinion
that everything that is intended to be achieved by this language can
already be achieved under the current rules. <br>
<br>
Finally, outcomes put aside, on a purely legalistic level, we are
currently looking at contradicting languages. While Rec 19
recommends one thing, the proposed language sets out to create a
loophole for just that thing Rec 19 seeks to prevent. This is
inconsistency per definition, no matter how well-intentioned and
worthwhile the intent is. To go beyond the language of Rec 19,
additional policy work of some form is needed. As many
constituencies have argued for a long time, the council does not
have the role of deciding or setting aside policy on its own, it
merely structures and channels the process.<br>
<br>
Best regards,<br>
<br>
Volker Greimann<br>
<br>
<br>
<div class="moz-cite-prefix">Am 28.04.2014 23:53, schrieb
Winterfeldt, Brian J.:<br>
</div>
<blockquote
cite="mid:670C6FC1C06021418D398DFA9BA0FE5901A2EDD8@xxxxxxxxxxxxxxxxxxxxxxxxx"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Microsoft Theme 2.00" content="Firm 011">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Times New Roman","serif";}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman","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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Times New Roman","serif";
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Times New Roman","serif";
font-weight:bold;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:black;}
span.skypepnhcontainer
{mso-style-name:skype_pnh_container;}
span.skypepnhmark1
{mso-style-name:skype_pnh_mark1;
display:none;}
span.skypepnhprintcontainer1398710629
{mso-style-name:skype_pnh_print_container_1398710629;}
span.baec5a81-e4d6-4674-97f3-e9220f0136c1
{mso-style-name:baec5a81-e4d6-4674-97f3-e9220f0136c1;}
span.skypepnhtextspan
{mso-style-name:skype_pnh_text_span;}
span.skypepnhfreetextspan
{mso-style-name:skype_pnh_free_text_span;}
span.skypepnhmenutollcallcredit2
{mso-style-name:skype_pnh_menu_toll_callcredit2;
font-family:"Helvetica","sans-serif";
color:#939598;
letter-spacing:0pt;
border:none windowtext 1.0pt;
padding:0in;
background:white;
font-weight:normal;
font-style:normal;}
span.skypepnhmenutollfree2
{mso-style-name:skype_pnh_menu_toll_free2;
font-family:"Helvetica","sans-serif";
color:#939598;
display:none;
letter-spacing:0pt;
border:none windowtext 1.0pt;
padding:0in;
background:white;
font-weight:normal;
font-style:normal;}
span.EmailStyle33
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:293485574;
mso-list-template-ids:-155679014;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1137726982;
mso-list-template-ids:-890237100;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:1428572860;
mso-list-type:hybrid;
mso-list-template-ids:-1474418432 67698689 67698691 67698693 67698689
67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
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:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
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:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
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:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:1572154278;
mso-list-template-ids:1930620314;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4
{mso-list-id:2120104113;
mso-list-template-ids:966018906;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l4:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Dear
James and Volker:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Please
let me know if I understand correctly the RrSG position
based your comments below:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l2 level1 lfo2"><!--[if
!supportLists]--><span
style="font-size:10.0pt;font-family:Symbol;color:black"><span
style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">The
proposed amendment to Specification 13 is inconsistent with
policy recommendation 19 because no discrimination between
registrars should be permitted;<o:p></o:p></span></p>
<p class="MsoListParagraph"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l2 level1 lfo2"><!--[if
!supportLists]--><span
style="font-size:10.0pt;font-family:Symbol;color:black"><span
style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Dot
Brands possess the sole ability to execute bulk transfers;
<o:p></o:p></span></p>
<p class="MsoListParagraph"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l2 level1 lfo2"><!--[if
!supportLists]--><span
style="font-size:10.0pt;font-family:Symbol;color:black"><span
style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Dot
Brands, as registrants, are able to choose their own
preferred registrars; and<o:p></o:p></span></p>
<p class="MsoListParagraph"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l2 level1 lfo2"><!--[if
!supportLists]--><span
style="font-size:10.0pt;font-family:Symbol;color:black"><span
style="mso-list:Ignore">·<span style="font:7.0pt
"Times New Roman"">
</span></span></span><!--[endif]--><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Dot
Brands can implement registration policies and requirements
to limit the services provided by registrars to only
eligible registrants.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Forgive
me if my encapsulation is wrong, but if I understand the
RrSG position correctly, then I am concerned that it may
gloss over some important nuances.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">First,
the RrSG position seems based on an assumption that dot
Brand registries will be the sole registrant for bulk
transfer and registrar selection purposes, whereas
Specification Thirteen clearly permits Affiliates and
Trademark Licensees to register names as well, thus
complicating matters a bit. Second, the RrSG position seems
to encourage dot brand registries to discriminate among
registrars using registration policies, or perhaps other
</span><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">restrictions
or
</span><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">side
agreements
</span><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">among</span><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">
Affiliates and Trademark Licensees, at their own peril.
Absent any assurances from ICANN legal regarding the
propriety of these indirect work-around suggestions, I
imagine that dot Brands would be much more comfortable with
the direct and
<i>formal</i> provision in the Registry Agreement that is
presently under consideration by the Council. As I
understand it, that is why the provision is necessary in the
first place—so dot Brands cannot be alleged to violate the
Registry Agreement in accrediting only one or two preferred
corporate registrars. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I
look forward to your responsive feedback.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333">Thank
you,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333">Brian<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333">Brian
J. Winterfeldt
<br>
</span></b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333">Head
of Internet Practice<br>
</span><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#83A6BD">Katten
Muchin Rosenman LLP<br>
</span></b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333">2900
K Street NW, North Tower - Suite 200 / Washington, DC
20007-5118<br>
p / (202) 625-3562 f / (202) 339-8244<br>
<a moz-do-not-send="true"
href="mailto:brian.winterfeldt@xxxxxxxxxxxxx";>brian.winterfeldt@xxxxxxxxxxxxx</a></span><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">
/
</span><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333"><a
moz-do-not-send="true"
href="http://www.kattenlaw.com/";>www.kattenlaw.com</a><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div align="center">
<table class="MsoNormalTable" style="width:90.0%"
cellpadding="0" width="90%" border="0">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<h3>Re: [council] A way forward on the Specification
13 question<o:p></o:p></h3>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">To</span></em>:
Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>,
Bret Fausett <bret@xxxxxxxx>, GNSO Council
List <council@xxxxxxxxxxxxxx>
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">Subject</span></em>:
Re: [council] A way forward on the Specification
13 question
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">From</span></em>:
"James M. Bladel" <jbladel@xxxxxxxxxxx>
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">Date</span></em>:
Mon, 28 Apr 2014 16:12:52 +0000
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">Accept-language</span></em>:
en-US
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">In-reply-to</span></em>:
<<a moz-do-not-send="true"
href="http://gnso.icann.org/mailing-lists/archives/council/msg16070.html";>535E1AA3.6090807@xxxxxxxxxxxxxxx</a>>
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">List-id</span></em>:
council@xxxxxxxxxxxxxx
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">Sender</span></em>:
owner-council@xxxxxxxxxxxxxx
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">Thread-index</span></em>:
Ac9U37pVNGMfDV+cTSyNSj0xaeNagAJSGHAAAKWMf0oAGtHogAAH4hAAAAWYJ4AAWH6IgAAEVA2A
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo5">
<em><span
style="font-family:"Calibri","sans-serif"">Thread-topic</span></em>:
[council] A way forward on the Specification 13
question
<o:p></o:p></li>
</ul>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr size="2" width="100%" align="center">
</div>
<pre>Just to add to Volker¹s comments:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Registrars have had a vigorous discussion on this topic,
and provided<o:p></o:p></pre>
<pre>feedback from diverse viewpoints. But on the narrow
question--whether<o:p></o:p></pre>
<pre>Spec 13 is compatible with Rec 19‹we generally believe
it is not.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>We recognize that dot-BRAND applicants and TLDs are a
new part of the<o:p></o:p></pre>
<pre>domain name ecosystem, and will have unique interests
not shared by other<o:p></o:p></pre>
<pre>TLDs. For example, we whole-heartedly agree with the
proposed<o:p></o:p></pre>
<pre>restrictions in Spec 13 on ICANN¹s ability to
re-delegate a string that<o:p></o:p></pre>
<pre>was formerly part of a dot-BRAND. However, we do not
agree with the<o:p></o:p></pre>
<pre>assertion that these TLDs must be formally allowed to
discriminate among<o:p></o:p></pre>
<pre>ICANN-accredited registrars.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>In response to the concerns raised by proponents of Spec
13, about being<o:p></o:p></pre>
<pre>beholden to a single registrar/service provider, we
would point out that,<o:p></o:p></pre>
<pre>as the Registry and Registrant, they would possess sole
authority to<o:p></o:p></pre>
<pre>execute a bulk transfer to a new exclusive
registrar/service provider<o:p></o:p></pre>
<pre>under existing ICANN policy. Additionally, to address
concerns about<o:p></o:p></pre>
<pre>³trusted² vs. ³untrusted² registrar/service providers,
we would note that,<o:p></o:p></pre>
<pre>as the Registrant, they would be able to choose the
services of any<o:p></o:p></pre>
<pre>registrar (or group of registrars) of their choosing,
without the need to<o:p></o:p></pre>
<pre>include this language in the Registry Agreement. In
fact, this concern is<o:p></o:p></pre>
<pre>only legitimate in the scenario where the dot-BRAND TLD
later extends<o:p></o:p></pre>
<pre>registrations to unaffiliated third
parties.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>In summary, Registrars do not believe that this
component of Spec 13 is<o:p></o:p></pre>
<pre>compatible with Recommendation 19 of the original new
gTLD policy, and<o:p></o:p></pre>
<pre>that while dot-Brand are likely to encounter concerns
unique to their new<o:p></o:p></pre>
<pre>category of TLD, these issues can be addressed under
existing policy.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks‹<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>J.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>From: Volker Greimann
<vgreimann@xxxxxxxxxxxxxxx><o:p></o:p></pre>
<pre>Date: Monday, April 28, 2014 at 4:08<o:p></o:p></pre>
<pre>To: Bret Fausett <bret@xxxxxxxx>, GNSO Council
List<o:p></o:p></pre>
<pre><council@xxxxxxxxxxxxxx><o:p></o:p></pre>
<pre>Subject: Re: [council] A way forward on the
Specification 13 question<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Dear council-members,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>after extensive discussion of the question put before
us, the RrSG has<o:p></o:p></pre>
<pre>likewise found this excemption to be inconsistent with
both the language<o:p></o:p></pre>
<pre>as well as with the spirit of the
recommendation.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The question we have been asked is not whether we like
the proposed<o:p></o:p></pre>
<pre>exemption or can live with it, but rather a very simple
one: Is the<o:p></o:p></pre>
<pre>proposed incorporation of an ability to restrict
nondiscriminatory<o:p></o:p></pre>
<pre>registrar access to dotBrand TLDs is not consistent
with<o:p></o:p></pre>
<pre> the intent and wording of Recommendation 19, or is it
not. The<o:p></o:p></pre>
<pre>recommendation explicitly states that "Registries (...)
may not<o:p></o:p></pre>
<pre>discriminate among (ICANN) accredited registrars". In
other words, the<o:p></o:p></pre>
<pre>language of the Recommendation 19 contradicts the
proposed<o:p></o:p></pre>
<pre> exemption. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Therefore, to find the additional language to be
consistent with the<o:p></o:p></pre>
<pre>recommendation requires substantial arguments to that
effect that would<o:p></o:p></pre>
<pre>allow such an interpretation. To find it consistent
because one likes the<o:p></o:p></pre>
<pre>result or can live with the result does
not<o:p></o:p></pre>
<pre> fulfill this requirement. For such cases where
implementation would<o:p></o:p></pre>
<pre>conflict with existing policy, further policy work
adjusting or confirming<o:p></o:p></pre>
<pre>the Policy Recommendation is required. The GNSO Council
should take the<o:p></o:p></pre>
<pre>lead in initiating this policy work.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Beyond the grammatical inconsistency of the
Recommendation, the intent of<o:p></o:p></pre>
<pre>the Recommendation also indicates
inconsistency.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>As detailed in the final report on the Introduction of
New Generic Top<o:p></o:p></pre>
<pre>Level Domains, the recommendation was supported by all
GNSO Constituencies<o:p></o:p></pre>
<pre>and Mrs Doria. According to the recollections of members
of the new gTLD<o:p></o:p></pre>
<pre>policy committee at the time the
Recommendation<o:p></o:p></pre>
<pre> was agreed upon, the concept of restricting registrar
access was<o:p></o:p></pre>
<pre>discussed in the context of community TLDs, which are in
many ways similar<o:p></o:p></pre>
<pre>to dotBrands. As registries have the ability under the
Registry Agreement<o:p></o:p></pre>
<pre>to restrict registrar access to their
TLDs<o:p></o:p></pre>
<pre> by establishing reasonable, nondiscriminatory
accreditation criteria, it<o:p></o:p></pre>
<pre>was ultimately agreed that discrimintation between
registrars should not<o:p></o:p></pre>
<pre>be permitted.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>In fact, the only public comment with regard to this
recommendation came<o:p></o:p></pre>
<pre>from the RyC, which was concerned that small,
specialized registries may<o:p></o:p></pre>
<pre>not be able to find a registrar to carry them. Note that
this concern<o:p></o:p></pre>
<pre>deals with a completely different
problem.<o:p></o:p></pre>
<pre> This concern led to the Vertical Integration Working
group and the<o:p></o:p></pre>
<pre>subsequent board decision allowing vertical integration.
The idea of<o:p></o:p></pre>
<pre>allowing only a few registrars does not appear in the
Final Report.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Finally, as registrants, dotBrands are perfectly free to
discriminate<o:p></o:p></pre>
<pre>between registrars. The Recommendation only deals with
registries. By<o:p></o:p></pre>
<pre>establishing certain registration requirements and
policies, registries<o:p></o:p></pre>
<pre>can further eliminate the ability of
registrars<o:p></o:p></pre>
<pre> to provide registry services beyond the eligible circle
of registrants.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker Greimann<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Am 26.04.2014 16:54, schrieb Bret
Fausett:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Feedback:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>What we have been asked by the Board is to "advise ICANN
as to whether the<o:p></o:p></pre>
<pre>GNSO Council believes that this additional provision is
inconsistent with<o:p></o:p></pre>
<pre>the letter and intent of GNSO Policy Recommendation 19
on the Introduction<o:p></o:p></pre>
<pre>of New Generic Top-Level Domains.²<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Policy Recommendation 19 reads: "Registries must use
only ICANN accredited<o:p></o:p></pre>
<pre>registrars in registering domain names and may not
discriminate among such<o:p></o:p></pre>
<pre>accredited registrars.²<o:p></o:p></pre>
<pre><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><o:p></o:p></pre>
<pre> The discussion section of this policy recommendation
does not make for<o:p></o:p></pre>
<pre>any exceptions for brands.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Plainly, as I read the provisions of the .BRAND
Specification 13, it is<o:p></o:p></pre>
<pre>³inconsistent with the letter and intent of GNSO Policy
Recommendation<o:p></o:p></pre>
<pre>19.² <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Now, I personally happen to think that the draft
Specification 13 for<o:p></o:p></pre>
<pre>.BRAND TLDs is a tightly drafted, well-considered
exception for a<o:p></o:p></pre>
<pre>specialized type of TLD that was not being considered
carefully when<o:p></o:p></pre>
<pre>Recommendation 19 was prepared. BUT, it is
definitely<o:p></o:p></pre>
<pre> inconsistent with the policy recommendation we made in
August, 2007.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Let¹s think about what this means.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>Bret Fausett, Esq. € General Counsel, Uniregistry,
Inc.<o:p></o:p></pre>
<pre>12025 Waterfront Drive, Suite 200 € Playa Vista, CA
90094-2536<o:p></o:p></pre>
<pre><span
class="baec5a81-e4d6-4674-97f3-e9220f0136c1">310-496-5755</span><span
class="skypepnhmark1"> begin_of_the_skype_highlighting</span><span
class="skypepnhcontainer"> </span><img id="Rectangle_x0020_6"
src="cid:part5.05060109.08000702@key-systems.net"
alt="skype-ie-addon-data://res/numbers_button_skype_logo.png" width="32"
border="0" height="32"><span
class="baec5a81-e4d6-4674-97f3-e9220f0136c1">310-496-5755</span><span
class="skypepnhfreetextspan"> FREE </span><span
class="skypepnhcontainer"> </span><span
class="skypepnhmark1">end_of_the_skype_highlighting</span> (T) € <span
class="baec5a81-e4d6-4674-97f3-e9220f0136c1">310-985-1351</span><span
class="skypepnhmark1"> begin_of_the_skype_highlighting</span><span
class="skypepnhcontainer"> </span><img id="Rectangle_x0020_5"
src="cid:part5.05060109.08000702@key-systems.net"
alt="skype-ie-addon-data://res/numbers_button_skype_logo.png" width="32"
border="0" height="32"><span class="baec5a81-e4d6-4674-!
97f3-e92
20f0136c1">310-985-1351</span><span class="skypepnhfreetextspan"> FREE
</span><span class="skypepnhcontainer"> </span><span
class="skypepnhmark1">end_of_the_skype_highlighting</span> (M) €
bret@xxxxxxxxxxxxxxx<o:p></o:p></pre>
<pre>‹ ‹ ‹ ‹ ‹ <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Apr 26, 2014, at 5:14 AM, Thomas Rickert
<rickert@xxxxxxxxxxx> wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Jonathan,<o:p></o:p></pre>
<pre>I do hope to get more feedback. So far, I do not really
have information<o:p></o:p></pre>
<pre>to act on, but I am standing by to do what is necessary
to meet the<o:p></o:p></pre>
<pre>deadline.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre>Thomas<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Am 26.04.2014 um 10:29 schrieb Jonathan Robinson
<jrobinson@xxxxxxxxxxxx>:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks Thomas,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>You will have seen that the motion deadline is Monday
28th 23h59<o:p></o:p></pre>
<pre> UTC so, assuming we will meet the 45 day deadline, we
will need a motion<o:p></o:p></pre>
<pre>on Monday.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Let¹s hope we can do that in such a way as to reflect
the feedback you<o:p></o:p></pre>
<pre>have and retain flexibility to modify<o:p></o:p></pre>
<pre> (if necessary) as we receive further
feedback.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Let¹s you and I talk on Monday.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Jonathan<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>From: Thomas<o:p></o:p></pre>
<pre> Rickert [<a moz-do-not-send="true"
href="mailto:rickert@xxxxxxxxxxx";>mailto:rickert@xxxxxxxxxxx</a>]<o:p></o:p></pre>
<pre>Sent: 25 April 2014 20:38<o:p></o:p></pre>
<pre>To: GNSO Council List<o:p></o:p></pre>
<pre>Subject: Fwd: [council] A way forward on the
Specification 13 question<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre>All,<o:p></o:p></pre>
<pre>this is a gentle reminder to provide me with preliminary
feedback. The<o:p></o:p></pre>
<pre>motions and documents deadline is approaching rapidly
and I have only<o:p></o:p></pre>
<pre>received one response from the registrars so
far.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Also, I have reached out to Marilyn Cade (CBUC), Tony
Holmes (ISPC),<o:p></o:p></pre>
<pre>Kristina Rosette (IPC), Robin Gross (NCUC), Bruce Tonkin
(Registrars) and<o:p></o:p></pre>
<pre>Ken Stubbs (Registries) as they were listed in the final
report of the PDP<o:p></o:p></pre>
<pre>to cover their respective groups and
since<o:p></o:p></pre>
<pre> they hopefully have first-hand information on the
discussions at the<o:p></o:p></pre>
<pre>time. More people such as Avri, Bret and Alan are still
here - please to<o:p></o:p></pre>
<pre>chime in and respond.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks and kind regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thomas <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Anfang der weitergeleiteten Nachricht:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Von: Thomas Rickert
<rickert@xxxxxxxxxxx><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Betreff: Aw: [council] A way forward on the
Specification 13 question<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Datum: 22. April 2014 14:40:58<o:p></o:p></pre>
<pre> MESZ<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>An: jrobinson@xxxxxxxxxxxx<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Kopie: GNSO Council List
<council@xxxxxxxxxxxxxx><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre>All,<o:p></o:p></pre>
<pre>thanks to Jonathan for putting together and sending out
the below message.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I am more than happy to assist with making sure we get
an answer prepared<o:p></o:p></pre>
<pre>in time. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Can I ask Councillors to get back to me offlist (in
order not to swamp the<o:p></o:p></pre>
<pre>list) with a status of the discussions with your
respective groups?<o:p></o:p></pre>
<pre>Certainly, one response per group is
sufficient.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>If there is anything I can help with to facilitate your
discussions,<o:p></o:p></pre>
<pre>please let me know.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The earlier I am provided with information on what
direction your answers<o:p></o:p></pre>
<pre>will take, the sooner I will be able to draft a motion
and a letter to the<o:p></o:p></pre>
<pre>NGPC for your review.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thomas<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Am 10.04.2014 um 19:10 schrieb Jonathan Robinson
<jrobinson@xxxxxxxxxxxx>:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre>All,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Following on from previous dialogue and the Council
meeting today, it<o:p></o:p></pre>
<pre>seems to me that the way forward is to
focus<o:p></o:p></pre>
<pre> as closely as possible on the question being asked and
to make every<o:p></o:p></pre>
<pre>attempt to respond in a timely and effective
manner.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>This means that, assuming it is required, a motion to be
voted on needs to<o:p></o:p></pre>
<pre>be submitted to the Council by 28 April<o:p></o:p></pre>
<pre> for consideration at the 8 May 2014
meeting.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>We are being asked (full letter attached for reference)
to<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>1. Š<o:p></o:p></pre>
<pre> advise ICANN as to whether the GNSO Council believes
that this additional<o:p></o:p></pre>
<pre>provision is inconsistent with the letter and intent of
GNSO Policy<o:p></o:p></pre>
<pre>Recommendation 19 on the Introduction of New Generic
Top-Level Domains;<o:p></o:p></pre>
<pre>or<o:p></o:p></pre>
<pre>2. advise<o:p></o:p></pre>
<pre> ICANN that the GNSO Council needs additional time for
review, including<o:p></o:p></pre>
<pre>an explanation as to why additional time is
required.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>I believe that the question to take to your respective
stakeholder groups<o:p></o:p></pre>
<pre>/ constituencies is therefore:<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Is this additional provision inconsistent with the
letter and intent of<o:p></o:p></pre>
<pre>GNSO Policy Recommendation 19?<o:p></o:p></pre>
<pre>It will be helpful to have as clear as possible an
answer as soon as<o:p></o:p></pre>
<pre>possible along the following lines:<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>· No.<o:p></o:p></pre>
<pre> It is not inconsistent (Š with the letter and intent
Š).<o:p></o:p></pre>
<pre>and<o:p></o:p></pre>
<pre>· Possibly,<o:p></o:p></pre>
<pre> an explanation as to why it is not
inconsistent.<o:p></o:p></pre>
<pre>and<o:p></o:p></pre>
<pre>· Are<o:p></o:p></pre>
<pre> there any other qualifying points that the Council
should make in its<o:p></o:p></pre>
<pre>response to the NGPC?<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>OR<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>· Yes.<o:p></o:p></pre>
<pre> It is inconsistent ( Š with the letter and intent Š
).<o:p></o:p></pre>
<pre>and<o:p></o:p></pre>
<pre>· Possibly,<o:p></o:p></pre>
<pre> an explanation as to why it is
inconsistent.<o:p></o:p></pre>
<pre>and<o:p></o:p></pre>
<pre>· Is<o:p></o:p></pre>
<pre> there a process by which the Council could assist the
NGPC in resolving<o:p></o:p></pre>
<pre>this issue and in what time frame?<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please can you all act as quickly as possible to provide
an answer to the<o:p></o:p></pre>
<pre>above. The timing is<o:p></o:p></pre>
<pre> very tight.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>We already have an indication of where the BC & the
IPC stand on this i.e.<o:p></o:p></pre>
<pre>no, it is not inconsistent.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Someone will need to lead on drafting a motion (for
submission to the<o:p></o:p></pre>
<pre>Council on or before 28 April) and an
associated<o:p></o:p></pre>
<pre> letter to the NGPC.<o:p></o:p></pre>
<pre>Given the time constraints, this should probably take
place in parallel<o:p></o:p></pre>
<pre>with the consultation work.<o:p></o:p></pre>
<pre>Can we please have a volunteer to lead this effort and
ensure it gets<o:p></o:p></pre>
<pre>done? Thomas?<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I have tried to simplify and focus the problem here in
the interest of<o:p></o:p></pre>
<pre>providing a representative, timely and<o:p></o:p></pre>
<pre> effective response.<o:p></o:p></pre>
<pre>I trust that in doing so I have not discounted any
material points in the<o:p></o:p></pre>
<pre>discussion to date. Please correct<o:p></o:p></pre>
<pre> me if I have.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Jonathan<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>Bret Fausett, Esq. € General Counsel, Uniregistry,
Inc.<o:p></o:p></pre>
<pre>12025 Waterfront Drive, Suite 200 € Playa Vista, CA
90094-2536<o:p></o:p></pre>
<pre><span
class="baec5a81-e4d6-4674-97f3-e9220f0136c1">310-496-5755</span><span
class="skypepnhmark1"> begin_of_the_skype_highlighting</span><span
class="skypepnhcontainer"> </span><img id="Rectangle_x0020_4"
src="cid:part5.05060109.08000702@key-systems.net"
alt="skype-ie-addon-data://res/numbers_button_skype_logo.png" width="32"
border="0" height="32"><span
class="baec5a81-e4d6-4674-97f3-e9220f0136c1">310-496-5755</span><span
class="skypepnhfreetextspan"> FREE </span><span
class="skypepnhcontainer"> </span><span
class="skypepnhmark1">end_of_the_skype_highlighting</span> (T) € <span
class="baec5a81-e4d6-4674-97f3-e9220f0136c1">310-985-1351</span><span
class="skypepnhmark1"> begin_of_the_skype_highlighting</span><span
class="skypepnhcontainer"> </span><img id="Rectangle_x0020_3"
src="cid:part5.05060109.08000702@key-systems.net"
alt="skype-ie-addon-data://res/numbers_button_skype_logo.png" width="32"
border="0" height="32"><span class="baec5a81-e4d6-4674-!
97f3-e92
20f0136c1">310-985-1351</span><span class="skypepnhfreetextspan"> FREE
</span><span class="skypepnhcontainer"> </span><span
class="skypepnhmark1">end_of_the_skype_highlighting</span> (M) €
bret@xxxxxxxxxxxxxxx<o:p></o:p></pre>
<pre>‹ ‹ ‹ ‹ ‹ <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-- <o:p></o:p></pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur
Verfügung.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- Rechtsabteilung -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: <span class="skypepnhprintcontainer1398710629">+49
(0) 6894 - 9396 901</span><span class="skypepnhmark1">
begin_of_the_skype_highlighting</span><span class="skypepnhcontainer">
</span><img id="Rectangle_x0020_2"
src="cid:part5.05060109.08000702@key-systems.net"
alt="skype-ie-addon-data://res/numbers_button_skype_logo.png" width="32"
border="0" height="32"><span class="skypepnhtextspan">+49 (0) 6894 - 9396
901</span><span class="skypepnhfreetextspan"> FREE </span><span
class="skypepnhcontainer"> </span><span
class="skypepnhmark1">end_of_the_skype_highlighting</span><o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: vgreimann@xxxxxxxxxxxxxxx<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a moz-do-not-send="true"
href="http://www.key-systems.net";>www.key-systems.net</a> <<a
moz-do-not-send="true"
href="http://www.key-systems.net";>http://www.key-systems.net</a>> / <a
moz-do-not-send="true"
href="http://www.RRPproxy.net";>www.RRPproxy.net</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.RRPproxy.net";>http://www.RRPproxy.net</a>><a
moz-do-not-send="true"
href="http://www.domaindiscount24.com";>www.domaindiscount24.com</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.domaindiscount24.com";>http://www.domaindiscount24.com</a>>
/ <a moz-do-not-send="true"
href="http://www.BrandShelter.com";>www.BrandShelter.com</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.BrandShelter.com";>http://www.BrandShelter.com</a>><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei
Facebook:<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems";>www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems";>http://www.facebook.com/KeySystems</a>><a
moz-do-not-send="true"
href="http://www.twitter.com/key_systems";>www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.twitter.com/key_systems";>http://www.twitter.com/key_systems</a>><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
<pre>Handelsregister Nr.: HR B 18835 -
Saarbruecken<o:p></o:p></pre>
<pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="http://www.keydrive.lu";>www.keydrive.lu</a> <<a moz-do-not-send="true"
href="http://www.keydrive.lu";>http://www.keydrive.lu</a>><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Der Inhalt dieser Nachricht ist vertraulich und nur für
den angegebenen<o:p></o:p></pre>
<pre>Empfänger bestimmt. Jede Form der Kenntnisgabe,
Veröffentlichung oder<o:p></o:p></pre>
<pre>Weitergabe an Dritte durch den Empfänger ist unzulässig.
Sollte diese<o:p></o:p></pre>
<pre>Nachricht nicht für Sie bestimmt sein, so bitten wir
Sie, sich mit uns per<o:p></o:p></pre>
<pre>E-Mail oder telefonisch in Verbindung zu
setzen.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--------------------------------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Should you have any further questions, please do not
hesitate to contact<o:p></o:p></pre>
<pre>us.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- legal department -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: <span class="skypepnhprintcontainer1398710629">+49
(0) 6894 - 9396 901</span><span class="skypepnhmark1">
begin_of_the_skype_highlighting</span><span class="skypepnhcontainer">
</span><img id="Rectangle_x0020_1"
src="cid:part5.05060109.08000702@key-systems.net"
alt="skype-ie-addon-data://res/numbers_button_skype_logo.png" width="32"
border="0" height="32"><span class="skypepnhtextspan">+49 (0) 6894 - 9396
901</span><span class="skypepnhfreetextspan"> FREE </span><span
class="skypepnhcontainer"> </span><span
class="skypepnhmark1">end_of_the_skype_highlighting</span><o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: vgreimann@xxxxxxxxxxxxxxx<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a moz-do-not-send="true"
href="http://www.key-systems.net";>www.key-systems.net</a> <<a
moz-do-not-send="true"
href="http://www.key-systems.net";>http://www.key-systems.net</a>> / <a
moz-do-not-send="true"
href="http://www.RRPproxy.net";>www.RRPproxy.net</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.RRPproxy.net";>http://www.RRPproxy.net</a>><a
moz-do-not-send="true"
href="http://www.domaindiscount24.com";>www.domaindiscount24.com</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.domaindiscount24.com";>http://www.domaindiscount24.com</a>>
/ <a moz-do-not-send="true"
href="http://www.BrandShelter.com";>www.BrandShelter.com</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.BrandShelter.com";>http://www.BrandShelter.com</a>><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Follow us on Twitter or join our fan community on
Facebook and stay<o:p></o:p></pre>
<pre>updated:<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems";>www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems";>http://www.facebook.com/KeySystems</a>><a
moz-do-not-send="true"
href="http://www.twitter.com/key_systems";>www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><<a moz-do-not-send="true"
href="http://www.twitter.com/key_systems";>http://www.twitter.com/key_systems</a>><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>CEO: Alexander Siffrin<o:p></o:p></pre>
<pre>Registration No.: HR B 18835 -
Saarbruecken<o:p></o:p></pre>
<pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="http://www.keydrive.lu";>www.keydrive.lu</a> <<a moz-do-not-send="true"
href="http://www.keydrive.lu";>http://www.keydrive.lu</a>><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>This e-mail and its attachments is intended only for the
person to whom it<o:p></o:p></pre>
<pre>is addressed. Furthermore it is not permitted to publish
any content of<o:p></o:p></pre>
<pre>this email. You must not use, disclose, copy, print or
rely on this<o:p></o:p></pre>
<pre>e-mail. If an addressing or transmission error has
misdirected this<o:p></o:p></pre>
<pre>e-mail, kindly notify the author by replying to this
e-mail or contacting<o:p></o:p></pre>
<pre>us by telephone.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr size="2" width="100%" align="center">
</div>
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-language:EN-US">
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
level1 lfo8">
<strong><span
style="font-family:"Calibri","sans-serif"">References</span></strong>:
<o:p></o:p>
<ul type="circle">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
level2 lfo8">
<a moz-do-not-send="true" name="16070"></a><a
moz-do-not-send="true"
href="http://gnso.icann.org/mailing-lists/archives/council/msg16070.html";><b>Re:
[council] A way forward on the
Specification 13 question</b></a>
<o:p></o:p>
<ul type="square">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4
level3 lfo8">
<em><span
style="font-family:"Calibri","sans-serif"">From:</span></em>
Volker Greimann<o:p></o:p></li>
</ul>
</li>
</ul>
</li>
</ul>
</span>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" style="text-align:center"
align="center"><a moz-do-not-send="true"
href="http://gnso.icann.org/mailing-lists/archives/council/msg16073.html";><<<</a>
<a moz-do-not-send="true"
href="http://gnso.icann.org/mailing-lists/archives/council/index.html#16074";>Chronological
Index</a> >>>
<a moz-do-not-send="true"
href="http://gnso.icann.org/mailing-lists/archives/council/msg16072.html";><<<</a>
<a moz-do-not-send="true"
href="http://gnso.icann.org/mailing-lists/archives/council/thrd268.html#16074";>Thread
Index</a> <a moz-do-not-send="true"
href="http://gnso.icann.org/mailing-lists/archives/council/msg16022.html";>>>></a>
<o:p></o:p></p>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" style="text-align:center"
align="center"><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal" style="background:white">Call<span
style="font-family:"Times New
Roman","serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white">Send SMS<o:p></o:p></p>
<p class="MsoNormal" style="background:white">Add to
Skype<o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span
class="skypepnhmenutollcallcredit2"><span
style="font-size:10.0pt">You'll need Skype
Credit</span></span><span
class="skypepnhmenutollfree2"><span style="font-size:10.0pt">Free
via Skype</span></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<table>
<tbody>
<tr>
<td bgcolor="#ffffff"><font color="#000000">
<pre>===========================================================
CIRCULAR 230 DISCLOSURE: Pursuant to Regulations Governing Practice Before the
Internal Revenue
Service, any tax advice contained herein is not intended or written to be used
and cannot be used
by a taxpayer for the purpose of avoiding tax penalties that may be imposed on
the taxpayer.
===========================================================
CONFIDENTIALITY NOTICE:
This electronic mail message and any attached files contain information
intended for the exclusive
use of the individual or entity to whom it is addressed and may contain
information that is
proprietary, privileged, confidential and/or exempt from disclosure under
applicable law. If you
are not the intended recipient, you are hereby notified that any viewing,
copying, disclosure or
distribution of this information may be subject to legal restriction or
sanction. Please notify
the sender, by electronic mail or telephone, of any unintended recipients and
delete the original
message without making any copies.
===========================================================
NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability
partnership that has
elected to be governed by the Illinois Uniform Partnership Act (1997).
===========================================================</pre>
</font></td>
</tr>
</tbody>
</table>
</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@xxxxxxxxxxxxxxx";>vgreimann@xxxxxxxxxxxxxxx</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@xxxxxxxxxxxxxxx";>vgreimann@xxxxxxxxxxxxxxx</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>
</body>
</html>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|