References from draft-gandhi-lsr-ber
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 |
|---|---|---|---|---|
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 4203 | OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) References Referenced by | Proposed Standard | informatively references | |
| RFC 5120 | M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs) References Referenced by | Proposed Standard | informatively references | |
| RFC 5305 | IS-IS Extensions for Traffic Engineering References Referenced by | Proposed Standard | informatively references | |
| RFC 7471 | OSPF Traffic Engineering (TE) Metric Extensions 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 8570 | IS-IS Traffic Engineering (TE) Metric Extensions References Referenced by | Proposed Standard | normatively references | |
| RFC 8571 | BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions References Referenced by | Proposed Standard | normatively references | |
| RFC 9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering References Referenced by | Proposed Standard | informatively references | |
| RFC 9552 | Distribution of Link-State and Traffic Engineering Information Using BGP References Referenced by | Proposed Standard | informatively references |