Skip to main content

References from draft-drake-bess-enhanced-vpn

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.

Reference type help

Document Title Status Type Downref
BCP 14
References Referenced by
normatively references
BCP 26
References Referenced by
normatively references
draft-ietf-idr-segment-routing-te-policy Advertising Segment Routing Policies in BGP
References Referenced by
Proposed Standard informatively references
draft-ietf-spring-sr-for-enhanced-vpn Segment Routing based Network Resource Partition (NRP) for Enhanced VPN
References Referenced by
informatively references
draft-ietf-teas-applicability-actn-slicing Applicability of Abstraction and Control of Traffic Engineered Networks (ACTN) to Network Slicing
References Referenced by
Informational informatively references
draft-ietf-teas-enhanced-vpn A Framework for NRP-based Enhanced Virtual Private Network
References Referenced by
Informational informatively references
draft-ietf-teas-ietf-network-slices A Framework for Network Slices in Networks Built from IETF Technologies
References Referenced by
Informational informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
References Referenced by
Proposed Standard normatively references
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels
References Referenced by
Proposed Standard informatively references
RFC 4271 A Border Gateway Protocol 4 (BGP-4)
References Referenced by
Draft Standard normatively references
RFC 4360 BGP Extended Communities Attribute
References Referenced by
Proposed Standard informatively references
RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs)
References Referenced by
Proposed Standard normatively references
RFC 4456 BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
References Referenced by
Draft Standard informatively references
RFC 4684 Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)
References Referenced by
Proposed Standard informatively references
RFC 7432 BGP MPLS-Based Ethernet VPN
References Referenced by
Proposed Standard normatively references
RFC 7606 Revised Error Handling for BGP UPDATE Messages
References Referenced by
Proposed Standard normatively references
RFC 7752 North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by
Proposed Standard normatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8299 YANG Data Model for L3VPN Service Delivery
References Referenced by
Proposed Standard informatively references
RFC 8309 Service Models Explained
References Referenced by
Informational informatively references
RFC 8402 Segment Routing Architecture
References Referenced by
Proposed Standard informatively references
RFC 8453 Framework for Abstraction and Control of TE Networks (ACTN)
References Referenced by
Informational informatively references
RFC 9012 The BGP Tunnel Encapsulation Attribute
References Referenced by
Proposed Standard normatively references