References from draft-ietf-alto-unified-props-new
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 122 |
Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
References Referenced by |
Best Current Practice | normatively references | |
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| draft-ietf-alto-cdni-request-routing-alto |
Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO
References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-alto-path-vector |
An ALTO Extension: Path Vector
References Referenced by |
Experimental | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3849 |
IPv6 Address Prefix Reserved for Documentation
References Referenced by |
Informational | informatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4291 |
IP Version 6 Addressing Architecture
References Referenced by |
Draft Standard | normatively references | |
| RFC 4632 |
Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5511 |
Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5737 |
IPv4 Address Blocks Reserved for Documentation
References Referenced by |
Informational | informatively references | |
| RFC 5952 |
A Recommendation for IPv6 Address Text Representation
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7285 |
Application-Layer Traffic Optimization (ALTO) Protocol
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7921 |
An Architecture for the Interface to the Routing System
References Referenced by |
Informational | informatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | normatively references | |
| RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8895 |
Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8896 |
Application-Layer Traffic Optimization (ALTO) Cost Calendar
References Referenced by |
Proposed Standard | informatively references | |
| STD 66 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| STD 90 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | normatively references |