Mail and Netnews Header Registration Procedure
draft-ietf-drums-MHRegistry-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Jacob Palme | ||
| Last updated | 1998-01-13 (Latest revision 1997-11-24) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Various IETF standards and http, e-mail and netnews software products use various http, e-mail and netnews header fields. This document specifies a procedure for the registration of http, e-mail and netnews header field names, to reduce the risk that two different products use the same header field name in different ways (homonyms) or that several different header field names are used with identical meaning (synonyms).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)