Re: [Ietf-message-headers] provisional registration Accept-Datetime header

Bjoern Hoehrmann <derhoermi@gmx.net> Thu, 20 May 2010 15:35 UTC

Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf-message-headers@core3.amsl.com
Delivered-To: ietf-message-headers@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96C7A3A6C91 for <ietf-message-headers@core3.amsl.com>; Thu, 20 May 2010 08:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, 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 dVLC1PX0XLIA for <ietf-message-headers@core3.amsl.com>; Thu, 20 May 2010 08:35:03 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id DB8F43A6C56 for <Ietf-message-headers@ietf.org>; Thu, 20 May 2010 08:34:55 -0700 (PDT)
Received: (qmail invoked by alias); 20 May 2010 15:34:48 -0000
Received: from dslb-094-222-156-193.pools.arcor-ip.net (EHLO hive) [94.222.156.193] by mail.gmx.net (mp069) with SMTP; 20 May 2010 17:34:48 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19KE4cWVwFKz6UeKXPKtXupKmBibwYVkbvI4m8B+F mQVZrmdzMV7BRw
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Herbert van de Sompel <hvdsomp@gmail.com>
Date: Thu, 20 May 2010 17:34:50 +0200
Message-ID: <n8lav5di99ku4a3n6rcqm0mi3t3t0hrm8p@hive.bjoern.hoehrmann.de>
References: <C82A7102-178E-43DA-8A34-9BACB17B681E@gmail.com> <k4jav51ivs4pkrdcgjdnp9q9vknte3q2ll@hive.bjoern.hoehrmann.de> <4BF5511D.7040101@gmx.de> <AANLkTilzaNOqTf3s84MsXaJrHrap00qx00q4HC-g9-C3@mail.gmail.com>
In-Reply-To: <AANLkTilzaNOqTf3s84MsXaJrHrap00qx00q4HC-g9-C3@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "Michael L. Nelson" <mln@cs.odu.edu>, Ietf-message-headers@ietf.org
Subject: Re: [Ietf-message-headers] provisional registration Accept-Datetime header
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-message-headers>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 15:35:04 -0000

* Herbert van de Sompel wrote:
>Forgive me for the brevity, but I thought I was following the procedure
>described in http://tools.ietf.org/html/rfc3864.
>
>=> For a very brief overview of the use of the proposed headers, see
>http://tools.ietf.org/html/rfc3864 , section "The Memento Solution, Part 1".
>
>=> The templates list 2 email addresses: my personal one and the
>memento-dev@googlegroups.com group where tech discussions about the Memento
>framework take place.

You cited http://www.mementoweb.org/guide/http/ as the specification for
the two header fields. I think the specification (not the registration)
should include an email address where comments on the headers could be
sent and it should include a definition for the header fields. Consider
how RFC 2616 defines the 'Allow' header, to pick a random example:

  The Allow entity-header field lists the set of methods supported
  by the resource identified by the Request-URI. The purpose of this
  field is strictly to inform the recipient of valid methods
  associated with the resource. An Allow header field MUST be
  present in a 405 (Method Not Allowed) response.

      Allow   = "Allow" ":" #Method

This defines what kind of header it is, what its purpose is, and what
the syntax for the header field ist. There is no corresponding text in
your specification, it is not clear, for example, whether one can use
other time zones than GMT in the header fields. I am not saying the two
headers cannot pass review without adding the email address and a good
definition, but it would sure be nice to have those.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/