ICANN/GNSO GNSO Email List Archives

[council]


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

[council] RE: IPC Support for Letter of Instruction regarding IANA IPR

  • To: "James M. Bladel" <jbladel@xxxxxxxxxxx>, GNSO Council List <council@xxxxxxxxxxxxxx>
  • Subject: [council] RE: IPC Support for Letter of Instruction regarding IANA IPR
  • From: Phil Corwin <psc@xxxxxxxxxxx>
  • Date: Sat, 1 Oct 2016 00:09:19 +0000
  • Accept-language: en-US
  • Cc: Greg Shatan <gregshatanipc@xxxxxxxxx>
  • In-reply-to: <8AC83481-A00E-4E5B-9BAD-211324B4F555@godaddy.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <CA+aOHUTDVDVhEXMm2XJxNvkDO0cu7MiojhE5HFcoa+T9QaAfgQ@mail.gmail.com> <8AC83481-A00E-4E5B-9BAD-211324B4F555@godaddy.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AQHSG2g7QaBJl75osUWNDL99CoJBMaCSSN+AgABwLWA=
  • Thread-topic: IPC Support for Letter of Instruction regarding IANA IPR

Chiming in from the BC, no objections have been heard so we are fine with GNSO 
inclusion.

Have a good transition weekend, all.

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-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On 
Behalf Of James M. Bladel
Sent: Friday, September 30, 2016 6:27 PM
To: GNSO Council List
Cc: Greg Shatan
Subject: [council] FW: IPC Support for Letter of Instruction regarding IANA IPR

Councilors –

Please see the note below from Greg Shatan on behalf of the IPC, and also some 
important context on the CWG Instruction Letter.

Thank you,

J.


From: Greg Shatan <gregshatanipc@xxxxxxxxx<mailto:gregshatanipc@xxxxxxxxx>>
Date: Friday, September 30, 2016 at 17:16
To: "James M. Bladel" <jbladel@xxxxxxxxxxx<mailto:jbladel@xxxxxxxxxxx>>, 
Heather Forrest 
<Heather.Forrest@xxxxxxxxxx<mailto:Heather.Forrest@xxxxxxxxxx>>, "Donna Austin 
(Donna.Austin@xxxxxxxxxxx<mailto:Donna.Austin@xxxxxxxxxxx>)" 
<Donna.Austin@xxxxxxxxxxx<mailto:Donna.Austin@xxxxxxxxxxx>>, Glen de Saint Géry 
<glen@xxxxxxxxx<mailto:glen@xxxxxxxxx>>
Cc: Kiran Malancharuvil 
<Kiran.Malancharuvil@xxxxxxxxxxxxxxx<mailto:Kiran.Malancharuvil@xxxxxxxxxxxxxxx>>,
 Lori Schulman <lschulman@xxxxxxxx<mailto:lschulman@xxxxxxxx>>, "Paul McGrady 
(Policy)" <policy@xxxxxxxxxxxxxxx<mailto:policy@xxxxxxxxxxxxxxx>>, "Steven J. 
Metalitz" <met@xxxxxxx<mailto:met@xxxxxxx>>, "Vayra, Fabricio (Perkins Coie)" 
<FVayra@xxxxxxxxxxxxxxx<mailto:FVayra@xxxxxxxxxxxxxxx>>
Subject: IPC Support for Letter of Instruction regarding IANA IPR

James,

On behalf of the IPC, I would like to convey to you and to the GNSO Council 
that the IPC supports GNSO inclusion in the Letter of Instruction and 
responding "yes" to the CWG Co-Chairs.

Speaking as a GNSO-appointed member of the CWG and as a member of the IANA IPR 
collaborative team that worked with the numbers and protocol parameters 
communities to complete this aspect of transition planning and implementation: 
I'd like to clarify the limited but significant role that this Letter plays.  
The Letter of Instruction directs ICANN to sign the Community Agreement, one of 
several agreements that are part of the IANA IPR transfer, which in turn is 
part of the IANA transition.  The Community Agreement gives the three 
operational communities oversight of the IETF Trust, as the new owner of the 
IANA IPR.  As the Names Community has no legal entity to act on its behalf, 
ICANN is being directed to do so in this Letter, which also constrains ICANN 
from taking other actions that might seem possible based on having its 
signature on the agreement.  (More simply put, ICANN is acting as the Names 
Community's avatar.)  This small act by the GNSO further smooths the way for 
the IANA transition.

Since the request to enjoin the IANA transition in federal court in Texas has 
been DENIED, now is the time to move forward.

Best regards,

Greg Shatan
IPC President
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7797 / Virus Database: 4656/13076 - Release Date: 09/24/16


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