Skip to main content

References from draft-ietf-pce-pcep-yang

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
draft-dhody-pce-pceps-tls13 Updates for PCEPS
References Referenced by
informatively references
draft-ietf-netconf-tls-client-server YANG Groupings for TLS Clients and TLS Servers
References Referenced by
Proposed Standard normatively references
draft-ietf-teas-yang-te A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces
References Referenced by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice normatively 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 normatively references
RFC 5089 IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery
References Referenced by
Proposed Standard normatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by
Proposed Standard informatively references
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by
Proposed Standard normatively references
RFC 5520 Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism
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 5557 Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization
References Referenced by
Proposed Standard normatively references
RFC 5925 The TCP Authentication Option
References Referenced by
Proposed Standard normatively references
RFC 6020 YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
References Referenced by
Proposed Standard normatively references
RFC 6241 Network Configuration Protocol (NETCONF)
References Referenced by
Proposed Standard normatively references
RFC 6242 Using the NETCONF Protocol over Secure Shell (SSH)
References Referenced by
Proposed Standard normatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7420 Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module
References Referenced by
Proposed Standard informatively references
RFC 7942 Improving Awareness of Running Code: The Implementation Status Section
References Referenced by
Best Current Practice informatively references
RFC 7950 The YANG 1.1 Data Modeling Language
References Referenced by
Proposed Standard normatively references
RFC 8040 RESTCONF Protocol
References Referenced by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8177 YANG Data Model for Key Chains
References Referenced by
Proposed Standard 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 8282 Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering
References Referenced 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
References Referenced by
Proposed Standard normatively references
RFC 8340 YANG Tree Diagrams
References Referenced by
Best Current Practice normatively references
RFC 8341 Network Configuration Access Control Model
References Referenced by
Internet Standard normatively references
RFC 8342 Network Management Datastore Architecture (NMDA)
References Referenced by
Proposed Standard informatively references
RFC 8408 Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages
References Referenced by
Proposed Standard normatively references
RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard normatively references
RFC 8623 Stateful Path Computation Element (PCE) Protocol Extensions for Usage with Point-to-Multipoint TE Label Switched Paths (LSPs)
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 8685 Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture
References Referenced by
Proposed Standard normatively references
RFC 8697 Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)
References Referenced by
Proposed Standard normatively references
RFC 8745 Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
References Referenced by
Proposed Standard normatively references
RFC 8751 Hierarchical Stateful Path Computation Element (PCE)
References Referenced by
Informational informatively references
RFC 8776 Common YANG Data Types for Traffic Engineering
References Referenced by
Proposed Standard normatively references
RFC 8779 Path Computation Element Communication Protocol (PCEP) Extensions for GMPLS
References Referenced by
Proposed Standard normatively references
RFC 8800 Path Computation Element Communication Protocol (PCEP) Extension for Label Switched Path (LSP) Diversity Constraint Signaling
References Referenced by
Proposed Standard normatively references
RFC 9005 Path Computation Element Communication Protocol (PCEP) Extension for Associating Policies and Label Switched Paths (LSPs)
References Referenced by
Proposed Standard normatively references
RFC 9129 YANG Data Model for the OSPF Protocol
References Referenced by
Proposed Standard normatively references
RFC 9130 YANG Data Model for the IS-IS Protocol
References Referenced by
Proposed Standard normatively references
RFC 9168 Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification
References Referenced by
Proposed Standard normatively references
RFC 9353 IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)
References Referenced by
Proposed Standard normatively references
RFC 9358 Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths and Virtual Networks
References Referenced by
Proposed Standard normatively references