[client com] [Iana-ipr] Agreement to use IETF Trust

[Jonathan Robinson]

All,

 

That position seems reasonable to me.

 

In my view, it is crucial that this is presented clearly and relatively simply to the CWG so that we can:

 

a.      Explain where we are 

b.      Get the guidance and/or support for the next steps that we need to take.

 

Thanks,

 

Jonathan

 

From: Hofheimer, Joshua T. [mailto:jhofheimer at sidley.com] 
Sent: 28 July 2016 00:44
To: Greg Shatan <gregshatanipc at gmail.com>; Client <cwg-client at icann.org>; Flanagan, Sharon <sflanagan at sidley.com>; Gregory, Holly <holly.gregory at sidley.com>; Resnick, Yael <yresnick at sidley.com>; Grapsas, Rebecca <rebecca.grapsas at sidley.com>
Subject: Re: [client com] [Iana-ipr] Agreement to use IETF Trust

 

I agree with Greg that it is premature to respond at this moment.  There does not appear to be anything structurally that would prevent the IETF Trust from acting in the proposed role.  However, CWG still needs to understand the extent to which the Trust is going to work with the community in its capacity as a steward of the IANA IP, thus we need to see how the discussions play out with the community groups weighing in on the two agreements (the IPR License and the Community Agreement).

 

Best regards,

Josh

 

Joshua Hofheimer

Sidley Austin LLP

jhofheimer at sidley.com <mailto:jhofheimer at sidley.com> 

(213) 896-6061 (LA direct)

(650) 565-7561 (Palo Alto direct)

(323) 708-2405 (cell)

 

From: Greg Shatan [mailto:gregshatanipc at gmail.com] 
Sent: Wednesday, July 27, 2016 4:04 PM
To: Client; Flanagan, Sharon; Hofheimer, Joshua T.; Gregory, Holly; Resnick, Yael; Grapsas, Rebecca
Subject: Fwd: [Iana-ipr] Agreement to use IETF Trust

 

All,

 

We need to consider this question and how to answer it.  I would say the following right now:

 

1.  It's premature, since we (this group) have not yet discussed or analyzed what we learned on the call.

2.  I'ts premature, since the full CWG-IANA has not done the same.

3.  It's premature, because it depends on how the IETF Trust reacts to the Community Agreement (and to a somewhat lesser extent, the License Agreement).  In other words, the Trust is not really suitable, but we can hopefully make it acceptable through the Community Agreement and the License Agreement, unless the IETF Trust refuses to do so.

 

I realize we don't have much time before the call tomorrow at 14:00 UTC, but some thoughts from this group would be useful.  I would be willing to get on a prep call before the main call, but I realize that's short notice, especially since the Europeans are late in the evening, and the prep call would be quite early for the U.S. West Coasters (making availablity awkward).  Absent that, some written reflections would be helpful.  

 

Greg

 

 

---------- Forwarded message ----------
From: Alan Barrett <alan.barrett at afrinic.net <mailto:alan.barrett at afrinic.net> >
Date: Wed, Jul 27, 2016 at 8:50 AM
Subject: [Iana-ipr] Agreement to use IETF Trust
To: iana-ipr at nro.net <mailto:iana-ipr at nro.net> 


Does the names community now agree that the IETF Trust is an acceptable home for the IANA IPR, or is there still any doubt?

Alan Barrett
_______________________________________________
Iana-ipr mailing list
Iana-ipr at nro.net <mailto:Iana-ipr at nro.net> 
https://www.nro.net/mailman/listinfo/iana-ipr <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.nro.net_mailman_listinfo_iana-2Dipr&d=CwMFaQ&c=Od00qP2XTg0tXf_H69-T2w&r=PyftdYkqjEDMIx5o_kyQ1bCTTkOV655ea67oiCGUI9M&m=TqZzzjSTANGQeLfKy2JSuK1jYmkjNl8B2KatuxNoLbo&s=5i25143YoaS4FOL5TKvzZQ4n-TpMR-08QtVzUH3GN5Y&e=> 

 

 

****************************************************************************************************
This e-mail is sent by a law firm and may contain information that is privileged or confidential.
If you are not the intended recipient, please delete the e-mail and any attachments and notify us
immediately.

****************************************************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-client/attachments/20160728/786b5336/attachment-0001.html>