References from draft-beeram-ccamp-gmpls-enni
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 | ||
| draft-beeram-ccamp-melg |
Mutually Exclusive Link Group (MELG)
References Referenced by |
normatively references | ||
| draft-farrel-interconnected-te-info-exchange |
Problem Statement and Architecture for Information Exchange Between Interconnected Traffic Engineered Networks
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4202 |
Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4208 |
Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4655 |
A Path Computation Element (PCE)-Based Architecture
References Referenced by |
Informational | informatively references | |
| RFC 4847 |
Framework and Requirements for Layer 1 Virtual Private Networks
References Referenced by |
Informational | informatively references | |
| RFC 5440 |
Path Computation Element (PCE) Communication Protocol (PCEP)
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 5623 |
Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering
References Referenced by |
Informational | Possible Reference |