References from draft-vasseur-ccamp-ospf-te-caps
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 11 |
References Referenced by |
Possible Reference | ||
draft-ietf-isis-traffic |
Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-mpls-p2mp-requirement |
Requirements for Point to Multipoint Traffic Engineered MPLS LSPs
References Referenced by |
informatively references | ||
draft-ietf-ospf-cap |
Extensions to OSPF for Advertising Optional Router Capabilities
References Referenced by |
Proposed Standard | informatively references | |
draft-vasseur-mpls-ospf-te-cap |
OSPF Traffic Engineering capability TLVs
References Referenced by |
Possible Reference | ||
draft-yasukawa-mpls-rsvp-p2mp |
Extended RSVP-TE for Point-to-Multipoint LSP Tunnels
References Referenced by |
informatively references | ||
RFC 2026 |
The Internet Standards Process -- Revision 3
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2328 |
OSPF Version 2
References Referenced by |
Internet Standard | normatively references | |
RFC 2370 |
The OSPF Opaque LSA Option
References Referenced by |
Proposed Standard | normatively references | |
RFC 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by |
Proposed Standard | normatively references |