References from rfc8454
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| draft-ietf-teas-actn-framework |
Framework for Abstraction and Control of TE Networks (ACTN) Refs Ref'd by |
Informational | normatively references | |
| draft-ietf-teas-yang-path-computation |
Yang model for requesting Path Computation Refs Ref'd by |
informatively references | ||
| draft-ietf-teas-yang-te-topo |
YANG Data Model for Traffic Engineering (TE) Topologies Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 3209 |
RSVP-TE: Extensions to RSVP for LSP Tunnels 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 4427 |
Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS) Refs Ref'd by |
Informational | informatively references | |
| RFC 5541 |
Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) 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 7926 |
Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks Refs Ref'd by |
Best Current Practice | informatively references |