References from RFC 6338

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	References Referenced by		normatively references
BCP 66	References Referenced by		normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	Possible Reference
RFC 2141	URN Syntax References Referenced by	Proposed Standard	informatively references
RFC 2798	Definition of the inetOrgPerson LDAP Object Class References Referenced by	Informational	informatively references
RFC 2818	HTTP Over TLS References Referenced by	Informational	normatively references
RFC 3120	A URN Namespace for XML.org References Referenced by	Informational	informatively references
RFC 3121	A URN Namespace for OASIS References Referenced by	Informational	informatively references
RFC 3406	Uniform Resource Names (URN) Namespace Definition Mechanisms References Referenced by	Best Current Practice	Possible Reference
RFC 3613	Definition of a Uniform Resource Name (URN) Namespace for the Middleware Architecture Committee for Education (MACE) References Referenced by	Informational	informatively references
RFC 4519	Lightweight Directory Access Protocol (LDAP): Schema for User Applications References Referenced by	Proposed Standard	informatively references
RFC 5234	Augmented BNF for Syntax Specifications: ABNF References Referenced by	Internet Standard	Possible Reference
RFC 5246	The Transport Layer Security (TLS) Protocol Version 1.2 References Referenced by	Proposed Standard	normatively references
RFC 5741	RFC Streams, Headers, and Boilerplates References Referenced by	Informational	Possible Reference
STD 68	References Referenced by		normatively references