References from draft-contreras-alto-service-edge
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 14 |
References Referenced by |
normatively references | ||
draft-ietf-alto-performance-metrics |
Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-teas-sf-aware-topo-model |
SF Aware TE Topology YANG Model
References Referenced by |
normatively references | ||
draft-llc-teas-dc-aware-topo-model |
DC aware TE topology model
References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 7285 |
Application-Layer Traffic Optimization (ALTO) Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 7752 |
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 9240 |
An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
References Referenced by |
Proposed Standard | normatively references | |
RFC 9275 |
An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector
References Referenced by |
Experimental | normatively references |