Skip to main content

References to RFC 4736

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 8149 RSVP Extensions for Reoptimization of Loosely Routed Point-to-Multipoint Traffic Engineering Label Switched Paths (LSPs)
References Referenced by
Proposed Standard normatively references Downref
draft-ietf-teas-rfc8776-update Common YANG Data Types for Traffic Engineering
References Referenced by
informatively references
RFC 4859 Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Session Attribute Object
References Referenced by
Informational informatively references
RFC 5146 Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks
References Referenced by
Informational 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 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 5710 PathErr Message Triggered MPLS and GMPLS LSP Reroutes
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 8776 Common YANG Data Types for Traffic Engineering
References Referenced by
Proposed Standard informatively references