[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 RFC 5064

Network Working Group                                          M. Duerst
Internet-Draft                                                       W3C
Expires: August 8, 2004                                 February 8, 2004


                       The Archived-At Email Header
                       draft-duerst-archived-at-00

Status of this Memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups. Note that other
    groups may also distribute working documents as Internet-Drafts.

    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time. It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at http://
    www.ietf.org/ietf/1id-abstracts.txt.

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.

    This Internet-Draft will expire on August 8, 2004.

Copyright Notice

    Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

    This memo defines a new email header, Archived-At:, to provide a
    direct link to the archived form of an individual mail message.














Duerst                   Expires August 8, 2004                 [Page 1]

Internet-Draft        The Archived-At Email Header         February 2004


Table of Contents

    1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3
    2. Syntax Definition  . . . . . . . . . . . . . . . . . . . . . . . 3
    3. Supporting Nested Lists  . . . . . . . . . . . . . . . . . . . . 3
    4. Implementation Considerations  . . . . . . . . . . . . . . . . . 3
    5. Security Considerations  . . . . . . . . . . . . . . . . . . . . 4
    6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 4
       References . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
       Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
       Intellectual Property and Copyright Statements . . . . . . . . . 5








































Duerst                   Expires August 8, 2004                 [Page 2]

Internet-Draft        The Archived-At Email Header         February 2004


1. Introduction

    [RFC2369] defines a number of header fields that can be added to
    email messages send by email distribution lists. One of them is the
    'List-Archive' header field that describes how to access archives for
    the list. This allows to access the archives as a whole, but not the
    individual message.

    There is often a need or desire to refer to the archived form of a
    single message. This memo defines a new header, 'Archived-At', to
    refer to a single message in an archive.

2. Syntax Definition

    The name of the header field is 'Archived-At'. The content of the
    header field is an URI [RFC2369] pointing to an archived version of
    the message.

    This header field is subject to the encoding and character
    restrictions for mail headers as described in [RFC2822].
    Additionally, the URI content is further restricted to the set of URI
    safe characters [RFC2396].

    OPEN ISSUE: For the current X-Archived-At: header, the syntax is very
    straightforward, just an URI, without '<' and '>', and not allowing
    for comments (or at least we haven't used them at all yet). Question:
    should we leave this as is, or move to a syntax more similar with
    [RFC2369]?

3. Supporting Nested Lists

    If a message is forwarded from a list to a sublist, and both lists
    support adding the Archived-At header field, then the sublist should
    add a new Archived-At header field without removing the already
    existing one(s).

4. Implementation Considerations

    This section shortly discusses some implementation considerations.
    Mailing list expanders and email archives are often separate pieces
    of software. This may make it difficult for the mailing list expander
    to create an 'Archived-At' header field.

    W3C uses a setup that allows to use the message id of the incoming
    mail, combined with a lookup in a database and HTTP redirection, to
    find the actual message. As an example, the URI
    "http://www.w3.org/mid/1057271304.16158.44.camel@dirk.dm93.org",
    containing the message id



Duerst                   Expires August 8, 2004                 [Page 3]

Internet-Draft        The Archived-At Email Header         February 2004


    "1057271304.16158.44.camel@dirk.dm93.org", is redirected to the usual
    mailing-list archive URI at
    http://lists.w3.org/Archives/Public/public-ietf-w3c/2003Jul/
    0000.html.

    When using the message id to create an address for the archived mail,
    care has to be taken to escape characters in the message id that are
    not allowed in the URI.

5. Security Considerations

6. Acknowledgements

    The members of the W3C system team, in particular Gerald Oskoboiny,
    Olivier Thereaux, and Jose Kahan, created the mid-based email archive
    lookup system and the experimental form of the Archived-At header.
    Pete Resnik provided the motivation for writing up this draft.

References

    [RFC2369]  Baer, J. and G. Neufeld, "The Use of URLs as Meta-Syntax
               for Core Mail List Commands and their Transport through
               Message Header Fields", RFC 2369, July 1998.

    [RFC2396]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
               Resource Identifiers (URI): Generic Syntax", RFC 2396,
               August 1998.

    [RFC2822]  Resnick, P., "Internet Message Format", RFC 2822, April
               2001.


Author's Address

    Martin Duerst (Note: Please write "Duerst" with u-umlaut wherever
                   possible, for example as "D&#252;rst in XML and HTML.)
    World Wide Web Consortium
    200 Technology Square
    Cambridge, MA  02139
    U.S.A.

    Phone: +1 617 253 5509
    Fax:   +1 617 258 5999
    EMail: duerst@w3.org
    URI:   http://www.w3.org/People/D%C3%BCrst/






Duerst                   Expires August 8, 2004                 [Page 4]

Internet-Draft        The Archived-At Email Header         February 2004


Intellectual Property Statement

    The IETF takes no position regarding the validity or scope of any
    intellectual property or other rights that might be claimed to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; neither does it represent that it
    has made any effort to identify any such rights. Information on the
    IETF's procedures with respect to rights in standards-track and
    standards-related documentation can be found in BCP-11. Copies of
    claims of rights made available for publication and any assurances of
    licenses to be made available, or the result of an attempt made to
    obtain a general license or permission for the use of such
    proprietary rights by implementors or users of this specification can
    be obtained from the IETF Secretariat.

    The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights which may cover technology that may be required to practice
    this standard. Please address the information to the IETF Executive
    Director.


Full Copyright Statement

    Copyright (C) The Internet Society (2004). All Rights Reserved.

    This document and translations of it may be copied and furnished to
    others, and derivative works that comment on or otherwise explain it
    or assist in its implementation may be prepared, copied, published
    and distributed, in whole or in part, without restriction of any
    kind, provided that the above copyright notice and this paragraph are
    included on all such copies and derivative works. However, this
    document itself may not be modified in any way, such as by removing
    the copyright notice or references to the Internet Society or other
    Internet organizations, except as needed for the purpose of
    developing Internet standards in which case the procedures for
    copyrights defined in the Internet Standards process must be
    followed, or as required to translate it into languages other than
    English.

    The limited permissions granted above are perpetual and will not be
    revoked by the Internet Society or its successors or assignees.

    This document and the information contained herein is provided on an
    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION



Duerst                   Expires August 8, 2004                 [Page 5]

Internet-Draft        The Archived-At Email Header         February 2004


    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Acknowledgement

    Funding for the RFC Editor function is currently provided by the
    Internet Society.











































Duerst                   Expires August 8, 2004                 [Page 6]


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/