References from draft-nottingham-rfc7320bis

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
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 1034	Domain names - concepts and facilities Refs Ref'd by	Internet Standard	informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 3986	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references
RFC 4395	Guidelines and Registration Procedures for New URI Schemes Refs Ref'd by	Best Current Practice	informatively references
RFC 6570	URI Template Refs Ref'd by	Proposed Standard	informatively references
RFC 6901	JavaScript Object Notation (JSON) Pointer Refs Ref'd by	Proposed Standard	informatively references
RFC 6943	Issues in Identifier Comparison for Security Purposes Refs Ref'd by	Informational	informatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by	Best Current Practice	normatively references
RFC 8288	Web Linking Refs Ref'd by	Proposed Standard	informatively references
RFC 8615	Well-Known Uniform Resource Identifiers (URIs) Refs Ref'd by	Proposed Standard	informatively references
STD 13	Domain names - implementation and specification Refs Ref'd by	Internet Standard	informatively references
STD 66	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references