References from RFC 8795
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 |
References Referenced by |
normatively references | ||
BCP 206 |
References Referenced by |
normatively references | ||
BCP 215 |
References Referenced by |
informatively references | ||
BCP 87 |
References Referenced by |
informatively references | ||
draft-ietf-ccamp-otn-topo-yang |
A YANG Data Model for Optical Transport Network Topology
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-ccamp-wson-yang |
A YANG Data Model for Wavelength Switched Optical Networks (WSONs)
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-netconf-subscribed-notifications |
Subscription to YANG Notifications
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-netconf-yang-push |
Subscription to YANG Notifications for Datastore Updates
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-teas-te-topo-and-tunnel-modeling |
TE Topology and Tunnel Modeling for Transport Networks
References Referenced by |
informatively references | ||
draft-ietf-teas-yang-l3-te-topo |
YANG Data Model for Layer 3 TE Topologies
References Referenced by |
informatively references | ||
draft-ietf-teas-yang-te-types |
Common YANG Data Types for Traffic Engineering
References Referenced by |
Proposed Standard | normatively references | |
draft-liu-netmod-yang-schedule |
A YANG Data Model for Configuration Scheduling
References Referenced by |
informatively references | ||
RFC 1195 |
Use of OSI IS-IS for routing in TCP/IP and dual environments
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 2702 |
Requirements for Traffic Engineering Over MPLS
References Referenced by |
Informational | informatively references | |
RFC 3209 |
RSVP-TE: Extensions to RSVP for LSP Tunnels
References Referenced by |
Proposed Standard | informatively references | |
RFC 3272 |
Overview and Principles of Internet Traffic Engineering
References Referenced by |
Informational | informatively references | |
RFC 3471 |
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description
References Referenced by |
Proposed Standard | informatively references | |
RFC 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by |
Proposed Standard | informatively references | |
RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
RFC 3785 |
Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric
References Referenced by |
Best Current Practice | informatively references | |
RFC 3945 |
Generalized Multi-Protocol Label Switching (GMPLS) Architecture
References Referenced by |
Proposed Standard | normatively references | |
RFC 4201 |
Link Bundling in MPLS Traffic Engineering (TE)
References Referenced by |
Proposed Standard | informatively references | |
RFC 4202 |
Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by |
Proposed Standard | informatively references | |
RFC 4203 |
OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by |
Proposed Standard | informatively references | |
RFC 4206 |
Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
References Referenced by |
Proposed Standard | informatively references | |
RFC 4872 |
RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
References Referenced by |
Proposed Standard | informatively references | |
RFC 5152 |
A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
References Referenced by |
Proposed Standard | informatively references | |
RFC 5212 |
Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
References Referenced by |
Informational | informatively references | |
RFC 5305 |
IS-IS Extensions for Traffic Engineering
References Referenced by |
Proposed Standard | informatively references | |
RFC 5316 |
ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
References Referenced by |
Proposed Standard | informatively references | |
RFC 5329 |
Traffic Engineering Extensions to OSPF Version 3
References Referenced by |
Proposed Standard | informatively references | |
RFC 5392 |
OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
References Referenced by |
Proposed Standard | informatively references | |
RFC 6001 |
Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
References Referenced by |
Proposed Standard | informatively 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 7308 |
Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)
References Referenced by |
Proposed Standard | informatively references | |
RFC 7471 |
OSPF Traffic Engineering (TE) Metric Extensions
References Referenced by |
Proposed Standard | informatively references | |
RFC 7579 |
General Network Element Constraint Encoding for GMPLS-Controlled Networks
References Referenced by |
Proposed Standard | informatively references | |
RFC 7752 |
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by |
Proposed Standard | informatively references | |
RFC 7926 |
Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
References Referenced by |
Best Current Practice | normatively 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 8340 |
YANG Tree Diagrams
References Referenced by |
Best Current Practice | informatively 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 | normatively references | |
RFC 8345 |
A YANG Data Model for Network Topologies
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 | |
STD 91 |
References Referenced by |
normatively references |