[http-state] Is this an omission in the parser rules of draft-ietf-httpstate-cookie-21?

"Remy Lebeau" <remy@lebeausoftware.org> Thu, 03 February 2011 02:01 UTC

Return-Path: <remy@lebeausoftware.org>
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 DDC0C3A67AE for <http-state@core3.amsl.com>; Wed, 2 Feb 2011 18:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 Qv+ZYsJd9XaE for <http-state@core3.amsl.com>; Wed, 2 Feb 2011 18:01:33 -0800 (PST)
Received: from smtpoutwbe03.prod.mesa1.secureserver.net (smtpoutwbe03.prod.mesa1.secureserver.net [208.109.78.114]) by core3.amsl.com (Postfix) with SMTP id 35E433A67A7 for <http-state@ietf.org>; Wed, 2 Feb 2011 18:01:32 -0800 (PST)
Received: (qmail 1305 invoked from network); 3 Feb 2011 02:04:53 -0000
Received: from unknown (HELO gem-wbe04.prod.mesa1.secureserver.net) (64.202.189.36) by smtpoutwbe03.prod.mesa1.secureserver.net with SMTP; 3 Feb 2011 02:04:53 -0000
Received: (qmail 15803 invoked by uid 99); 3 Feb 2011 02:04:53 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 76.93.119.83
User-Agent: Web-Based Email 5.3.08
Message-Id: <20110202190453.f00013ceab8fb1928885c5c172fbfd4a.158515956e.wbe@email00.secureserver.net>
From: "Remy Lebeau" <remy@lebeausoftware.org>
To: http-state@ietf.org
Date: Wed, 02 Feb 2011 19:04:53 -0700
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 03 Feb 2011 12:03:06 -0800
Subject: [http-state] =?utf-8?q?Is_this_an_omission_in_the_parser_rules_of?= =?utf-8?q?_draft-ietf-httpstate-cookie-21=3F?=
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: Thu, 03 Feb 2011 17:32:42 -0000

RFC 2109 allows cookie and attribute values to be wrapped in quotation
marks, but ietf-httpstate-cookie-21's definitions of "cookie-value" and
"cookie-av" do not seem to allow for that.  Or am I missing something? 
The examples in RFC 2109 fail to parse properly if the draft definitions
are strictly used (for instance, processing a "Path" attribute can fail
because the first character may be <"> instead of "/" unless <'>
characters are stripped off during parsing).

Also in the draft, "cookie-value" is defined as:

  cookie-value      = token / ""

Is the <""> portion a typo, or was it meant to be more like this
instead?

  cookie-value      = token / <"> token <">