Message-Id: <v03110701b0df8fa58da5@[130.237.150.138]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 12 Jan 1998 10:22:14 +0100
To: IETF working group on revision of mail standards <drums@cs.utk.edu>
From: Jacob Palme <jpalme@dsv.su.se>
Subject: draft-ietf-drums-MHRegistry-04.txt

A new version of the draft on a header registry has now been submitted
to IETF drafts. You can get it by FTP from
ftp://ftp.dsv.su.se/users/jpalme/draft-ietf-drums-MHRegistry-04.txt

Please do not send followup on this message only to the
http-wg@cuckoo.hpl.hp.com mailing list, since I do not subscribe
to that list. Send them to me personally, or send them to the
drums@cs.utk.edu mailing list, too.

Changes from version 03 of this draft

Also http header fields are now included in the registry, not as
before only e-mail and netnews header fields.

Added text that also fields from Internet drafts can be registered
on a temporary basis, such registration expires with the Internet
draft:

   3.1 Registration of headers from Internet drafts

   Headers in Internet drafts can be registered on a temporary
   basis, so that the header registry can be used to find also
   such headers. If the IETF draft expires, such headers must
   either be removed from the registry, or changed to reflect
   their new status (as an IETF standard or as a non-standard
   documented separately from IETF).

   Expiration month: (For a header field from an Internet draft,
   this must be the expiration date of the draft. After this
   time, the registration must either be removed or changed. The
   word "unlimited" can be used for fields without an expiration
   month.)

Changed paragraph about "X-" headers:

   Because of this, an IANA registry for http, e-mail and
   Netnews header field names is needed. This registry can
   contain header fields starting with "X-", even though such
   header fields cannot be specified in IETF standards. The
   registry can also contain header fields not starting with
   "X-", even though such fields are not part of IETF standards.
   There is no promise that such non-standard field names, not
   starting with "X-", will not be used in future standards, but
   normally future standards can be expected not to use field
   names from the header registry in ways which are incompatible
   with existing usage of such fields as specified in the
   registry.

Added text that the IESG can change any header registration.

   Minor changes to registered headers, which will not cause
   problems for those who have already implemented the header,
   can be done by the person or organisation who has change
   control for the header. This person or organisation can also
   add to the register advance notice about future changes under
   development. The IESG additionally has the right to modify an
   header field registration, even without permission from the
   change controller. This right for the IESG should of course
   be used with great caution.

The name of the mailing list has been changed from "mail-headers"
to "message-headers" to allow also http and netnews header fields.

------------------------------------------------------------------------
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/~jpalme