Re: [http-state] Minor things concerning draft-ietf-httpstate-cookie-01

Adam Barth <ietf@adambarth.com> Tue, 12 January 2010 11:01 UTC

Return-Path: <adam@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 C86A23A6919 for <http-state@core3.amsl.com>; Tue, 12 Jan 2010 03:01:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 JnFtg7NOgOkR for <http-state@core3.amsl.com>; Tue, 12 Jan 2010 03:01:01 -0800 (PST)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id 16C373A672F for <http-state@ietf.org>; Tue, 12 Jan 2010 03:01:01 -0800 (PST)
Received: by pwi20 with SMTP id 20so2194338pwi.29 for <http-state@ietf.org>; Tue, 12 Jan 2010 03:00:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.142.66.27 with SMTP id o27mr752753wfa.216.1263294056194; Tue, 12 Jan 2010 03:00:56 -0800 (PST)
In-Reply-To: <4B4C54F6.3060307@jondos.de>
References: <4B476F1E.7080003@KingsMountain.com> <7789133a1001080950s24c1df4fg742546be69f657ee@mail.gmail.com> <4B4C48C2.8020209@jondos.de> <7789133a1001120234i727449c3s69fb6691eae77cea@mail.gmail.com> <4B4C54F6.3060307@jondos.de>
From: Adam Barth <ietf@adambarth.com>
Date: Tue, 12 Jan 2010 03:00:36 -0800
Message-ID: <7789133a1001120300w5c027595xabe2c82e1e95fc66@mail.gmail.com>
To: Georg Koppen <g.koppen@jondos.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: IETF httpstate WG <http-state@ietf.org>
Subject: Re: [http-state] Minor things concerning draft-ietf-httpstate-cookie-01
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, 12 Jan 2010 11:01:01 -0000

On Tue, Jan 12, 2010 at 2:54 AM, Georg Koppen <g.koppen@jondos.de> wrote:
>>> 5) Section 5 says that there are some algorithms specified for some
>>> tasks concerning the cookie protocol but the user agents do not have to
>>> follow these ("user agents are free to implement the cookie
>>> protocol..."). But, for instance in Section 5.1.1., there it says "The
>>> user agent MUST use the following algorithm..." Thus, am I free to
>>> implement it differently or not? It's a bit confusing...
>>
>> The operative requirement is:
>>
>>       <t>Although some parts of the cookie protocol are specified
>>       algorithmically, user agents are free to implement the cookie protocol
>>       in any manner as long as their resultant behavior is "black-box"
>>       indistinguishable from a user agent that implements the protocol as
>>       described.</t>
>>
>> Is there some way we can be clearer that user agents are free to
>> implement the protocol however they like?
>
> Why MUST the user use these algorithms? Wouldn't it be enough if the
> user MAY use them? I mean, they are free to implement the protocol
> however they want to do it, provided they come to the same results.

The goal is to require that they come up with the same results.  I
guess we could say something more elaborate each time.  It just seems
a bit wordy.  Any suggestions for text to use?

Adam