Re: [http-state] consensus call: cookie server conformance

"Anne van Kesteren" <annevk@opera.com> Sat, 29 January 2011 10:21 UTC

Return-Path: <annevk@opera.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 394883A697A for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 02:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 C5CKCksETJgM for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 02:21:51 -0800 (PST)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id D2D7E3A693A for <http-state@ietf.org>; Sat, 29 Jan 2011 02:21:50 -0800 (PST)
Received: from anne-van-kesterens-macbook-pro.local (5355737B.cm-6-6b.dynamic.ziggo.nl [83.85.115.123]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0TAOtPS019488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 29 Jan 2011 10:24:56 GMT
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: =JeffH <Jeff.Hodges@kingsmountain.com>, "Dan Winship" <dan.winship@gmail.com>
References: <4D41FA83.5040302@KingsMountain.com> <4D433C9A.7010203@gmail.com>
Date: Sat, 29 Jan 2011 11:24:57 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software
Message-ID: <op.vp2e7uyj64w2qv@anne-van-kesterens-macbook-pro.local>
In-Reply-To: <4D433C9A.7010203@gmail.com>
User-Agent: Opera Mail/11.01 (MacIntel)
X-Scanned-By: MIMEDefang 2.64 on 213.236.208.81
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 10:21:52 -0000

On Fri, 28 Jan 2011 23:00:58 +0100, Dan Winship <dan.winship@gmail.com>;  
wrote:
> -1, because Section 4 says "cookie-value=token", which is annoying
> (since it prohibits both base64 and URI encoding, both of which are
> commonly used) and unnecessary for interoperability (both existing and
> future clients will DTRT with non-token values) and widely violated by
> real-world servers that would otherwise be considered well-behaved.
>
> I suppose I could probably be happy with
>
>     cookie-value  = token | base64-string
>     base64-string = <a base64 string, defined in [RFC4648], Section 4>
>
> and then change the later Base 16 reference back to Base 64. This still
> declares lots of perfectly-interoperable servers "non-compliant", but it
> at least provides them with a sane way out.

Why would we not want to their usage conforming too?


-- 
Anne van Kesteren
http://annevankesteren.nl/