RFC 4249: Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components

Implementation of generators and parsers of header fields requires certain information about those fields. Interoperability is most likely when all such…

Read RFC 4249 on the RFC Editor

Outgoing relationships (17 related RFCs)

Informative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Informative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Informative reference — RFC 822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Informative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Informative reference — RFC 3692: Assigning Experimental and Testing Numbers Considered Useful
Informative reference — RFC 1958: Architectural Principles of the Internet
Informative reference — RFC 3464: An Extensible Message Format for Delivery Status Notifications
Informative reference — RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
Informative reference — RFC 3798: Message Disposition Notification
Informative reference — RFC 987: Mapping between X.400 and RFC 822
Informative reference — RFC 2533: A Syntax for Describing Media Feature Sets
Informative reference — RFC 3282: Content Language Headers
Informative reference — RFC 2156: MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME
Informative reference — RFC 2369: The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields
Informative reference — RFC 2919: List-Id: A Structured Field and Namespace for the Identification of Mailing Lists
Informative reference — RFC 3297: Content Negotiation for Messaging Services based on Email
Informative reference — RFC 886: Proposed standard for message header munging