References from rfc5536

This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document	Title	Status	Type	Downref
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
BCP 90	Registration Procedures for Message Header Fields Refs Ref'd by	Best Current Practice	informatively references
RFC 1036	Standard for interchange of USENET messages Refs Ref'd by	Unknown	informatively references
RFC 2045	Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies Refs Ref'd by	Draft Standard	normatively references
RFC 2046	Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types Refs Ref'd by	Draft Standard	normatively references
RFC 2047	MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text Refs Ref'd by	Draft Standard	normatively references
RFC 2049	Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples Refs Ref'd by	Draft Standard	normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 2156	MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME Refs Ref'd by	Proposed Standard	informatively references
RFC 2183	Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field Refs Ref'd by	Proposed Standard	normatively references
RFC 2231	MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations Refs Ref'd by	Proposed Standard	normatively references
RFC 2616	Hypertext Transfer Protocol -- HTTP/1.1 Refs Ref'd by	Draft Standard	informatively references
RFC 2822	Internet Message Format Refs Ref'd by	Proposed Standard	informatively references
RFC 2980	Common NNTP Extensions Refs Ref'd by	Informational	informatively references
RFC 3156	MIME Security with OpenPGP Refs Ref'd by	Proposed Standard	informatively references
RFC 3282	Content Language Headers Refs Ref'd by	Draft Standard	normatively references
RFC 3696	Application Techniques for Checking and Transformation of Names Refs Ref'd by	Informational	informatively references
RFC 3851	Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification Refs Ref'd by	Proposed Standard	informatively references
RFC 3864	Registration Procedures for Message Header Fields Refs Ref'd by	Best Current Practice	informatively references
RFC 3977	Network News Transfer Protocol (NNTP) Refs Ref'd by	Proposed Standard	informatively references
RFC 3986	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references
RFC 5234	Augmented BNF for Syntax Specifications: ABNF Refs Ref'd by	Internet Standard	normatively references
RFC 5322	Internet Message Format Refs Ref'd by	Draft Standard	informatively references
RFC 5537	Netnews Architecture and Protocols Refs Ref'd by	Proposed Standard	normatively references
RFC 822	STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES Refs Ref'd by	Internet Standard	informatively references
RFC 850	Standard for interchange of USENET messages Refs Ref'd by	Unknown	informatively references
STD 1	Internet Official Protocol Standards Refs Ref'd by	Historic	Possible Reference	Possible Downref
STD 11	STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES Refs Ref'd by	Internet Standard	informatively references
STD 66	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references
STD 68	Augmented BNF for Syntax Specifications: ABNF Refs Ref'd by	Internet Standard	normatively references