References from draft-ietf-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.
| 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 205 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Best Current Practice | informatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | informatively references | |
| draft-gont-numeric-ids-sec-considerations |
Security Considerations for Transient Numeric Identifiers Employed in Network Protocols References Referenced by |
Best Current Practice | informatively references | |
| draft-ietf-idr-flow-spec-v6 |
Dissemination of Flow Specification Rules for IPv6 References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-idr-flowspec-l2vpn |
BGP Dissemination of L2 Flow Specification Rules References Referenced by |
normatively references | Possible Downref | |
| draft-ietf-idr-rfc5575bis |
Dissemination of Flow Specification Rules References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-pce-pcep-yang |
A YANG Data Model for Path Computation Element Communications Protocol (PCEP) References Referenced by |
informatively references | ||
| draft-ietf-teas-yang-path-computation |
YANG Data Model for requesting Path Computation 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 4364 |
BGP/MPLS IP Virtual Private Networks (VPNs) References Referenced by |
Proposed Standard | normatively references | |
| RFC 4655 |
A Path Computation Element (PCE)-Based Architecture References Referenced by |
Informational | informatively references | |
| RFC 4760 |
Multiprotocol Extensions for BGP-4 References Referenced by |
Draft Standard | normatively 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 5886 |
A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture References Referenced by |
Proposed Standard | informatively references | |
| RFC 6123 |
Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts References Referenced by |
Historic | informatively 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 7942 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Best Current Practice | 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 | normatively references | |
| RFC 8232 |
Optimizations of Label Switched Path State Synchronization Procedures for a 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 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 | |
| RFC 8664 |
Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing References Referenced by |
Proposed Standard | informatively references |