RE: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft

["Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>]

Thanks Berry.  I read it in the redline draft and that was what I was 
commenting on.  So long as there is nothing in the clean draft which will be 
the one we are looking at, then I am fine.



Sent with Good (www.good.com)


 -----Original Message-----
From:   Berry Cobb [mailto:mail@xxxxxxxxxxxxx]
Sent:   Thursday, September 20, 2012 02:11 PM Eastern Standard Time
To:     gnso-iocrc-dt@xxxxxxxxx
Subject:        RE: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft

Team,

 

Yes, this was only a balloon comment that I added to the redline draft given 
the brief discussion of this topic on the call yesterday.  It was unclear where 
the WG stood, and I wanted to ensure it was not left off without WG feedback.

 

At this point, it does not appear there will be consensus about the possible 
registration of the IOC/RCRC names only until such a PDP can make the 
determination of the protections and exceptions.

 

My apologies for the confusion.

 

Thank you.  B

 

Berry Cobb

Internet Corporation for Assigned Names & Numbers (ICANN)

720.839.5735

mail@xxxxxxxxxxxxx <mailto:mail@xxxxxxxxxxxxx> 

@berrycobb

 

 

From: owner-gnso-iocrc-dt@xxxxxxxxx [mailto:owner-gnso-iocrc-dt@xxxxxxxxx] On 
Behalf Of Gomes, Chuck
Sent: Thursday, September 20, 2012 10:58
To: Shatan, Gregory S.; 'onovoa@xxxxxxxxxxxx'; 'Jeff.Neuman@xxxxxxxxxx'; 
'mail@xxxxxxxxxxxxx'; 'gnso-iocrc-dt@xxxxxxxxx'
Subject: RE: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft

 

Thanks Greg.

 

Chuck

 

From: Shatan, Gregory S. [mailto:GShatan@xxxxxxxxxxxxx] 
Sent: Thursday, September 20, 2012 1:56 PM
To: Gomes, Chuck; 'onovoa@xxxxxxxxxxxx'; 'Jeff.Neuman@xxxxxxxxxx'; 
'mail@xxxxxxxxxxxxx'; 'gnso-iocrc-dt@xxxxxxxxx'
Subject: Re: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft

 

This was a marginal "balloon" comment in the track changes version of the 
document. 
-------------------------- 
Sent from my BlackBerry Wireless Device 

 

From: Gomes, Chuck [mailto:cgomes@xxxxxxxxxxxx] 
Sent: Thursday, September 20, 2012 01:52 PM
To: Novoa, Osvaldo <onovoa@xxxxxxxxxxxx>; 'Neuman, Jeff' 
<Jeff.Neuman@xxxxxxxxxx>; Berry Cobb <mail@xxxxxxxxxxxxx>; 
gnso-iocrc-dt@xxxxxxxxx <gnso-iocrc-dt@xxxxxxxxx> 
Subject: RE: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft 
 

I don’t believe the final draft (that was just distributed) had anything about 
exceptions.  Am I missing something?

 

Chuck

 

From: owner-gnso-iocrc-dt@xxxxxxxxx [mailto:owner-gnso-iocrc-dt@xxxxxxxxx] On 
Behalf Of Novoa, Osvaldo
Sent: Thursday, September 20, 2012 1:35 PM
To: 'Neuman, Jeff'; Berry Cobb; gnso-iocrc-dt@xxxxxxxxx
Subject: RE: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft

 

Jeff, and All,

I totally agree with Jeff’s comments, though I heard the proposal during the 
call I didn’t realized it was agree to include it in the draft.  I, and the 
ISPCP, supported J. Scott’s proposal as it was stated, allowing no exceptions 
till the PDP is finished.  Otherwise it might allow situations that later the 
PDP disallows.

Best regards,

Osvaldo Novoa

 

________________________________

De: owner-gnso-iocrc-dt@xxxxxxxxx [mailto:owner-gnso-iocrc-dt@xxxxxxxxx] En 
nombre de Neuman, Jeff
Enviado el: Jueves, 20 de Septiembre de 2012 14:10
Para: Berry Cobb; gnso-iocrc-dt@xxxxxxxxx
Asunto: RE: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft

 

All,

 

Thanks for your hard work on this yesterday and for putting this out.  This 
comment is being provided not as the chair, but as an individual on a comment 
in the draft which states:  

 

Need to confirm if the registration of the 2nd level domains is allowed by the 
IOC/RCRC organizations at their discretion. [Jim B]

 

It would seem to me that allowing the registration of any 2nd levels (even by 
the organizations themselves) would contradict the entire premise of our 
proposal; namely, that we are recommending a moratorium (I know we do not use 
this word) and not a standard reservation of the names while we work on the 
pdp.  It is precisely why we want this to go to a pdp to not only figure out 
the rationale for having protections in place for these names, but also to 
figure out how exceptions (if any) are worked out.  It may well be after the 
pdp that we have an exception process that allows these organizations to get 
the names (as well as others that may have rights), but that should be figured 
out in the pdp and not pre-judged.   

 

My recommendation is that this comment be taken out of the current draft as it 
was not part of the original consensus call which groups have been soliciting 
comments on.

 

But, putting my chair hat back on, if this is something that the group does 
want, then of course we can leave it in.


Thanks.

 

Jeffrey J. Neuman 
Neustar, Inc. / Vice President, Business Affairs

 

From: owner-gnso-iocrc-dt@xxxxxxxxx [mailto:owner-gnso-iocrc-dt@xxxxxxxxx] On 
Behalf Of Berry Cobb
Sent: Thursday, September 20, 2012 12:15 PM
To: gnso-iocrc-dt@xxxxxxxxx
Subject: [gnso-iocrc-dt] Latest IOC/RCRC Recommendations Draft
Importance: High

 

Team,

 

Attached is the latest draft of recommendations as a result of yesterday’s 
IOC/RCRC call.  I attached a redline version starting from a copy of Jeff’s 
email.  A clean version is also provided.  

 

Please distribute this draft to your respective groups as soon as possible.  
The deadline for determining your respective group’s position about the 
proposed recommendations is due next Wednesday 26 September 2012.

 

If you have any suggestions for changes to this draft, please send them to list.

 

Thank you.  B

 

Berry Cobb

Internet Corporation for Assigned Names & Numbers (ICANN)

720.839.5735

mail@xxxxxxxxxxxxx

@berrycobb

 

 

 

________________________________

El presente correo y cualquier posible archivo adjunto está dirigido únicamente 
al destinatario del mensaje y contiene información que puede ser confidencial. 
Si Ud. no es el destinatario correcto por favor notifique al remitente 
respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los 
posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier 
utilización, difusión o copia de este e-mail por cualquier persona o entidad 
que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna 
responsabilidad con respecto a cualquier comunicación que haya sido emitida 
incumpliendo nuestra Política de Seguridad de la Información


This e-mail and any attachment is confidential and is intended solely for the 
addressee(s). If you are not intended recipient please inform the sender 
immediately, answering this e-mail and delete it as well as the attached files. 
Any use, circulation or copy of this e-mail by any person or entity that is not 
the specific addressee(s) is prohibited. ANTEL is not responsible for any 
communication emitted without respecting our Information Security Policy.

 

* * *

This E-mail, along with any attachments, is considered confidential and may 
well be legally privileged. If you have received it in error, you are on notice 
of its status. Please notify us immediately by reply e-mail and then delete 
this message from your system. Please do not copy it or use it for any 
purposes, or disclose its contents to any other person. Thank you for your 
cooperation.

* * *

To ensure compliance with Treasury Department regulations, we inform you that, 
unless otherwise indicated in writing, any U.S. Federal tax advice contained in 
this communication  (including any attachments) is not intended or written to 
be used, and cannot be used, for the purpose of (1) avoiding penalties under 
the Internal Revenue Code or applicable state and local provisions or (2) 
promoting, marketing or recommending to another party any tax-related matters 
addressed herein.

Disclaimer Version RS.US.20.10.00