References from draft-chen-pce-pcep-ifit
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 | |
BCP 195 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) 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-6man-ipv6-alt-mark |
IPv6 Application of the Alternate Marking Method References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-ippm-ioam-data |
Data Fields for In-situ OAM References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-ippm-ioam-direct-export |
In-situ OAM Direct Exporting References Referenced by |
normatively references | ||
draft-ietf-ippm-ioam-flags |
In-situ OAM Flags References Referenced by |
normatively references | ||
draft-ietf-ippm-ioam-ipv6-options |
In-situ OAM IPv6 Options References Referenced by |
normatively references | ||
draft-ietf-pce-segment-routing-ipv6 |
PCEP Extensions for Segment Routing leveraging the IPv6 data plane References Referenced by |
informatively references | ||
draft-ietf-pce-segment-routing-policy-cp |
PCEP extension to support Segment Routing Policy Candidate Paths References Referenced by |
informatively references | ||
draft-ietf-spring-segment-routing-policy |
Segment Routing Policy Architecture References Referenced by |
informatively references | ||
draft-qin-idr-sr-policy-ifit |
BGP SR Policy Extensions to Enable IFIT 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 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP) References Referenced by |
Proposed Standard | normatively references | |
RFC 7525 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) References Referenced by |
Best Current Practice | normatively references | |
RFC 7799 |
Active and Passive Metrics and Methods (with Hybrid Types In-Between) References Referenced by |
Informational | normatively 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 8231 |
Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE 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 8321 |
Alternate-Marking Method for Passive and Hybrid Performance Monitoring References Referenced by |
Experimental | normatively references | |
RFC 8664 |
Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing References Referenced by |
Proposed Standard | normatively references |