Re: [http-state] parser rules of draft-ietf-httpstate-cookie-22

Peter Saint-Andre <stpeter@stpeter.im> Mon, 28 February 2011 21:51 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 7AD253A6CA2 for <http-state@core3.amsl.com>; Mon, 28 Feb 2011 13:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.63
X-Spam-Level:
X-Spam-Status: No, score=-102.63 tagged_above=-999 required=5 tests=[AWL=-0.031, 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 pKHiEYFj4dNA for <http-state@core3.amsl.com>; Mon, 28 Feb 2011 13:51:01 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id CA23B3A6A21 for <http-state@ietf.org>; Mon, 28 Feb 2011 13:51:00 -0800 (PST)
Received: from dhcp-64-101-72-185.cisco.com (dhcp-64-101-72-185.cisco.com [64.101.72.185]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E2F45400F6; Mon, 28 Feb 2011 15:11:14 -0700 (MST)
Message-ID: <4D6C1900.1050005@stpeter.im>
Date: Mon, 28 Feb 2011 14:52:00 -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: =JeffH <Jeff.Hodges@KingsMountain.com>
References: <4D6A9C8D.7090401@KingsMountain.com> <4D6BF059.2010909@stpeter.im>
In-Reply-To: <4D6BF059.2010909@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="------------ms040804080502070807050003"
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] parser rules of draft-ietf-httpstate-cookie-22
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: Mon, 28 Feb 2011 21:51:05 -0000

On 2/28/11 11:58 AM, Peter Saint-Andre wrote:
> On 2/27/11 11:48 AM, =JeffH wrote:
>> Julian noted..
>>>
>>> On 25.02.2011 18:21, =JeffH wrote:
>>>>  >>> cookie-value = *cookie-octet / ( DQUOTE *cookie-octet DQUOTE )
>>>>  >>> cookie-octet = %x21 / %x23-2B / %x2D-3A / %x3C-5B / %x5D-7E
>>>>  >>> ; ASCII characters excluding CTLs, whitespace,
>>>>  >>> ; DQUOTE, comma, semicolon, and backslash
>>>>  >>
>>>>  >> Works for me. Thanks Roy.
>>>>  >
>>>>  > In the datatracker, I've updated the RFC Editor note accordingly.
>>>>
>>>> great, thx all for sorting this out.
>>>>
>>>> Also, I'm glad you've added the comment to the ABNF above, tho one might
>>>> add..
>>>>
>>>> s/ASCII/7-bit ASCII/
>>>>
>>>> ..or something similar to explicitly indicate exclusion of %x80-FF.
>>>
>>> "US-ASCII", please.
>>
>> doh, yes of course.
>>
>> at this point I'm thinking we should add an RFC-Editor Note to the
>> effect of adding an explicit normative reference to..
>>
>>         US-ASCII. Coded Character Set - 7-Bit American Standard Code for
>>         Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986.
>>
>> We already use the term "US-ASCII" also in section 2.2 (of -cookie-22)
>> but without citation.
> 
> I agree with Julian: not an RFC Editor note (I really don't like those
> because they aren't very transparent), but a revised I-D.

The reason I don't particularly like RFC Editor notes is that they are
not very transparent (how many people watch the datatracker history?).
So here is some transparency for you...

The RFC Editor note currently on file in the datatracker is:

###

RFC Editor Note

   1. Please add the following sentence to the end of the Abstract:

      "This document obsoletes RFC 2395."

   2. In Section 4.1.1, please change:

      cookie-value     = token / *base64-character
      base64-character = ALPHA / DIGIT / "+" / "/" / "="

   to:

      cookie-value     = *cookie-octet / ( DQUOTE *cookie-octet DQUOTE )
      cookie-octet     = %x21 / %x23-2B / %x2D-3A / %x3C-5B / %x5D-7E
                       ; US-ASCII characters excluding CTLs,
                       ; whitespace DQUOTE, comma, semicolon,
                       ; and backslash

   3. In Section 2.2, please change both instances of:

      any US-ASCII character

   to:

      any [US-ASCII] character

   4. Please add the following reference:

      [US-ASCII] American National Standards Institute, "Coded
      Character Set - 7-bit American Standard Code for Information
      Interchange," ANSI X3.4, 1986.

###

Peter

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