References from draft-sreekantiah-idr-segment-routing-te
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-filsfils-rtgwg-segment-routing |
Segment Routing Architecture
References Referenced by |
informatively references | ||
| draft-ietf-idr-flowspec-redirect-ip |
BGP Flow-Spec Redirect to IP Action
References Referenced by |
Possible Reference | ||
| draft-sivabalan-pce-segment-routing |
PCEP Extensions for Segment Routing
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 2858 |
Multiprotocol Extensions for BGP-4
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3209 |
RSVP-TE: Extensions to RSVP for LSP Tunnels
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 4271 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | normatively references | |
| RFC 4760 |
Multiprotocol Extensions for BGP-4
References Referenced by |
Draft Standard | Possible Reference | |
| RFC 5462 |
Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 5512 |
The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5575 |
Dissemination of Flow Specification Rules
References Referenced by |
Proposed Standard | Possible Reference |