ICANN ICANN Email List Archives

[bc-gnso]


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

Re: [bc-gnso] Re: Business Constituency comment on Board Consideration of IRTP-B Recommendations

  • To: Phil Corwin <psc@xxxxxxxxxxx>, "Mike O'Connor" <mike@xxxxxxxxxx>, Steve DelBianco <sdelbianco@xxxxxxxxxxxxx>
  • Subject: Re: [bc-gnso] Re: Business Constituency comment on Board Consideration of IRTP-B Recommendations
  • From: Steve DelBianco <sdelbianco@xxxxxxxxxxxxx>
  • Date: Thu, 9 Feb 2012 01:13:40 +0000

That's why we directed this request to Mikey and Chris instead of Phil.

No worries — I will amend our August comment and submit.
--Steve

From: Phil Corwin <psc@xxxxxxxxxxx<mailto:psc@xxxxxxxxxxx>>
Date: Wed, 8 Feb 2012 23:47:27 +0000
To: Mike O'Connor <mike@xxxxxxxxxx<mailto:mike@xxxxxxxxxx>>, Steve DelBianco 
<sdelbianco@xxxxxxxxxxxxx<mailto:sdelbianco@xxxxxxxxxxxxx>>
Cc: Chris Chaplow <chris@xxxxxxxxxxxxx<mailto:chris@xxxxxxxxxxxxx>>, bc - GNSO 
list <bc-gnso@xxxxxxxxx<mailto:bc-gnso@xxxxxxxxx>>
Subject: RE: [bc-gnso] Re: Business Constituency comment on Board Consideration 
of IRTP-B Recommendations

That’s for the current, ongoing IRTP-C WG, where they are still in the planning 
rather than very much substantive stages.

The comment period is for one recommendation from  last year’s IRTP-B.

Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/cell

Twitter: @VlawDC

"Luck is the residue of design" -- Branch Rickey

From: owner-bc-gnso@xxxxxxxxx<mailto:owner-bc-gnso@xxxxxxxxx> 
[mailto:owner-bc-gnso@xxxxxxxxx] On Behalf Of Mike O'Connor
Sent: Wednesday, February 08, 2012 6:20 PM
To: Steve DelBianco
Cc: Chris Chaplow; bc - GNSO list
Subject: [bc-gnso] Re: Business Constituency comment on Board Consideration of 
IRTP-B Recommendations

i thought Phil Corwin signed up to be rapporteur on this one.

i've been pretty steadily saying that i can't rapporteur this one, so i'd be 
happy to participate in a conference call with a rapporteur but i just can't 
dive in at the review/edit level.

sorry to be such a louse -- but i just can't.

sorry,

mikey


On Feb 8, 2012, at 11:36 AM, Steve DelBianco wrote:


Mikey and Chris — following up on today's BC member call.

As our leads on IRTP-B, could you please look at the comment we submitted last 
August (below), and edit to fit the current Public Comment opportunity 
(Link<http://www.icann.org/en/public-comment/irtp-b-rec9-part2-23jan12-en.htm>)?

This comment is due 13-Feb-2012.

Thanks,
Steve

From: Steve DelBianco 
<sdelbianco@xxxxxxxxxxxxx<mailto:sdelbianco@xxxxxxxxxxxxx>>
Date: Mon, 8 Aug 2011 15:16:54 -0400
To: <irtp-b-recommendations@xxxxxxxxx<mailto:irtp-b-recommendations@xxxxxxxxx>>
Cc: "'bc-GNSO@xxxxxxxxx<mailto:'bc-GNSO@xxxxxxxxx> GNSO list'" 
<bc-gnso@xxxxxxxxx<mailto:bc-gnso@xxxxxxxxx>>
Subject: Business Constituency comment on Board Consideration of IRTP-B 
Recommendations

The Business Constituency (BC) endorses the recommendations made by the IRTP-B 
Working Group and encourages ICANN Board members to vote in favor of the motion 
as drafted.

If Board members have issues which prevent them from supporting the motion, the 
BC urges the Board refer the issue back to the GNSO Council which can ask the 
IRTP-B working group to review the Board's feedback, and perhaps modify 
recommendations where appropriate.

This document was reviewed and approved by BC members in accordance with our 
charter.
--
Steve DelBianco
Vice chair for policy coordination
ICANN Business Constituency
http://Www.bizconst.org<http://Www.bizconst.org/>




- - - - - - - - -
phone    651-647-6109
fax                          866-280-2356
web        http://www.haven2.com
handle   OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)

________________________________

No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 10.0.1424 / Virus Database: 2112/4796 - Release Date: 02/08/12


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

Privacy Policy | Terms of Service | Cookies Policy