MPLS/BGP IP VPNs
I worked on MPLS/BGP IP VPNs since the early days. As a lead architect at AT&T, I was a main contributor to the design and deployment of the
I have been very active in the L3 IP VPN and MPLS communities, and in the related IETF WGs, contributing to several of the main innovations in the area, including BGP/MPLS IP VPNs, MPLS-TP, and Virtual PE/Virtual CE.
Here are a few links to some of the most significant IP VPNs and MPLS RFCs/IDs that I have co-authored on this subject.
- RFC 4364, “BGP/MPLS IP Virtual Private Networks (VPNs).”
- RFC 4111, “Security Framework for Provider Provisioned Virtual Private Networks,” and RFC 5920, “MPLS and GMPLS Security Framework.”
- RFC 4031, “Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks.”
- RFC 4684, “Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)," and RFC 3564, “Requirements for support of Differentiated Services-aware MPLS Traffic Engineering.”
- RFC 6388, “Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths,” and RFC 5501, “Requirements for Multicast Support in Virtual Private LAN Services.”
- RFC 6373, “MPLS-TP Control Plane Framework,” and RFC 6941: “MPLS Transport Profile (MPLS-TP) Security Framework.”
- RFC 6669, “An Overview of the Operations, Administration, and Maintenance (OAM) Toolset for MPLS-Based Transport Networks.”
- "BGP-signaled end-system IP/VPNs" (draft-ietf-l3vpn-end-system), request for RFC publication.
DHCP Extensions
DHCP has been around forever (RFC 1531 was published in 1993), but it is still being worked on very actively, especially for DHCPv6. Service providers are finding new good uses for this protocol all the time.
- Our IETF draft, "Forcerenew Reconfiguration Extensions for DHCPv4" (draft-fang-dhc-dhcpv4-forcerenew-extensions), proposes a few simple extension for DHCPv4 to achieve feature parity with v6.