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

Ted Hardie <> Wed, 29 September 2010 18:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9F31E3A6D32 for <>; Wed, 29 Sep 2010 11:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.039
X-Spam-Status: No, score=-2.039 tagged_above=-999 required=5 tests=[AWL=0.560, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6ooUjmRvJINp for <>; Wed, 29 Sep 2010 11:14:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C7ACB3A6C57 for <>; Wed, 29 Sep 2010 11:13:59 -0700 (PDT)
Received: by qyk2 with SMTP id 2so1657654qyk.10 for <>; Wed, 29 Sep 2010 11:14:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=IzWKuiMGf59IGSA5X7MGzEXLGEPM95iLom3o66sCcFM=; b=Kb9zR1qXuq6KBdZxkZCkvSM2080XnYxbVxEWVmNvwO3p1kKmkz53ubVNe1pnpVvxGY Oj/ItH8K1j2zo+zwnDCijBet6nD1UXxVk2awnmx7Ke0LkKMGSUNBn+mXG3NTERthdrnQ jwAHia2o8e0B5urGMt7D2dtBjUKduwf6yw/7w=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ixE7XJoEnxPyO1gU6NCbUgW9S+GWZtAWe5q+XkXs4945o8dZaqirZdXOx82Z/sGi4i i+WmE4Qh1ZLimGyK6rljyJheZYql35tEibegv1kSZ3OnZhMU38uwLDLi823zcNuJg1ju XKJA9ajp39SviRC0BgJs5nNiNUbirGUEwYHCA=
MIME-Version: 1.0
Received: by with SMTP id n28mr1430597qak.175.1285784080212; Wed, 29 Sep 2010 11:14:40 -0700 (PDT)
Received: by with HTTP; Wed, 29 Sep 2010 11:14:40 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Wed, 29 Sep 2010 11:14:40 -0700
Message-ID: <>
From: Ted Hardie <>
To: Herbert Van de Sompel <>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "Michael L. Nelson" <>,
Subject: Re: [Ietf-message-headers] provisional registration Memento-Datetime header
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 29 Sep 2010 18:14:03 -0000


First, I would suggest that the pointer given in the specification document
be to the introduction document (
because leaping into the middle of the guide cited doesn't tell you anything
about what this is for.  Without that, it is sort of hard to tell
whether the header
is well-specified.

Second, I would suggest that you include in the linked document (
guide or other)
ABNF or similar pseudo-code indicating what you expect in the two
headers you are
dealing with.  This would tell a develop whether or not q-factors are permitted,
for example.

Third, I would suggest you consider a modification similar to that in
allowing you to include a series of time values and q factors for
them.  If you would really
like August 28, 1963, but would okay with August 29, 1963 or August
30, 1963, the
q-factors would allow you indicate which would be better.  I also
strongly suspect
that if you don't do this some bright spark will do it for you later,
as we've seen
q-factor additions crop up to Accept headers in a variety of "Interesting" ways.


Ted Hardie

On Wed, Sep 29, 2010 at 10:18 AM, Herbert Van de Sompel
<> wrote:
>    Header field name: Memento-Datetime
>    Applicable protocol: http
>    Status: provisional
>    Author/Change controller: Herbert Van de Sompel,, Los
> Alamos National Laboratory,
>    Specification document(s):
>    Related information:
> Van de Sompel, H., Sanderson, R., Nelson, M.L., Balakireva, L., Ainsworth,
> S., Shankar, H. (2010) An HTTP-Based Versioning Mechanism for Linked Data.
> Proceedings of the 3rd Workshop on Linked Data on the Web (LDOW2010).Arxiv
> preprint.
> Van de Sompel, H., Nelson, M.L., Sanderson, R., Balakireva, L., Ainsworth,
> S., Shankar, H. (2009) Memento: Time Travel for the Web. Arxiv preprint.
> _______________________________________________
> Ietf-message-headers mailing list