Re: Locating RFC [2]822 headers

[Dave Crocker <[e-mail]>]

Graham,

Thanks for raising this.  I had a task something like this on my work queue 
from, perhaps, a year ago.  sigh.

On the other hand, I had only thought of documenting a procedure; you have 
suggested a larger task that is, really, a header cleanup project.

However, casting the approach as an extension to DRUMS work seems like the 
right thing to do.  That would justify having a document that repeats the 
definitions found in earlier documents, since DRUMS is about coalescing, as 
well as clarifying and fixing.  It does mean that we would be required to 
go over, and modify, RFC2076 carefully and achieve rough consensus on it.

The standards status of the result should be the same the same track as 2822.

d/


At 04:29 AM 9/19/2001, Graham Klyne wrote:
>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.

----------
Dave Crocker  <mailto:[e-mail]>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel [phone];  fax [phone]