Locating RFC [2]822 headers
Graham Klyne <GK@ninebynine.org> Wed, 19 September 2001 14:33 UTC
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id f8JEXLx18142 for ietf-822-bks; Wed, 19 Sep 2001 07:33:21 -0700 (PDT)
Received: from joy.songbird.com (IDENT:root@songbird.com [208.184.79.7]) by above.proper.com (8.11.6/8.11.3) with ESMTP id f8JEXGD18111 for <ietf-822@imc.org>; Wed, 19 Sep 2001 07:33:16 -0700 (PDT)
Received: from GK-VAIO.NineByNine.org (host213-122-182-227.btinternet.com [213.122.182.227]) by joy.songbird.com (8.9.3/8.9.3) with ESMTP id HAA27298; Wed, 19 Sep 2001 07:33:15 -0700
Message-Id: <5.1.0.14.2.20010919115724.00a007d0@joy.songbird.com>
X-Sender: gk@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 19 Sep 2001 12:29:16 +0100
To: ietf-822@imc.org
From: Graham Klyne <GK@ninebynine.org>
Subject: Locating RFC [2]822 headers
Cc: Jacob Palme <jpalme@dsv.su.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>
How does one reliably track down all of the defined RFC [2]822 headers? That is, when proposing a new header, how is one to be sure that it is not already defined somewhere? From the RFC index: 0822 Standard for the format of ARPA Internet text messages. D. Crocker. Aug-13-1982. (Format: TXT=109200 bytes) (Obsoletes RFC0733) (Obsoleted by RFC2822) (Updated by RFC1123, RFC1138, RFC1148, RFC1327, RFC2156) (Also STD0011) (Status: STANDARD) and 2822 Internet Message Format. P. Resnick, Editor. April 2001. (Format: TXT=110695 bytes) (Obsoletes RFC0822) (Status: PROPOSED STANDARD) Apart from the RFC822 "updated by" references to MIXER, there is no indication here that MIME adds a new set of header names that occupy (part of) the same naming scope as RFC [2]822 headers. Also, there are numerous other documents that define additional headers that may appear in an Internet message. The usual IETF way to deal with these situations is to have an IANA registry of values. But none exists for message headers (I can find no reference to RFC822 or email messages in http://www.iana.org/numbers.htm). The nearest to a registry we have seems to be Jacob Palme's RFC 2076 and more recent Internet Draft updates (currently draft-palme-mailext-headers-05.txt). I would like to suggest taking Jacob's draft, and: (a) adding an IANA considerations section to create a message header registry (or creating a new companion document) (b) incorporating all of the standards-track-defined headers noted in Jacob's draft into the registry (c) issuing the result as BCP RFC(s) (d) noting in the RFC index that the document updates RFC 2822. Before taking on any drafting work, I'd like to gauge the sense of whether this general approach is likely to fly. ------------ Graham Klyne (GK@ACM.ORG)
- Re: Locating RFC [2]822 headers Jacob Palme
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers Graham Klyne
- Re: Locating RFC [2]822 headers Graham Klyne
- Re: Locating RFC [2]822 headers Jacob Palme
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers Charles Lindsey
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers Charles Lindsey
- Re: Locating RFC [2]822 headers Kai Henningsen
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers Charles Lindsey
- Re: Locating RFC [2]822 headers Charles Lindsey
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers D. J. Bernstein
- Re: Locating RFC [2]822 headers Graham Klyne
- Re: Locating RFC [2]822 headers Charles Lindsey
- Re: Locating RFC [2]822 headers ned+ietf-822
- Re: Locating RFC [2]822 headers Graham Klyne
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers Graham Klyne
- Re: Locating RFC [2]822 headers Lawrence Greenfield
- Re: Locating RFC [2]822 headers Dave Crocker
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers Dave Crocker
- Re: Locating RFC [2]822 headers ned+ietf-822
- Locating RFC [2]822 headers Graham Klyne
- Re: Loop control Craig_Everhart
- Re: Loop control Russ Allbery
- Re: Loop control Jacob Palme
- Re: Loop control James M Galvin
- Re: Loop control D. J. Bernstein
- Re: Loop control Philip Hazel
- Re: Loop control James M Galvin
- Re: Loop control Dave Crocker
- Re: Loop control Russ Allbery
- Loop control Jacob Palme
- Re: Locating RFC [2]822 headers Keith Moore
- Re: Locating RFC [2]822 headers D. J. Bernstein