Re: [apps-discuss] IANA hanges to draft-nottingham-http-link-header

Mark Nottingham <mnot@mnot.net> Wed, 29 September 2010 07:51 UTC

Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <6.2.5.6.2.20100928222414.0abb3710@resistor.net>
Date: Wed, 29 Sep 2010 17:52:01 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA2C6FE1-3940-4B85-981C-3FACA0E6085A@mnot.net>
References: <D92B699E-32AA-4CD8-94B8-469296A4D48B@mnot.net> <6.2.5.6.2.20100928222414.0abb3710@resistor.net>
To: SM <sm@resistor.net>
Cc: Apps Discuss <discuss@apps.ietf.org>
Subject: Re: [apps-discuss] IANA hanges to draft-nottingham-http-link-header
Precedence: list

On 29/09/2010, at 3:36 PM, SM wrote:

> Hi Mark,
> At 21:25 22-09-10, Mark Nottingham wrote:
>> 3) Adding the following to the beginning of section 6.2, "Link Relation Type Registry":
>> 
>>   The underlying registry data (e.g., the XML file) must include
>>   Simplified BSD License text as described in Section 4.e of the Trust
>>   Legal Provisions (<http://trustee.ietf.org/license-info>).
> 
> Why are you specifying a license for the registry?

Because there was concern -- especially from the HTML community -- about it, because implementations need to incorporate the registry data and remain "clean" from an Open Source perspective.

We've been discussing this with IANA and the IESG Chair for a while; stay tuned.

> Section 6.2.1 sets a hard limit for approving or denying registration.   There draft defines an appeal process.  That is usual.  Can't you leave these procedures to RFC 5226?

I'm not sure what you're saying here. This text hasn't changed from the 1st LC.

Regards,

--
Mark Nottingham     http://www.mnot.net/

[apps-discuss] IANA hanges to draft-nottingham-ht… Mark Nottingham
Re: [apps-discuss] IANA hanges to draft-nottingha… SM
Re: [apps-discuss] IANA hanges to draft-nottingha… Mark Nottingham
Re: [apps-discuss] IANA hanges to draft-nottingha… SM