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

=JeffH <Jeff.Hodges@KingsMountain.com> Sun, 27 February 2011 18:47 UTC

Return-Path: <Jeff.Hodges@KingsMountain.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 980943A6A00 for <http-state@core3.amsl.com>; Sun, 27 Feb 2011 10:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.776
X-Spam-Level:
X-Spam-Status: No, score=-100.776 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, 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 E0PHMtuhgHNC for <http-state@core3.amsl.com>; Sun, 27 Feb 2011 10:47:51 -0800 (PST)
Received: from oproxy2-pub.bluehost.com (oproxy2-pub.bluehost.com [67.222.39.60]) by core3.amsl.com (Postfix) with SMTP id 8B11E3A67D6 for <http-state@ietf.org>; Sun, 27 Feb 2011 10:47:51 -0800 (PST)
Received: (qmail 30446 invoked by uid 0); 27 Feb 2011 18:48:49 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy2.bluehost.com with SMTP; 27 Feb 2011 18:48:49 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=FT85KZ91LNp6+LekSPWs5QHOLvtlUFH2I2p95sO4gGGwx2ayOj424C89uCQwTP9ToNkqrsFBo/9/1/otluzX7asCfkIm6Dtdxzx4kup/g9y9aRvRm9I1s/lP2s0BmahR;
Received: from c-24-4-122-173.hsd1.ca.comcast.net ([24.4.122.173] helo=[192.168.11.10]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Ptlfl-0000o1-Eb for http-state@ietf.org; Sun, 27 Feb 2011 11:48:49 -0700
Message-ID: <4D6A9C8D.7090401@KingsMountain.com>
Date: Sun, 27 Feb 2011 10:48:45 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: IETF HTTP State WG <http-state@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
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: Sun, 27 Feb 2011 18:47:52 -0000

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.

=JeffH