References from draft-ietf-idr-bgpls-segment-routing-epe
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| draft-dawra-idr-bgpls-srv6-ext |
BGP Link State Extensions for SRv6 References Referenced by |
informatively references | ||
| draft-ietf-idr-bgp-ls-segment-routing-ext |
BGP Link-State extensions for Segment Routing References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-spring-segment-routing-central-epe |
Segment Routing Centralized BGP Egress Peer Engineering References Referenced by |
Informational | informatively references | |
| draft-ietf-spring-segment-routing-policy |
Segment Routing Policy Architecture References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
| RFC 5065 |
Autonomous System Confederations for BGP References Referenced by |
Draft Standard | normatively references | |
| RFC 6286 |
Autonomous-System-Wide Unique BGP Identifier for BGP-4 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 8402 |
Segment Routing Architecture References Referenced by |
Proposed Standard | normatively references |