<div>
I think the intent of Feb06 is to reach a little farther and actually
have policy around the subjects of its terms of reference. Those would primarily affect the Registries' agreements with ICANN. The procedure we're looking for affects what happens when the Registries' want changes to their agreement with us.</div>
<div><BR><BR>Tim Ruiz<BR>Vice President<BR>Corp. Development & Policy<BR>The Go Daddy Group, Inc.<BR>Mobile: 319-329-9804<BR>Office: 319-294-3940<BR>Fax: 480-247-4516<BR><A href="mailto:tim@godaddy.com">tim@godaddy.com</A><BR><BR>How am I doing? Please contact my direct supervisor at <A href="mailto:president@godaddy.com">president@godaddy.com</A> with any feedback.<BR><BR>
This email message and any attachments hereto is intended for use only
by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.<BR><BR></div>
<div name="wmMessageComp"><BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid">-------- Original Message --------<BR>Subject: Re: [registrars] FW: Draft Procedure<BR>From: Thomas Keller <tom@schlund.de><BR>Date: Mon, January 22, 2007 2:58 am<BR>To: registrars@gnso.icann.org<BR><BR>Ok, one cup of coffee later ;).<BR><BR>The sentence was supposed to look like that:<BR><BR>Isn't that what the FEB 06 Taskforce is supposed to come up with?<BR><BR>Best,<BR><BR>tom<BR><BR>Am 22.01.2007 schrieb Thomas Keller:<BR>> Am 19.01.2007 schrieb Tim Ruiz:<BR>
> > I would think ICANN GC could come up with a base set
of terms that cannot change without Board approval. Other than that, the draft procedure looks fine.<BR><BR>Tim <BR><BR>> <BR>
> Isn't that what the FEB 06 Taskforce is not supposed to come up
with?<BR>> <BR>> Best,<BR>> <BR>> tom<BR>> <BR>> > <div name="wmMessageComp"><BR><BR><BR>
> > <BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px;
BORDER-LEFT: blue 2px solid">-------- Original Message --------<BR>Subject: RE: [registrars] FW: Draft Procedure<BR>From: "Nevett, Jonathon" <jnevett@networksolutions.com><BR>Date: Fri, January 19, 2007 8:18 am<BR>To: "Thomas Keller" <tom@schlund.de><BR>Cc: "Registrars Constituency" <registrars@gnso.icann.org><BR><BR>Thanks Tom.<BR><BR><BR>
> > No vote necessary -- just provide comments to the list and to
ICANN.<BR>> > My<BR><BR>
> > only proposed change to the proposal is to add a standard for
when<BR>> > these<BR><BR>
> > decisions should go to the Board. The current draft
is<BR>> > too<BR>discretionary in that regard. <BR><BR>Thanks.<BR><BR>Jon<BR><BR>-----Original Message-----<BR>From: Thomas Keller [mailto:tom@schlund.de] <BR>Sent: Friday, January 19, 2007 5:08 AM<BR>To: Nevett, Jonathon<BR>Cc: Registrars Constituency<BR>Subject: Re: [registrars] FW: Draft Procedure<BR><BR><BR>
> > Seems ok to me. Do we have to vote on this draft to formally
accept<BR>> > it<BR>and make it policy?<BR><BR>Best,<BR><BR>tom<BR><BR>Am 17.01.2007 schrieb Nevett, Jonathon:<BR>> From ICANN for our review and comment. Thanks. Jon<BR>> <BR>> -----Original Message-----<BR>> From: Kurt Pritz [mailto:pritz@icann.org] <BR>> Sent: Wednesday, January 17, 2007 9:02 PM<BR>> To: Nevett, Jonathon; Marie Zitkova<BR><BR>
> > > Cc: Tim Ruiz; Cherstubbs@aol.com; Tim Cole; Mike
Zupke;<BR>> > Craig<BR>Schwartz;<BR>> Dan Halloran<BR>> Subject: Draft Procedure<BR>> <BR>> Marie, Jon:<BR>> <BR>> Please share this information with your constituency groups.<BR>> <BR><BR>
> > > Attached is a draft procedure for considering gTLD
registry<BR>> > proposals<BR><BR><BR>
> > > for amendments to the Registry-Registrar Agreement
(RRA). The<BR>> > <BR><BR>
> > > procedure is intended to provide opportunity for
comment and<BR>
> > <BR>> discussion and also provide
certainty as to timeframe for<BR>consideration.<BR>> <BR><BR>
> > > This draft arises from the new form of registry
agreements that<BR>> > <BR><BR>
> > > requires ICANN approval for proposed changes to the
RRA. This draft<BR>> > <BR><BR>
> > > procedure essentially provides for notice to
registrars of proposed<BR>> > <BR><BR>
> > > changes, an opportunity for comment, and a forum for
possibly<BR>> > <BR><BR>
> > > resolving areas of controversy. Not specifically
described in the<BR>> > <BR><BR>
> > > procedure but included are public posting of major
changes changes<BR>> > to<BR><BR><BR>
> > > agreements as has been discussed in the recent past
and Board<BR>
> > <BR>> approval of changes to ICANN
agreements in certain circumstances.<BR>> <BR>> Please review and provide comment.<BR>> <BR>> Regards,<BR>> <BR>> Kurt<BR>> <BR>> <BR>> Kurt Pritz<BR>> <BR>> ICANN<BR>> 4676 Admiralty Way, #330<BR>> Marina del Rey. CA 90292<BR>> <BR>> +1.310.301.5809 (office)<BR>> +1.310.400.4184 (mobile)<BR>> <BR><BR><BR><BR><BR>Gruss,<BR><BR>tom<BR><BR>(__) <BR>(OO)_____ <BR>(oo) /|\ A cow is not entirely full of<BR> | |--/ | * milk some of it is hamburger!<BR> w w w w </BLOCKQUOTE></DIV><BR>> > <BR>> > <BR>> > <BR>> <BR>> Gruss,<!
BR>> <BR>> tom<BR>> <BR>> (__) <BR>> (OO)_____ <BR>> (oo) /|\ A cow is not entirely full of<BR>> | |--/ | * milk some of it is hamburger!<BR>> w w w w <BR>> <BR>> <BR><BR>Gruss,<BR><BR>tom<BR><BR>(__) <BR>(OO)_____ <BR>(oo) /|\ A cow is not entirely full of<BR> | |--/ | * milk some of it is hamburger!<BR> w w w w </BLOCKQUOTE></DIV>