References from draft-ietf-pce-stateful-pce-p2mp

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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
BCP 195 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Refs Ref'd by
Best Current Practice normatively references
BCP 26 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice informatively references
draft-ietf-pce-pcep-yang A YANG Data Model for Path Computation Element Communications Protocol (PCEP)
Refs Ref'd by
informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels
Refs Ref'd by
Proposed Standard normatively references
RFC 4655 A Path Computation Element (PCE)-Based Architecture
Refs Ref'd by
Informational informatively references
RFC 4875 Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)
Refs Ref'd by
Proposed Standard normatively references
RFC 5088 OSPF Protocol Extensions for Path Computation Element (PCE) Discovery
Refs Ref'd by
Proposed Standard normatively references
RFC 5089 IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery
Refs Ref'd by
Proposed Standard normatively references
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)
Refs Ref'd by
Proposed Standard normatively references
RFC 5511 Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications
Refs Ref'd by
Proposed Standard normatively references
RFC 5671 Applicability of the Path Computation Element (PCE) to Point-to-Multipoint (P2MP) MPLS and GMPLS Traffic Engineering (TE)
Refs Ref'd by
Informational informatively references
RFC 7525 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Refs Ref'd by
Best Current Practice normatively references
RFC 8051 Applicability of a Stateful Path Computation Element (PCE)
Refs Ref'd by
Informational informatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references
RFC 8231 Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
Refs Ref'd by
Proposed Standard normatively references
RFC 8232 Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE
Refs Ref'd by
Proposed Standard normatively references
RFC 8253 PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
Refs Ref'd by
Proposed Standard normatively references
RFC 8281 Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model
Refs Ref'd by
Proposed Standard normatively references
RFC 8306 Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
Refs Ref'd by
Proposed Standard normatively references