BGP Extension For L3VPN Performance Monitoring
draft-fan-bess-pm-bgp-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             J. Fan
Internet-Draft                                                     Z. Li
Intended status: Standards Track                               S. Zhuang
Expires: January 4, 2018                                          Huawei
                                                           July 03, 2017

             BGP Extension For L3VPN Performance Monitoring
                        draft-fan-bess-pm-bgp-01

Abstract

   This document describes a new VT address family in BGP to exchange
   information required for apply performance monitoring in MPLS/BGP
   VPN, as described in [I-D.dong-l3vpn-pm-framework].

Requirements Language

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

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 http://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 January 4, 2018.

Copyright Notice

   Copyright (c) 2017 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

Fan, et al.              Expires January 4, 2018                [Page 1]
Internet-Draft         BGP Extension For L3VPN PM              July 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminologies . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The New VT Sub Address Family . . . . . . . . . . . . . . . .   3
     3.1.  VT Sub Address Family . . . . . . . . . . . . . . . . . .   3
     3.2.  VT NLRI . . . . . . . . . . . . . . . . . . . . . . . . .   4
       3.2.1.  VT VPN-membership A-D Route . . . . . . . . . . . . .   5
       3.2.2.  VT Labeled Route  . . . . . . . . . . . . . . . . . .   5
   4.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  VRF-to-VRF VPN Membership Auto Discovery  . . . . . . . .   6
     4.2.  VRF-to-VRF Labeled Route Exchange . . . . . . . . . . . .   7
       4.2.1.  VT Labeled Route Update . . . . . . . . . . . . . . .   7
       4.2.2.  VT Labeled Route Withdrawal . . . . . . . . . . . . .   7
     4.3.  VRF-to-VRF Labeled Route Application  . . . . . . . . . .   8
   5.  VT Route Selection Consideration  . . . . . . . . . . . . . .   8
   6.  Deployment Consideration  . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This document describes the BGP encodings and procedures for
   exchanging the information elements required by applying traffic
   performance monitoring in MPLS/BGP VPN, as specified
   in[I-D.dong-l3vpn-pm-framework].

   Current BGP Labeled VPN Route exchange procedure combines VRF VPN-
   membership Auto-Discovery and L3VPN Label allocation together.  While
   applying PM for L3VPN needs BGP extended to support VPN membership
   Auto-Discovery and L3VPN Label allocation in a VRF-to-VRF manner.  To
   achieve this, a new Sub address family, called VRF-to-VRF Tunnel(VT)
   Subsequent Address Family, is introduced.

   This document defines two kinds of routes for VT NLRI:

Fan, et al.              Expires January 4, 2018                [Page 2]
Internet-Draft         BGP Extension For L3VPN PM              July 2017

   VPN-Membership A-D Route: for the use of doing VRF VPN membership
Show full document text