References from draft-eastlake-cturi

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
RFC 1738 Uniform Resource Locators (URL)
Refs Ref'd by
Proposed Standard informatively references
RFC 2026 The Internet Standards Process -- Revision 3
Refs Ref'd by
Best Current Practice Possible Reference
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 2048 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
Refs Ref'd by
Best Current Practice normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2368 The mailto URL scheme
Refs Ref'd by
Proposed Standard informatively references
RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax
Refs Ref'd by
Draft Standard normatively references
RFC 2405 The ESP DES-CBC Cipher Algorithm With Explicit IV
Refs Ref'd by
Proposed Standard Possible Reference
RFC 2717 Registration Procedures for URL Scheme Names
Refs Ref'd by
Best Current Practice normatively references
RFC 2718 Guidelines for new URL Schemes
Refs Ref'd by
Informational normatively references
RFC 2822 Internet Message Format
Refs Ref'd by
Proposed Standard informatively references
RFC 3275 (Extensible Markup Language) XML-Signature Syntax and Processing
Refs Ref'd by
Draft Standard informatively references
RFC 822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Refs Ref'd by
Internet Standard Possible Reference