References from RFC 4126
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 26 | References Referenced by | normatively references | ||
| BCP 78 | References Referenced by | informatively references | ||
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 3209 | RSVP-TE: Extensions to RSVP for LSP Tunnels References Referenced by | Proposed Standard | informatively references | |
| RFC 3564 | Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering References Referenced by | Informational | normatively references | |
| RFC 3630 | Traffic Engineering (TE) Extensions to OSPF Version 2 References Referenced by | Proposed Standard | informatively references | |
| RFC 4124 | Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering References Referenced by | Proposed Standard | normatively references | |
| RFC 4125 | Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering 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 4128 | Bandwidth Constraints Models for Differentiated Services (Diffserv)-aware MPLS Traffic Engineering: Performance Evaluation References Referenced by | Informational | informatively references |