Re: [http-state] parser rules of draft-ietf-httpstate-cookie-22
Adam Barth <ietf@adambarth.com> Tue, 01 March 2011 21:19 UTC
Return-Path: <ietf@adambarth.com>
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 257733A6AE6 for <http-state@core3.amsl.com>; Tue, 1 Mar 2011 13:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.856
X-Spam-Level:
X-Spam-Status: No, score=-2.856 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 y2BcjLD+o+NM for <http-state@core3.amsl.com>; Tue, 1 Mar 2011 13:19:19 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id B0CCA3A6ADD for <http-state@ietf.org>; Tue, 1 Mar 2011 13:19:18 -0800 (PST)
Received: by iwl42 with SMTP id 42so5082794iwl.31 for <http-state@ietf.org>; Tue, 01 Mar 2011 13:20:22 -0800 (PST)
Received: by 10.42.227.134 with SMTP id ja6mr7334844icb.144.1299014422478; Tue, 01 Mar 2011 13:20:22 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx.google.com with ESMTPS id gy41sm6033396ibb.11.2011.03.01.13.20.19 (version=SSLv3 cipher=OTHER); Tue, 01 Mar 2011 13:20:19 -0800 (PST)
Received: by iyj8 with SMTP id 8so4857002iyj.31 for <http-state@ietf.org>; Tue, 01 Mar 2011 13:20:19 -0800 (PST)
Received: by 10.231.16.200 with SMTP id p8mr6719641iba.181.1299014419072; Tue, 01 Mar 2011 13:20:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.40.7 with HTTP; Tue, 1 Mar 2011 13:19:49 -0800 (PST)
In-Reply-To: <4D6C1900.1050005@stpeter.im>
References: <4D6A9C8D.7090401@KingsMountain.com> <4D6BF059.2010909@stpeter.im> <4D6C1900.1050005@stpeter.im>
From: Adam Barth <ietf@adambarth.com>
Date: Tue, 01 Mar 2011 13:19:49 -0800
Message-ID: <AANLkTikpoAzVhzoeqNzbKwZEpUAarTOpsBX84Ziof3FB@mail.gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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: Tue, 01 Mar 2011 21:19:20 -0000
On Mon, Feb 28, 2011 at 1:52 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote: > 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." Presumably RFC 2965. It seems RFC 2395 is an informational RFC about IP Payload Compression Using LZS. Adam > 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. > > ###
- Re: [http-state] parser rules of draft-ietf-https… =JeffH
- Re: [http-state] parser rules of draft-ietf-https… Julian Reschke
- Re: [http-state] parser rules of draft-ietf-https… =JeffH
- Re: [http-state] parser rules of draft-ietf-https… Peter Saint-Andre
- Re: [http-state] parser rules of draft-ietf-https… Peter Saint-Andre
- Re: [http-state] parser rules of draft-ietf-https… Adam Barth
- Re: [http-state] parser rules of draft-ietf-https… Peter Saint-Andre