References from draft-ietf-pce-sid-algo
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 |
---|---|---|---|---|
draft-ietf-pce-pcep-yang |
A YANG Data Model for Path Computation Element Communications Protocol (PCEP)
References Referenced by |
normatively references | ||
draft-ietf-pce-segment-routing-ipv6 |
Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-pce-stateful-pce-optional |
Extension for Stateful PCE to allow Optional Processing of PCE Communication Protocol (PCEP) Objects
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5541 |
Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7471 |
OSPF Traffic Engineering (TE) Metric Extensions
References Referenced by |
Proposed Standard | normatively references | |
RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Best Current Practice | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8231 |
Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
References Referenced by |
Proposed Standard | normatively references | |
RFC 8233 |
Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8253 |
PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8281 |
Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model
References Referenced by |
Proposed Standard | normatively references | |
RFC 8402 |
Segment Routing Architecture
References Referenced by |
Proposed Standard | normatively references | |
RFC 8570 |
IS-IS Traffic Engineering (TE) Metric Extensions
References Referenced by |
Proposed Standard | normatively references | |
RFC 8664 |
Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 8665 |
OSPF Extensions for Segment Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 8667 |
IS-IS Extensions for Segment Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 9256 |
Segment Routing Policy Architecture
References Referenced by |
Proposed Standard | normatively references | |
RFC 9350 |
IGP Flexible Algorithm
References Referenced by |
Proposed Standard | normatively references |