Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-21.txt

Peter Saint-Andre <stpeter@stpeter.im> Fri, 18 February 2011 13:14 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 253F33A6DEF for <http-state@core3.amsl.com>; Fri, 18 Feb 2011 05:14:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.71
X-Spam-Level:
X-Spam-Status: No, score=-102.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1hGDFUZ4EKb4 for <http-state@core3.amsl.com>; Fri, 18 Feb 2011 05:14:47 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id E7A523A6DD0 for <http-state@ietf.org>; Fri, 18 Feb 2011 05:14:43 -0800 (PST)
Received: from squire.local (dsl-251-175.dynamic-dsl.frii.net [216.17.251.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E2DF440CFF for <http-state@ietf.org>; Fri, 18 Feb 2011 06:33:34 -0700 (MST)
Message-ID: <4D5E70E4.3010706@stpeter.im>
Date: Fri, 18 Feb 2011 06:15:16 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: http-state@ietf.org
References: <20110119231502.3778.58453.idtracker@localhost> <4D37F4EE.80700@gmx.de> <4D5E127C.7080508@gmx.de> <AANLkTinGO3BfcMC9HGeAacPyic9_-fiurJJNUYEAERMe@mail.gmail.com> <4D5E6FE5.10200@stpeter.im>
In-Reply-To: <4D5E6FE5.10200@stpeter.im>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms090105030304090709010503"
Subject: Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-21.txt
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 13:14:48 -0000

On 2/18/11 6:11 AM, Peter Saint-Andre wrote:
> On 2/17/11 11:43 PM, Adam Barth wrote:
>> On Thu, Feb 17, 2011 at 10:32 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>>> On 20.01.2011 09:40, Julian Reschke wrote:
>>>> On 20.01.2011 00:15, Internet-Drafts@ietf.org wrote:
>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>> directories.
>>>>> This draft is a work item of the HTTP State Management Mechanism
>>>>> Working Group of the IETF.
>>>>>
>>>>>
>>>>> Title : HTTP State Management Mechanism
>>>>> Author(s) : A. Barth
>>>>> Filename : draft-ietf-httpstate-cookie-21.txt
>>>>> Pages : 43
>>>>> Date : 2011-01-19
>>>>> ...
>>>>
>>>> Nit: there's an unused reference to RFC 5246, probably caused by a
>>>> change in draft 20
>>>> (<http://tools.ietf.org/rfcdiff?url2=draft-ietf-httpstate-cookie-20.txt>
>>>> and
>>>>
>>>> <http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-httpstate-cookie-21.txt>).
>>>>
>>>>
>>>> There's also ABNF text that needs to be reformatted due to the width
>>>> constraints...
>>>> ...
>>>
>>> These problems are still present in draft 22...
>>
>> Fixed.
>>
>>> Also note:
>>>
>>>  -- The draft header indicates that this document obsoletes RFC2965, but the
>>>     abstract doesn't seem to mention this, which it should.
>>>
>>> (<http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-httpstate-cookie-22.txt>)
>>
>> Is there boilerplate text we should use for that?
> 
> I'll add an RFC Editor note on this point.

Done:

https://datatracker.ietf.org/doc/draft-ietf-httpstate-cookie/writeup/

Peter

-- 
Peter Saint-Andre
https://stpeter.im/