ICANN ICANN Email List Archives

[bc-gnso]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [bc-gnso] BC on .net renewal - Version 3, to be submitted 10-May-2011

  • To: Steve DelBianco <sdelbianco@xxxxxxxxxxxxx>, "bc-gnso@xxxxxxxxx" <bc-gnso@xxxxxxxxx>
  • Subject: Re: [bc-gnso] BC on .net renewal - Version 3, to be submitted 10-May-2011
  • From: Frederick Felman <Frederick.Felman@xxxxxxxxxxxxxxx>
  • Date: Tue, 10 May 2011 17:29:42 +0000

well drafted, thanks to all who created and participated in the debate over 
content.

From: Steve DelBianco 
<sdelbianco@xxxxxxxxxxxxx<mailto:sdelbianco@xxxxxxxxxxxxx>>
Date: Tue, 10 May 2011 01:58:14 +0000
To: "bc-gnso@xxxxxxxxx<mailto:bc-gnso@xxxxxxxxx>" 
<bc-gnso@xxxxxxxxx<mailto:bc-gnso@xxxxxxxxx>>
Subject: [bc-gnso] BC on .net renewal - Version 3, to be submitted 10-May-2011

Recap of BC discussion and review of our comments on .net renewal:

21-Apr member call:  BC members our approach for this comment, and there was 
universal support to request Verisign to have a "Thick WHOIS" service in .NET   
 This was 21 days before the comment due date of 10-May.

3-May: we circulated draft written comment by Rapporteurs Elisa Cooper and 
Mikey O'Connor.  (8 days before deadline).  This draft proposed two additional 
requests based on new gTLD registry contract requirements:
 - Add TM Claims Service once the TM Clearinghouse is operating.
 - Add URS  (Uniform Rapid Suspension)

4-May:  Philip Sheppard offered a general principle: "The ICANN contract 
renewal process should be the opportunity to upgrade older contracts to the new 
standards."    Rapporteurs accepted this proposal.

8-May:   Phil Corwin questioned the rationale for requiring URS and TM Claims.  
I advised Phil that the BC charter calls for discussion and/or vote only when 
10% of membership (5 members) object to a proposed position.

Phil also pointed out that the URS and TM Claims proposals were circulated with 
8 days of review period, which is less than the 14 days required per charter.

Recommendation of vice chair for policy coordination:

Today, I asked Elisa and Mikey to consider revising the draft comment to stick 
with Thick Whois, which was appropriately noticed (21 days) and for which no 
opposition was noted.

Response from BC Rapporteurs Elisa Cooper and Mikey O'Connor:

Elisa and Mikey quickly responded with the attached version 3, adding Philip 
Sheppard's principle, retaining the recommendation for Thick Whois, and 
dropping recommendations for URS and TM Claims Service in .net

Next steps:

Please review version 3 (attached) since this will be submitted 10-May unless 
10% of members object.

I also invite BC members to examine new gTLD registry contract requirements 
once the guidebook is finalized, so the BC can determine which requirements 
should apply when existing gTLD contracts are up for renewal.

I encourage any BC member to submit their own individual / corporate views on 
this and all ICANN public comment items.

Thanks to all members for conducting such a civil and practical discussion with 
due attention to the BC charter.

Thanks especially to Elisa and Mikey for their work as our rapporteurs.

--Steve


From:  Steve DelBianco
Sent: Tuesday, May 03, 2011 5:12 PM
To: 'bc-GNSO@xxxxxxxxx<mailto:'bc-GNSO@xxxxxxxxx> GNSO list'
Subject: [bc-gnso] Draft BC comment on proposed .NET Renewal

ICANN is gathering responses to the proposed renewal of .NET registry contract.
Attached is a discussion draft for BC response prepared by Elisa Cooper  (with 
edits by Mikey O'Connor and Steve DelBianco)

On our 21-April BC member call, we discussed our approach for this comment, and 
there was universal support to request Verisign to have a "Thick WHOIS" service 
in .NET

Elise and Mikey added two additional requests based on new gTLD registry 
contract requirements:
 - Add TM Claims Service once the TM Clearinghouse is operating.
 - Add URS  (Uniform Rapid Suspension)

ICANN's Comment period closes 10-May.    Our member call on 21-Apr was 21 days 
before deadline, and today's draft is circulated 8 days before deadline.

We can submit this response later if members feel they need the entire 14-day 
review and discussion period.
Please review and post your suggestions/edits as soon as possible.   If there 
are no disagreements noted by 10-May, this response will be adopted without a 
voting period, and posted to ICANN.

For topic background, see http://icann.org/en/public-comment/#net-renewal
Thanks again to Elisa Cooper and Mikey O'Connor for drafting this comment.

Regards,
Steve DelBianco
Vice chair for policy coordination
________________________________





<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy