References from rfc8776

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
BCP 14	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
BCP 87	Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric References Referenced by	Best Current Practice	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 3477	Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) 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 4090	Fast Reroute Extensions to RSVP-TE for LSP Tunnels References Referenced by	Proposed Standard	informatively references
RFC 4124	Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering References Referenced by	Proposed Standard	informatively references
RFC 4125	Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering References Referenced by	Experimental	informatively references
RFC 4126	Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons References Referenced by	Experimental	informatively references
RFC 4127	Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering References Referenced by	Experimental	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 4328	Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control References Referenced by	Proposed Standard	informatively references
RFC 4427	Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS) References Referenced by	Informational	informatively references
RFC 4561	Definition of a Record Route Object (RRO) Node-Id Sub-Object References Referenced by	Proposed Standard	informatively references
RFC 4657	Path Computation Element (PCE) Communication Protocol Generic Requirements References Referenced by	Informational	informatively references
RFC 4736	Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP) References Referenced by	Informational	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 4873	GMPLS Segment Recovery References Referenced by	Proposed Standard	informatively references
RFC 4875	Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs) References Referenced by	Proposed Standard	informatively references
RFC 4920	Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE References Referenced by	Proposed Standard	informatively references
RFC 5003	Attachment Individual Identifier (AII) Types for Aggregation References Referenced by	Proposed Standard	informatively references
RFC 5150	Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE) References Referenced by	Proposed Standard	informatively references
RFC 5151	Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions References Referenced by	Proposed Standard	informatively references
RFC 5305	IS-IS Extensions for Traffic Engineering References Referenced by	Proposed Standard	informatively references
RFC 5307	IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) References Referenced by	Proposed Standard	informatively references
RFC 5420	Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE) References Referenced by	Proposed Standard	informatively references
RFC 5541	Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) References Referenced by	Proposed Standard	informatively references
RFC 5712	MPLS Traffic Engineering Soft Preemption References Referenced by	Proposed Standard	informatively references
RFC 5817	Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks References Referenced by	Informational	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 6004	Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching References Referenced by	Proposed Standard	informatively references
RFC 6020	YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF) References Referenced by	Proposed Standard	normatively references
RFC 6119	IPv6 Traffic Engineering in IS-IS References Referenced by	Proposed Standard	informatively references
RFC 6205	Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers 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 6370	MPLS Transport Profile (MPLS-TP) Identifiers References Referenced by	Proposed Standard	informatively references
RFC 6378	MPLS Transport Profile (MPLS-TP) Linear Protection References Referenced by	Proposed Standard	informatively references
RFC 6511	Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths References Referenced by	Proposed Standard	informatively references
RFC 6780	RSVP ASSOCIATION Object Extensions References Referenced by	Proposed Standard	informatively references
RFC 6790	The Use of Entropy Labels in MPLS Forwarding References Referenced by	Proposed Standard	informatively references
RFC 6827	Automatically Switched Optical Network (ASON) Routing for OSPFv2 Protocols References Referenced by	Proposed Standard	informatively references
RFC 6991	Common YANG Data Types References Referenced by	Proposed Standard	normatively references
RFC 7139	GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport Networks References Referenced by	Proposed Standard	informatively references
RFC 7260	GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration References Referenced by	Proposed Standard	informatively 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 7551	RSVP-TE Extensions for Associated Bidirectional Label Switched Paths (LSPs) References Referenced by	Proposed Standard	informatively references
RFC 7570	Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO) References Referenced by	Proposed Standard	informatively references
RFC 7571	GMPLS RSVP-TE Extensions for Lock Instruct and Loopback 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 7823	Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric Extensions References Referenced by	Informational	informatively references
RFC 7950	The YANG 1.1 Data Modeling Language References Referenced by	Proposed Standard	normatively references
RFC 7951	JSON Encoding of Data Modeled with YANG References Referenced by	Proposed Standard	normatively references
RFC 8001	RSVP-TE Extensions for Collecting Shared Risk Link Group (SRLG) Information References Referenced by	Proposed Standard	informatively references
RFC 8040	RESTCONF Protocol References Referenced by	Proposed Standard	normatively references
RFC 8149	RSVP Extensions for Reoptimization of Loosely Routed Point-to-Multipoint Traffic Engineering Label Switched Paths (LSPs) References Referenced by	Proposed Standard	informatively references
RFC 8169	Residence Time Measurement in MPLS Networks References Referenced by	Proposed Standard	informatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by	Best Current Practice	normatively references
RFC 8294	Common YANG Data Types for the Routing Area References Referenced by	Proposed Standard	normatively references
RFC 8341	Network Configuration Access Control Model References Referenced by	Internet 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
RFC 8570	IS-IS Traffic Engineering (TE) Metric Extensions References Referenced by	Proposed Standard	informatively references
STD 91	Network Configuration Access Control Model References Referenced by	Internet Standard	normatively references