[http-state] cookie-date syntax and algorithm

"NARUSE, Yui" <yui.naruse@gmail.com> Fri, 22 January 2010 17:07 UTC

Return-Path: <yui.naruse@gmail.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 D5FA23A6A95 for <http-state@core3.amsl.com>; Fri, 22 Jan 2010 09:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 OUJ-BtaA++Wg for <http-state@core3.amsl.com>; Fri, 22 Jan 2010 09:07:53 -0800 (PST)
Received: from mail-px0-f186.google.com (mail-px0-f186.google.com [209.85.216.186]) by core3.amsl.com (Postfix) with ESMTP id 11C9E3A6A94 for <http-state@ietf.org>; Fri, 22 Jan 2010 09:07:53 -0800 (PST)
Received: by pxi16 with SMTP id 16so976863pxi.29 for <http-state@ietf.org>; Fri, 22 Jan 2010 09:07:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=k82qzWleR/lV/nmeb5NvJFy+cy2Qp1s54u8Eb0Jh1Ig=; b=SKd1YHtSATtsATHVvKhJw+pRCKs0oCbjZHb63yDIoIxU+os97Qr+7HYX9aA3SLgoxO +uwvgTiDxqww9S8sfG+X0mEzIU0kfM1IL7ZCH6Q/3egeI6UpmgvAB5RD5dEst8eULWyA CDR3FgQElYHFLNJiAsHWutEJLcYVtFvEE0usA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iYpvyaJqXOOnhfKr7FXyxeCwj0rjLZ0NeZt63r7vYCJOGPvxVp2wQjXTUWf7bGWQ0J cTiCu1qMuRsJWk08iavCghB6s8zG3Ah96DImUUPV1LHOUG5amj00aIPgV/MKTjOfIv9o 4FNiIrFa5Js9sckmiCJZFjJ3LRf8QE5kcIP8c=
MIME-Version: 1.0
Received: by 10.141.100.14 with SMTP id c14mr2256751rvm.4.1264180066528; Fri, 22 Jan 2010 09:07:46 -0800 (PST)
Date: Sat, 23 Jan 2010 02:07:46 +0900
Message-ID: <146d7afa1001220907y5c2fb324q668f8bb4ddf449bc@mail.gmail.com>
From: "NARUSE, Yui" <yui.naruse@gmail.com>
To: http-state@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [http-state] cookie-date syntax and algorithm
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: Fri, 22 Jan 2010 17:09:24 -0000

I sent this from naruse@airemix.jp but it seems not accepted,
so I post this again.

Anyway,
draft-ietf-httpstate-cookie-02 says in 4.1.1. Syntax,

   cookie-date       = <rfc1123-date, as defined in RFC 2616>

But you know, cookie-date is not rfc1123-date.
It's a original exotic date format.

   rfc1123-date = <Wdy, DD Mon YYYY HH:MM:SS GMT>
   rfc850-date  = <Weekday, DD-Mon-YYYY HH:MM:SS GMT>
   asctime-date = <Wdy, Month dd HH:MM:SS YYYY>
   cookie-date  = <Wdy, DD-Mon-YYYY HH:MM:SS GMT> ; not RFC 2822

Current description causes misunderstanding.

= 5.1.1.  Dates

Why it needs such a complex definition?
Its demerit is clear in ticket #7.

It seems to intend to change cookie-date from current exotic format
to exact rfc-1123-date or something in future, but why?

Recently, many specs are using ISO 8601 Date and Time format (or other
related specs).
So formats they really needed are only exotic and ISO 8601.
Current algorithm make things too complex but still can't express timezone.
So I object this.

If make cookie-date exotic or RFC 3339 (ISO 8601 related RFC),
the syntax would be following:

  cookie-date      = rfc3339-datetime / obs-cookie-date
  rfc3339-datetime = <date-time, as defined in RFC 3339>
                   ; YYYY-MM-DDTHH:MM:SSZ
                   ; YYYY-MM-DDTHH:MM:SS+09:00
  obs-cookie-date  = <Wdy, DD-Mon-YYYY HH:MM:SS GMT> ; not RFC 2822

-- 
NARUSE, Yui  <naruse@airemix.jp>


-- 
NARUSE, Yui
naruse@airemix.jp