Skip to main content

6. IANA Considerations

This document updates the registrations that appeared in RFC 4021, which references the definitions in RFC 2822. IANA has updated the Permanent Message Header Field Repository with the following header fields according to the procedures set out in RFC 3864.

Registered Header Fields​

Origination Fields​

Date

  • Header field name: Date
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.1)

From

  • Header field name: From
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.2)

Sender

  • Header field name: Sender
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.2)

Reply-To

  • Header field name: Reply-To
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.2)

Destination Fields​

To

  • Header field name: To
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.3)

Cc

  • Header field name: Cc
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.3)

Bcc

  • Header field name: Bcc
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.3)

Identification Fields​

Message-ID

  • Header field name: Message-ID
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.4)

In-Reply-To

  • Header field name: In-Reply-To
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.4)

References

  • Header field name: References
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.4)

Informational Fields​

Subject

  • Header field name: Subject
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.5)

Comments

  • Header field name: Comments
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.5)

Keywords

  • Header field name: Keywords
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.5)

Resent Fields​

Resent-Date, Resent-From, Resent-Sender, Resent-To, Resent-Cc, Resent-Bcc, Resent-Message-ID

  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.6)

Resent-Reply-To

  • Header field name: Resent-Reply-To
  • Applicable protocol: Mail
  • Status: obsolete
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 4.5.6)

Trace Fields​

Return-Path

  • Header field name: Return-Path
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.7)

Received

  • Header field name: Received
  • Applicable protocol: Mail
  • Status: standard
  • Author/Change controller: IETF
  • Specification document(s): This document (Section 3.6.7)
  • Related information: RFC 5321

Header Field Classification​

By Status​

StatusFieldsCount
standardAll except Resent-Reply-To23
obsoleteResent-Reply-To1

IANA Registration Process​

This specification follows the Permanent Message Header Field registration procedures defined in RFC 3864:

  1. Registration Request: Submit to IANA
  2. Review Process: IESG review
  3. Registration Approval: IANA approval and recording
  4. Public Access: Published on IANA website

Permanent Message Header Field Repository​

The IANA-maintained Permanent Message Header Field Repository contains:

  • Standardized header fields
  • Experimental header fields
  • Provisional header fields
  • Obsolete header fields

Access: https://www.iana.org/assignments/message-headers/

Summary​

RFC 5322 registers 23 standard header fields and 1 obsolete field with IANA, updating the previous RFC 2822 registrations. All registrations follow procedures defined in RFC 3864 and are maintained in IANA's Permanent Message Header Field Repository.

Next: 7. References

Previous: 5. Security Considerations

Last updated on