RE: [gnso-rn-wg] ICANN and IANA reserved names version 12

["Gomes, Chuck" <cgomes@xxxxxxxxxxxx>]

Marilyn,

This does not mean that any requirements for new gTLDs might not
eventually be incorporated into existing agreements nor does it preclude
development of a consensus policy with which existing registries would
have to comply.  This WG cannot change negotiated agreements with
registries.

Chuck Gomes
 
"This message is intended for the use of the individual or entity to
which it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. Any
unauthorized use, distribution, or disclosure is strictly prohibited. If
you have received this message in error, please notify sender
immediately and destroy/delete the original transmission." 
 

> -----Original Message-----
> From: Marilyn Cade [mailto:marilynscade@xxxxxxxxxxx] 
> Sent: Tuesday, March 06, 2007 5:53 PM
> To: Gomes, Chuck; tim@xxxxxxxxxxxx; gnso-rn-wg@xxxxxxxxx
> Cc: glen@xxxxxxxxx
> Subject: RE: [gnso-rn-wg] ICANN and IANA reserved names version 12
> 
> Will digest this. 
> -----Original Message-----
> From: owner-gnso-rn-wg@xxxxxxxxx 
> [mailto:owner-gnso-rn-wg@xxxxxxxxx] On Behalf Of Gomes, Chuck
> Sent: Tuesday, March 06, 2007 5:05 PM
> To: tim@xxxxxxxxxxxx; gnso-rn-wg@xxxxxxxxx
> Cc: glen@xxxxxxxxx
> Subject: RE: [gnso-rn-wg] ICANN and IANA reserved names version 12
> 
> Thanks Tim.  Here are some suggestions for the 
> recommendations section.
> 
> The recommendations we are making will be for new gTLDs, not 
> specifically for existing ones like .pro and .name, so you 
> shouldn't mention those two gTLDs in your recommendations for 
> the 3rd level.  You should use general language that 
> basically says something like this: "as applicable for gTLDs 
> that register names at the 3rd level".
> 
> Regarding recommendations for more work, you should add some 
> guidelines in that regard below the table.  Also, I wouldn't 
> use the "as above" for that column.  Ideas for guidelines: 
> consulting with the IDN WG in the case of IDNs; consulting 
> with experts regarding http, https and html; further 
> consideration of concerns raised by Mike Palage and Mike 
> Rodenbaugh.  Regarding the latter, where in your report did 
> you discuss this.  It seems to me that there should be a 
> brief reference to this concern in the recommendations 
> section in the context of possible additional work by the 
> GNSO.  Also, in the case of 'example', it would be helpful to 
> discuss what you think needs to be done with regard to 
> additional work in that regard (e.g., further consultation 
> with the IDN WG? Or with IDN experts?)
> 
> Finally, in the IDN Implications section of Section 4, I 
> think it would be helpful to add a footnote that gives the 
> link to the MPC and/or the transcript for the meeting in 
> which we had the consultation.
> 
> Chuck Gomes
>  
> "This message is intended for the use of the individual or 
> entity to which it is addressed, and may contain information 
> that is privileged, confidential and exempt from disclosure 
> under applicable law. Any unauthorized use, distribution, or 
> disclosure is strictly prohibited. If you have received this 
> message in error, please notify sender immediately and 
> destroy/delete the original transmission." 
>  
> 
> > -----Original Message-----
> > From: owner-gnso-rn-wg@xxxxxxxxx
> > [mailto:owner-gnso-rn-wg@xxxxxxxxx] On Behalf Of tim@xxxxxxxxxxxx
> > Sent: Tuesday, March 06, 2007 3:31 PM
> > To: gnso-rn-wg@xxxxxxxxx
> > Cc: glen@xxxxxxxxx
> > Subject: [gnso-rn-wg] ICANN and IANA reserved names version 12
> > 
> > All: This is for our meeting tomorrow.
> > TMD
> > 
> > 
> > 
> > 
> 
> 
>