References from draft-ietf-teas-yang-te-topo

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 206 Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
Refs Ref'd by
Best Current Practice normatively references
BCP 215 YANG Tree Diagrams
Refs Ref'd by
Best Current Practice informatively references
BCP 87 Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric
Refs Ref'd by
Best Current Practice informatively references
draft-ietf-ccamp-otn-topo-yang A YANG Data Model for Optical Transport Network Topology
Refs Ref'd by
informatively references
draft-ietf-ccamp-wson-yang A YANG Data Model for WSON (Wavelength Switched Optical Networks)
Refs Ref'd by
Proposed Standard informatively references
draft-ietf-netconf-subscribed-notifications Subscription to YANG Event Notifications
Refs Ref'd by
Proposed Standard informatively references
draft-ietf-netconf-yang-push Subscription to YANG Datastores
Refs Ref'd by
Proposed Standard informatively references
draft-ietf-teas-te-topo-and-tunnel-modeling TE Topology and Tunnel Modeling for Transport Networks
Refs Ref'd by
informatively references
draft-ietf-teas-yang-l3-te-topo YANG Data Model for Layer 3 TE Topologies
Refs Ref'd by
informatively references
draft-ietf-teas-yang-te-types Traffic Engineering Common YANG Types
Refs Ref'd by
Proposed Standard normatively references
draft-liu-netmod-yang-schedule A YANG Data Model for Configuration Scheduling
Refs Ref'd by
informatively references
RFC 1195 Use of OSI IS-IS for routing in TCP/IP and dual environments
Refs Ref'd by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2702 Requirements for Traffic Engineering Over MPLS
Refs Ref'd by
Informational informatively references
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels
Refs Ref'd by
Proposed Standard informatively references
RFC 3272 Overview and Principles of Internet Traffic Engineering
Refs Ref'd by
Informational informatively references
RFC 3471 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description
Refs Ref'd by
Proposed Standard informatively references
RFC 3630 Traffic Engineering (TE) Extensions to OSPF Version 2
Refs Ref'd by
Proposed Standard informatively references
RFC 3688 The IETF XML Registry
Refs Ref'd by
Best Current Practice normatively references
RFC 3785 Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric
Refs Ref'd by
Best Current Practice informatively references
RFC 3945 Generalized Multi-Protocol Label Switching (GMPLS) Architecture
Refs Ref'd by
Proposed Standard normatively references
RFC 4201 Link Bundling in MPLS Traffic Engineering (TE)
Refs Ref'd by
Proposed Standard informatively references
RFC 4202 Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Refs Ref'd by
Proposed Standard informatively references
RFC 4203 OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Refs Ref'd by
Proposed Standard informatively references
RFC 4206 Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
Refs Ref'd by
Proposed Standard informatively references
RFC 4872 RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
Refs Ref'd by
Proposed Standard informatively references
RFC 5152 A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
Refs Ref'd by
Proposed Standard informatively references
RFC 5212 Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
Refs Ref'd by
Informational informatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
Refs Ref'd by
Proposed Standard normatively references
RFC 5305 IS-IS Extensions for Traffic Engineering
Refs Ref'd by
Proposed Standard informatively references
RFC 5316 ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Refs Ref'd by
Proposed Standard informatively references
RFC 5329 Traffic Engineering Extensions to OSPF Version 3
Refs Ref'd by
Proposed Standard informatively references
RFC 5392 OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Refs Ref'd by
Proposed Standard informatively references
RFC 6001 Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
Refs Ref'd by
Proposed Standard informatively references
RFC 6241 Network Configuration Protocol (NETCONF)
Refs Ref'd by
Proposed Standard normatively references
RFC 6242 Using the NETCONF Protocol over Secure Shell (SSH)
Refs Ref'd by
Proposed Standard normatively references
RFC 6536 Network Configuration Protocol (NETCONF) Access Control Model
Refs Ref'd by
Proposed Standard normatively references
RFC 6991 Common YANG Data Types
Refs Ref'd by
Proposed Standard normatively references
RFC 7308 Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)
Refs Ref'd by
Proposed Standard informatively references
RFC 7471 OSPF Traffic Engineering (TE) Metric Extensions
Refs Ref'd by
Proposed Standard informatively references
RFC 7579 General Network Element Constraint Encoding for GMPLS-Controlled Networks
Refs Ref'd by
Proposed Standard informatively references
RFC 7752 North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Refs Ref'd by
Proposed Standard informatively references
RFC 7926 Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
Refs Ref'd by
Best Current Practice normatively references
RFC 7950 The YANG 1.1 Data Modeling Language
Refs Ref'd by
Proposed Standard normatively references
RFC 8040 RESTCONF Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references
RFC 8340 YANG Tree Diagrams
Refs Ref'd by
Best Current Practice informatively references
RFC 8342 Network Management Datastore Architecture (NMDA)
Refs Ref'd by
Proposed Standard normatively references
RFC 8345 A YANG Data Model for Network Topologies
Refs Ref'd by
Proposed Standard normatively references