Skip to main content

References from draft-li-pce-pcep-flowspec

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
References Referenced by
normatively references
BCP 26
References Referenced by
informatively references
draft-dhodylee-pce-pcep-ls PCEP extensions for Distribution of Link-State and TE Information
References Referenced by
normatively references
draft-ietf-idr-flow-spec-v6 Dissemination of Flow Specification Rules for IPv6
References Referenced by
Proposed Standard normatively references
draft-ietf-pce-segment-routing Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
References Referenced by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs)
References Referenced by
Proposed Standard informatively references
RFC 4655 A Path Computation Element (PCE)-Based Architecture
References Referenced by
Informational informatively references
RFC 5088 OSPF Protocol Extensions for Path Computation Element (PCE) Discovery
References Referenced by
Proposed Standard informatively references
RFC 5089 IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery
References Referenced by
Proposed Standard informatively references
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by
Proposed Standard normatively references
RFC 5511 Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications
References Referenced by
Proposed Standard normatively references
RFC 5575 Dissemination of Flow Specification Rules
References Referenced by
Proposed Standard normatively references
RFC 6952 Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
References Referenced by
Informational informatively references
RFC 7399 Unanswered Questions in the Path Computation Element Architecture
References Referenced by
Informational informatively references
RFC 7761 Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
References Referenced by
Internet Standard informatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
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 informatively references
RFC 8232 Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE
References Referenced by
Proposed Standard informatively 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 informatively references
RFC 8283 An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control
References Referenced by
Informational informatively references
STD 83
References Referenced by
informatively references