References from rfc4664
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 |
|---|---|---|---|---|
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 1771 |
A Border Gateway Protocol 4 (BGP-4) Refs Ref'd by |
Draft Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2661 |
Layer Two Tunneling Protocol "L2TP" Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 2684 |
Multiprotocol Encapsulation over ATM Adaptation Layer 5 Refs Ref'd by |
Proposed Standard | Possible Reference | |
| RFC 2796 |
BGP Route Reflection - An Alternative to Full Mesh IBGP Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 3036 |
LDP Specification Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 3985 |
Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture Refs Ref'd by |
Informational | normatively references | |
| RFC 4026 |
Provider Provisioned Virtual Private Network (VPN) Terminology Refs Ref'd by |
Informational | normatively references | |
| RFC 4665 |
Service Requirements for Layer 2 Provider-Provisioned Virtual Private Networks Refs Ref'd by |
Informational | normatively references |