BGP based Virtual Private Network (VPN) Services over SRm6 enabled IPv6 networks
draft-ssangli-bess-bgp-vpn-srm6-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01

IDR                                                            S. Sangli
Internet-Draft                                                 R. Bonica
Intended status: Standards Track                   Juniper Networks Inc.
Expires: September 10, 2020                               March 09, 2020

BGP based Virtual Private Network (VPN) Services over SRm6 enabled IPv6
                                networks
                   draft-ssangli-bess-bgp-vpn-srm6-01

Abstract

   This document defines BGP protocol extensions for encoding and
   carrying SRm6 Tunnel Payload Forwarding information (TPF) to support
   Virtual Private Network services.  This is applicable when the VPN
   services are offered in a SRm6 enabled IPv6 network such that the VPN
   payload is transported over IPv6.  The Tunnel Payload Information is
   encoded in the IPv6 Destination Option Header in the IPv6 data
   packets.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 10, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Sangli & Bonica        Expires September 10, 2020               [Page 1]
Internet-DraftBGP based VPN Services over SRm6 enabled IPv6   March 2020

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Per-Path Service Instruction Information  . . . . . . . . . .   3
   4.  Usage of Tunnel Encapsulation Attribute . . . . . . . . . . .   4
   5.  Procedures for Egress BGP Speaker . . . . . . . . . . . . . .   6
   6.  Procedures for Ingress BGP Speaker  . . . . . . . . . . . . .   7
   7.  BGP Nexthop and Tunnel Endpoint address handling
       procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  BGP based L3 VPN services over IPv6 . . . . . . . . . . . . .   8
     8.1.  IPv4 VPN on SRm6 enabled IPv6 Core  . . . . . . . . . . .   8
     8.2.  IPv6 VPN on SRm6 enabled IPv6 Core  . . . . . . . . . . .   8
     8.3.  IPv4 Global Routes on SRm6 enabled IPv6 Core  . . . . . .   9
   9.  BGP based Ethernet VPN services over IPv6 . . . . . . . . . .   9
     9.1.  Ethernet Per ES Auto-Discovery (A-D) route  . . . . . . .  10
     9.2.  Ethernet per EVI Auto-Discovery (A-D) route . . . . . . .  10
     9.3.  MAC/IP Advertisement route  . . . . . . . . . . . . . . .  11
     9.4.  Inclusive Multicast Ethernet Route  . . . . . . . . . . .  11
     9.5.  IP Prefix Route . . . . . . . . . . . . . . . . . . . . .  12
   10. Deployment Considerations . . . . . . . . . . . . . . . . . .  12
   11. Backward Compatibility  . . . . . . . . . . . . . . . . . . .  13
   12. Security Considerations . . . . . . . . . . . . . . . . . . .  14
   13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   14. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   15. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     15.1.  Normative References . . . . . . . . . . . . . . . . . .  14
     15.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Virtual Private Network (VPN) technologies allow network providers to
   emulate private networks with shared infrastructure.  For example,
   assume that a set of red sites, set of blue sites and a set of green
   sites connect to a provider network.  Furthermore, assume that red
   sites and blue sites wish to interconnect, exchange packets.
   However, the green sites wish to communicate with green sites only.
   The provider should allow its infrastructure network to scale to both
   the requirements without having to create multiple parallel network