Re: New Version Notification - draft-nottingham-http-link-header-07.txt

Mark Nottingham <mnot@mnot.net> Fri, 29 January 2010 04:25 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BA933A67EA for <apps-discuss@core3.amsl.com>; Thu, 28 Jan 2010 20:25:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.727
X-Spam-Level:
X-Spam-Status: No, score=-3.727 tagged_above=-999 required=5 tests=[AWL=-1.128, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WtN96wKQP5cY for <apps-discuss@core3.amsl.com>; Thu, 28 Jan 2010 20:25:19 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 3F1E23A6781 for <discuss@apps.ietf.org>; Thu, 28 Jan 2010 20:25:19 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.167.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A435922E258; Thu, 28 Jan 2010 23:25:37 -0500 (EST)
Subject: Re: New Version Notification - draft-nottingham-http-link-header-07.txt
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <62C36D7B-2385-47AB-8A92-DEA15A81B99E@mac.com>
Date: Fri, 29 Jan 2010 15:25:34 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <08D686C3-17DD-4179-93A3-710728DA991B@mnot.net>
References: <20100119053002.5CD613A683B@core3.amsl.com> <E4FF7733-D744-4AC3-AB99-66A12868E4CE@mnot.net> <A70E9FE8-512E-42A1-8523-042368DABBBC@subbu.org> <EA551C32-6AC0-4AE1-AB22-0BA8876022C9@mac.com> <0460AF05-93FE-41D1-8E7D-D2FE6889C1F9@subbu.org> <62C36D7B-2385-47AB-8A92-DEA15A81B99E@mac.com>
To: Jan Algermissen <algermissen1971@mac.com>
X-Mailer: Apple Mail (2.1077)
Cc: Apps Discuss <discuss@apps.ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2010 04:25:20 -0000

No, the extension fields are in the registry itself; e.g., by adding a "foo" field to it, you add a "foo" field to every registered link relation type, in the registry (NOT on the wire). 


On 23/01/2010, at 8:53 AM, Jan Algermissen wrote:

> 
> On Jan 22, 2010, at 7:19 PM, Subbu Allamaraju wrote:
> 
>> You mean "link-extension" params?
> 
> Hmm, no I am getting confused :-)
> 
> I;d say link-extension == field.
> 
> Mark?
> 
> Jan
> 
> 
> 
>> 
>> Subbu
>> 
>> On Jan 20, 2010, at 11:37 PM, Jan Algermissen wrote:
>> 
>>> 
>>> On Jan 20, 2010, at 10:38 PM, Subbu Allamaraju wrote:
>>> 
>>>> The usage of fields is not clear. Sec. 6.3 says that "entries in the Link Relation Type Registry can be extended with application-specific data". But the BNF in Sec. 5 does not specify fields. Could you clarify the intent of fields?
>>> 
>>> I understand fields to be meant as link relation specific parameters.
>>> 
>>> Jan
>>> 
>>> 
>>> 
>>>> 
>>>> Subbu
>>>> 
>>>> On Jan 18, 2010, at 9:31 PM, Mark Nottingham wrote:
>>>> 
>>>>> 
>>>>> 
>>>>> Begin forwarded message:
>>>>> 
>>>>>> From: Internet-Draft@ietf.org
>>>>>> Date: 19 January 2010 4:30:02 PM AEDT
>>>>>> To: mnot@pobox.com, draft-nottingham-http-link-header@tools.ietf.org,lisa.dusseault@gmail.com
>>>>>> Subject: New Version Notification - draft-nottingham-http-link-header-07.txt
>>>>>> 
>>>>>> New version (-07) has been submitted for draft-nottingham-http-link-header-07.txt.
>>>>>> http://www.ietf.org/internet-drafts/draft-nottingham-http-link-header-07.txt
>>>>>> Sub state has been changed to AD Follow up from New Id Needed
>>>>>> 
>>>>>> Diff from previous version:
>>>>>> http://tools.ietf.org/rfcdiff?url2=draft-nottingham-http-link-header-07
>>>>>> 
>>>>>> IETF Secretariat.
>>>>> 
>>>>> 
>>>>> --
>>>>> Mark Nottingham     http://www.mnot.net/
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> -----------------------------------
>>> Jan Algermissen, Consultant
>>> 
>>> Mail: algermissen@acm.org
>>> Blog: http://www.nordsc.com/blog/
>>> Work: http://www.nordsc.com/
>>> -----------------------------------
>>> 
>>> 
>>> 
>> 
>> 
> 
> -----------------------------------
> Jan Algermissen, Consultant
> 
> Mail: algermissen@acm.org
> Blog: http://www.nordsc.com/blog/
> Work: http://www.nordsc.com/
> -----------------------------------
> 
> 
> 


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