[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 draft-abhattacharya-bess-l2vpn-ipv6-remotepe

INTERNET-DRAFT                                         Avik Bhattacharya
                                                       Apratim Mukherjee
Intended Status: Proposed Standard                                  Ixia
Expires: July 17, 2015                                  January 13, 2015


Provisioning, Auto-Discovery, and Signaling in L2VPNs for IPv6 Remote PE
          draft-abhattacharya-l2vpn-signaling-ipv6-remotepe-00


Abstract

   L2VPN Signaling specification defines the semantic structure of the
   endpoint identifiers required by each model.  It discusses the
   distribution of these identifiers by the discovery process,
   especially when discovery is based on the Border Gateway Protocol
   (BGP).  This document updates the end point encoding for BGP-Based
   Auto-Discovery and suggests a format for NLRI encoding for IPv6 PE
   Address.


Status of this Memo

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

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008. The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."




Bhattacharya, et al.     Expires July 17, 2015                  [Page 1]


INTERNET DRAFT     L2VPN signaling for IPv6 Remote PE   January 13, 2015


   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html


   This Internet-Draft will expire on July 17, 2015.






Copyright and License Notice

   Copyright (c) 2015 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   (http://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
   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. This document may contain
   material from IETF Documents or IETF Contributions published or made
   publicly available before November 10, 2008.  The person(s)
   controlling the copyright in some of this   material may not have
   granted the IETF Trust the right to allow modifications of such
   material outside the IETF Standards Process. Without obtaining an
   adequate license from the person(s) controlling the copyright in such
   materials, this document may not be modified outside the IETF
   Standards Process, and derivative works of it may not be created
   outside the IETF Standards Process, except to format it for
   publication as an RFC or to translate it into languages other than
   English.














Bhattacharya, et al.     Expires July 17, 2015                  [Page 2]


INTERNET DRAFT     L2VPN signaling for IPv6 Remote PE   January 13, 2015


Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2  BGP NLRI format for the IPv6 PE Address . . . . . . . . . . . .  4
   3  Discussion on Route Distinguisher(RD) and Route Target(RT)  . .  5
   4  Security Considerations . . . . . . . . . . . . . . . . . . . .  5
   5  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  5
   6  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     6.1  Normative References  . . . . . . . . . . . . . . . . . . .  6
     6.2  Informative References  . . . . . . . . . . . . . . . . . .  6
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  6







































Bhattacharya, et al.     Expires July 17, 2015                  [Page 3]


INTERNET DRAFT     L2VPN signaling for IPv6 Remote PE   January 13, 2015


1  Introduction

   RFC 6074 specifies a number of L2VPN provisioning models, and further
   specifies the semantic structure of the endpoint identifiers required
   by each model.  It discusses the distribution of these identifiers by
   the discovery process, especially when discovery is based on the
   Border Gateway Protocol (BGP).  It then specifies how the endpoint
   identifiers are carried in the two signaling protocols that are used
   to set up PWs, the Label Distribution Protocol (LDP), and the Layer 2
   Tunneling Protocol version 3 (L2TPv3).  This draft updates the
   section 3.2.2.1 of RFC 6074 (BGP-Based Auto-Discovery) and suggests a
   format for NLRI encoding for IPv6 PE Address.

1.1  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].


2  BGP NLRI format for the IPv6 PE Address

   RFC 6074 Section 3.2.2.1 defines the BGP advertisement for a
   particular VSI at a given PE will contain:

      o  an NLRI of AFI = L2VPN, SAFI = VPLS, encoded as RD:PE_addr

      o  a BGP next hop equal to the loopback address of the PE

      o  an Extended Community Attribute containing the VPLS-id

      o  an Extended Community Attribute containing one or more RTs.

   The format for the NLRI encoding defined in RFC 6074 Section 3.2.2.1
   is:

           +------------------------------------+
           |  Length (2 octets)                 |
           +------------------------------------+
           |  Route Distinguisher (8 octets)    |
           +------------------------------------+
           |  PE_addr (4 octets)                |
           +------------------------------------+


   In this format the size of the PE_addr is defined as 4 octets which
   can carry only IPv4 addresses. In a situation where the route is
   originating from a BGP end point running on an IPv6 address, the



Bhattacharya, et al.     Expires July 17, 2015                  [Page 4]


INTERNET DRAFT     L2VPN signaling for IPv6 Remote PE   January 13, 2015


   PE_addr in the NLRI needs to carry that IPv6 address. The updated
   format for the NLRI encoding is:


           +------------------------------------+
           |  Length (2 octets)                 |
           +------------------------------------+
           |  Route Distinguisher (8 octets)    |
           +------------------------------------+
           |  PE_addr (4 or 16 octets)          |
           +------------------------------------+


   The length field MUST contain the sum of the length of the Length
   field(2), the length of the Route Distiguisher(8) and the length of
   the 4 or 16 octet PE_addr field.

   The type of the PE_addr can be derived by the receiving node by
   subtracting the fixed length of the Route Distinguisher and the
   Length field from the value of the received Length.

   This PE_addr should be used to initiate adjacency of the underlying
   signaling protocol if it supports IPv6 endpoints.(such as LDPv6)

3  Discussion on Route Distinguisher(RD) and Route Target(RT)

   Note that RD and RT can be in format AS 2byte + 4 byte Assigned
   Number or IP 4 byte + 2 byte Assigned Number. Just like RD or RT
   cannot carry 4 byte AS numbers , they also cannot utilize 16 byte
   IPv6 Address. Updates to RD and RT to operate in a pure IPv6
   environment is outside the scope of this document.


4  Security Considerations

   There is no additional security impact in addition to what is
   mentioned in RFC6074.


5  IANA Considerations

   No new IANA considerations are introduced in this specifications.









Bhattacharya, et al.     Expires July 17, 2015                  [Page 5]


INTERNET DRAFT     L2VPN signaling for IPv6 Remote PE   January 13, 2015


6  References

6.1  Normative References

   [RFC6074]  E. Rosen, B. Davie, "Provisioning, Auto-Discovery, and
              Signaling in Layer 2 Virtual Private Networks (L2VPNs)",
              BCP 74, RFC 6074, January 2011,
              <http://www.rfc-editor.org/info/rfc6074>.



6.2  Informative References

   [RFC4364]  E. Rosen, "BGP/MPLS IP Virtual Private Networks (VPNs)",
              BCP 78, RFC 4364, February 2006,
              <http://www.rfc-editor.org/info/rfc4364>.


Authors' Addresses


              Avik Bhattacharya
              Ixia
              Infinity Building, Tower 2, Floor -4
              Sector 5, Saltlike,
              Kolkata, West Bengal, India - 700091.

              EMail: abhattacharya@ixiacom.com

              Apratim Mukherjee
              Ixia
              Infinity Building, Tower 2, Floor -4
              Sector 5, Saltlike,
              Kolkata, West Bengal, India - 700091.

              EMail: amukherjee@ixiacom.com















Bhattacharya, et al.     Expires July 17, 2015                  [Page 6]


Html markup produced by rfcmarkup 1.123, available from https://tools.ietf.org/tools/rfcmarkup/