[Iana-ipr] Summary note for ICG site

Jari Arkko jari.arkko at piuha.net
Mon Sep 19 13:23:15 CEST 2016


And here as well. Thanks guys.

Jari

On 19 Sep 2016, at 14:21, Greg Shatan <gregshatanipc at gmail.com> wrote:

> Same here.
> 
> Greg
> 
> On Monday, September 19, 2016, Jonathan Robinson <jrobinson at afilias.info> wrote:
> Ditto. Jonathan
> 
> -----Original Message-----
> From: Lise Fuhr [mailto:Fuhr at etno.eu]
> Sent: 19 September 2016 11:32
> To: 'Andrew Sullivan' <ajs at anvilwalrusden.com>; Alissa Cooper <alissa at cooperw.in>
> Cc: iana-ipr at nro.net
> Subject: Re: [Iana-ipr] Summary note for ICG site
> 
> I am fine with it
> Lise
> 
> -----Original Message-----
> From: iana-ipr-bounces at nro.net [mailto:iana-ipr-bounces at nro.net] On Behalf Of Andrew Sullivan
> Sent: 17 September 2016 02:34
> To: Alissa Cooper
> Cc: iana-ipr at nro.net
> Subject: Re: [Iana-ipr] Summary note for ICG site
> 
> Looks good to me.
> 
> --
> Andrew Sullivan
> Please excuse my clumbsy thums.
> 
> > On Sep 16, 2016, at 17:10, Alissa Cooper <alissa at cooperw.in> wrote:
> >
> > Here is a draft note for posting to the ICG site.
> >
> > —
> >
> > Summary of Changes to IANA IPR Agreements
> >
> > There were seven public comments <link> submitted regarding the IANA IPR agreements, one of which was a correction to a previously submitted comment.
> >
> > One comment <http://ianacg.org/pipermail/ianaiprpubliccomment_ianacg.org/2016-September/000002.html>was about the transition in general. There was nothing actionable for the IPR agreements from this comment.
> >
> > All of the other comments were supportive of the IANA IPR agreements as written.
> >
> > As a result, no edits to the agreements were made on the basis of the public comments received.
> >
> > However, at the time the agreements were put out for public comment, there were a number of placeholders in the text that required further discussion amongst the parties to the agreements and the operational communities in order to be finalized. These items have been addressed as follows:
> >
> > ASSIGNMENT AGREEMENT
> >
> > Section 6.1: The term of indemnification has been set at 3 years.
> >
> > LICENSE AGREEMENT
> >
> > Section 4.3.c: ICANN agrees to cover cost of ongoing enforcement actions existing as of the Effective Date.
> >
> > Section 7.4: The venue of arbitration will be New York and three arbitrators will be appointed if the parties cannot agree on a single arbitrator.
> >
> > Exhibit D, Item 5: Clarification provided that the use of ‘IANA’ as an entity name is permitted in archived RFCs and other documents.
> >
> > COMMUNITY AGREEMENT
> >
> > Preamble: ICANN has been identified as the Names Community signatory.
> >
> > Section 1.24: The following definition of "Names Community" has been provided, as agreed by the CWG: [TBD].
> >
> >
> >
> > _______________________________________________
> > Iana-ipr mailing list
> > Iana-ipr at nro.net
> > https://www.nro.net/mailman/listinfo/iana-ipr
> 
> 
> _______________________________________________
> Iana-ipr mailing list
> Iana-ipr at nro.net
> https://www.nro.net/mailman/listinfo/iana-ipr
> _______________________________________________
> Iana-ipr mailing list
> Iana-ipr at nro.net
> https://www.nro.net/mailman/listinfo/iana-ipr
> 
> 
> _______________________________________________
> Iana-ipr mailing list
> Iana-ipr at nro.net
> https://www.nro.net/mailman/listinfo/iana-ipr
> _______________________________________________
> Iana-ipr mailing list
> Iana-ipr at nro.net
> https://www.nro.net/mailman/listinfo/iana-ipr

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://www.nro.net/pipermail/iana-ipr/attachments/20160919/62adee74/signature-0001.asc>


More information about the Iana-ipr mailing list