Network Working Group B. Lilly Internet-Draft April 2005 Intended status: Informational Expires: October 23, 2005 Registration Templates for Legacy Message Header Field Names draft-lilly-legacy-fields-00 Status of this Memo By submitting this Internet-Draft, the author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This memo documents several Internet Message Format message header field names and provides registration templates so that the names can be registered in the permanent message header field name registry. Lilly Expires October 23, 2005 [Page 1] Internet-Draft Legacy Message Header Field Names April 2005 Table of Contents 1. Introduction.................................................... 3 2. Header Field Name Registration Templates........................ 3 2.1. Bilateral-Info............................................. 3 2.2. Delivery-Report-Content-Billing-Information................ 3 2.3. Delivery-Report-Content-Intermediate-Trace................. 4 2.4. Delivery-Report-Content-Original........................... 4 2.5. Delivery-Report-Content-Reported-Recipient-Info............ 4 2.6. Delivery-Report-Content-UA-Content-ID...................... 5 2.7. Fcc........................................................ 5 2.8. Mail-From.................................................. 5 2.9. Original-Recipient......................................... 6 2.10. P1-Content-Type........................................... 6 2.11. P1-Message-ID............................................. 6 2.12. P1-Recipient.............................................. 7 2.13. Received-Content-MIC...................................... 7 2.14. UA-Content-ID............................................. 7 3. Acknowledgments................................................. 7 4. Security Considerations......................................... 7 5. Internationalization Considerations............................. 8 6. IANA Considerations............................................. 8 Appendix A. Change History......................................... 8 Appendix B. Disclaimer............................................. 8 Normative Reference................................................ 8 Informative References............................................. 8 Author's Address................................................... 9 Lilly Expires October 23, 2005 [Page 2] Internet-Draft Legacy Message Header Field Names April 2005 1. Introduction [I1.RFC4021]provides registration templates for several Internet Message Format [I2.RFC822], [I3.RFC2822] header field names. However, there are more than a dozen message header field names which have been defined in published RFCs but which are not included in [I1.RFC4021]. This memo provides registration templates for field names defined in early RFCs for use in Internet Message Format documents so as to preclude contradictory redefinition of those field names. Messages may be kept in archives for long periods of time, and contradictory use of defined field names would be highly undesirable. The registration templates are provided in accordance with [N1.BCP90]. 2. Header Field Name Registration Templates 2.1. Bilateral-Info Header field name: Bilateral-Info Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: obsoleted by RFC 1327 [I5.RFC1327] 2.2. Delivery-Report-Content-Billing-Information Header field name: Delivery-Report-Content-Billing-Information Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Obsoleted by RFC 1327 [I5.RFC1327] Lilly Expires October 23, 2005 [Page 3] Internet-Draft Legacy Message Header Field Names April 2005 2.3. Delivery-Report-Content-Intermediate-Trace Header field name: Delivery-Report-Content-Intermediate-Trace Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Most convoluted syntax ever. Obsoleted by RFC 1327 [I5.RFC1327]. 2.4. Delivery-Report-Content-Original Header field name: Delivery-Report-Content-Original Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Obsoleted by RFC 1327 [I5.RFC1327] 2.5. Delivery-Report-Content-Reported-Recipient-Info Header field name: Delivery-Report-Content-Reported-Recipient-Info Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Obsoleted by RFC 1327 [I5.RFC1327]. Longest field name ever. Lilly Expires October 23, 2005 [Page 4] Internet-Draft Legacy Message Header Field Names April 2005 2.6. Delivery-Report-Content-UA-Content-ID Header field name: Delivery-Report-Content-UA-Content-ID Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Obsoleted by RFC 1327 [I5.RFC1327] 2.7. Fcc Header field name: Fcc Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 724 [I6.RFC724] Related information: Obsoleted by RFC 733 [I7.RFC733] 2.8. Mail-From Header field name: Mail-From Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsoleted Author/Change controller: IESG Specification document(s): RFC 788 [I8.RFC788] Related information: Specified in original SMTP specification for mail [I8.RFC788]. Functionality subsumed by Received field [I1.RFC4021] as specified in [I9.RFC821]. Obsoleted by RFC 821 [I9.RFC821]. Lilly Expires October 23, 2005 [Page 5] Internet-Draft Legacy Message Header Field Names April 2005 2.9. Original-Recipient Header field name: Original-Recipient Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: standards track Author/Change controller: IESG Specification document(s): RFC 2156 [I10.RFC2156], RFC 3798 [I11.RFC3798] Related information: Also used in Delivery Status Notification (DSN) per-recipient fields [I12.RFC3464]. 2.10. P1-Content-Type Header field name: P1-Content-Type Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsolete Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Obsoleted by RFC 1327 [I5.RFC1327] 2.11. P1-Message-ID Header field name: P1-Message-ID Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsolete Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Obsoleted by RFC 1327 [I5.RFC1327] Lilly Expires October 23, 2005 [Page 6] Internet-Draft Legacy Message Header Field Names April 2005 2.12. P1-Recipient Header field name: P1-Recipient Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsolete Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] as amended by RFC 1026 [I13.RFC1026] Related information: Obsoleted by RFC 1327 [I5.RFC1327] 2.13. Received-Content-MIC Header field name: Received-Content-MIC Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: standards track Author/Change controller: IESG Specification document(s): RFC 3335 [I14.RFC3335] Related information: 2.14. UA-Content-ID Header field name: UA-Content-ID Applicable protocol: Internet Message Format [I2.RFC822], [I3.RFC2822] Status: obsolete Author/Change controller: IESG Specification document(s): RFC 987 [I4.RFC987] Related information: Obsoleted by RFC 1327 [I5.RFC1327] 3. Acknowledgments Matt Groening for "Comic Book Guy". 4. Security Considerations No security considerations are addressed by this memo. Lilly Expires October 23, 2005 [Page 7] Internet-Draft Legacy Message Header Field Names April 2005 5. Internationalization Considerations This memo raises no new internationalization considerations. 6. IANA Considerations IANA shall register the header field names in section 2 of this memo in the permanent message header field registry. Appendix A. Change History [[This change history will not be part of a published RFC]] -00 o initial version Appendix B. Disclaimer The author is male; any reference to "or she" or "/SHE" in boilerplate of this document is irrelevant. Normative Reference [N1.BCP90] Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864, September 2004. Informative References [I1.RFC4021] Klyne, G. and J. Palme, "Registration of Mail and MIME Header Fields", RFC 4021, March 2005. [I2.RFC822] Crocker, D., "Standard for the format of ARPA Internet text messages", STD 11, RFC 822, August 1982. [I3.RFC2822] Resnick, P., "Internet Message Format", RFC 2822, April 2001. [I4.RFC987] Kille, S., "Mapping between X.400 and RFC 822", RFC 987, June 1986. [I5.RFC1327] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", RFC 1327, May 1992. [I6.RFC724] Crocker, D., Pogran, K., Vittal, J., and D. Henderson, "Proposed official standard for the format of ARPA Network messages", RFC 724, May 1977. [I7.RFC733] Crocker, D., Vittal, J., Pogran, K., and D. Henderson, "Standard for the format of ARPA network text messages", RFC 733, November 1977. Lilly Expires October 23, 2005 [Page 8] Internet-Draft Legacy Message Header Field Names April 2005 [I8.RFC788] Postel, J., "Simple Mail Transfer Protocol", RFC 788, November 1981. [I9.RFC821] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821, August 1982. [I10.RFC2156] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME", RFC 2156, January 1998. [I11.RFC3798] Hansen, T. and G. Vaudreuil, "Message Disposition Notification", RFC 3798, May 2004. [I12.RFC3464] Moore, K. and G. Vaudreuil, "An Extensible Message Format for Delivery Status Notifications", RFC 3464, January 2003. [I13.RFC1026] Kille, S., "Addendum to RFC 987: (Mapping between X.400 and RFC-822)", RFC 1026, September 1987. [I14.RFC3335] Harding, T., Drummond, R., and C. Shih, "MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet", RFC 3335, September 2002. Author's Address Bruce Lilly Email: blilly@erols.com Full Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information Lilly Expires October 23, 2005 [Page 9] Internet-Draft Legacy Message Header Field Names April 2005 on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Lilly Expires October 23, 2005 [Page 10]