Simulating "Partial Mesh of MP2MP P-Tunnels" with Ingress Replication
draft-ietf-bess-mvpn-bidir-ingress-replication-01

The information below is for an old version of the document
Document Type Active Internet-Draft (bess WG)
Last updated 2015-08-03
Replaces draft-ietf-l3vpn-mvpn-bidir-ingress-replication
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Consensus: Waiting for Write-Up
Doc Shepherd Follow-up Underway
Document shepherd Thomas Morin
Shepherd write-up Show (last changed 2015-07-27)
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Thomas Morin" <thomas.morin@orange.com>
Network Working Group                                           Z. Zhang
Internet-Draft                                                Y. Rekhter
Updates: 6514 (if approved)                             Juniper Networks
Intended status: Standards Track                             A. Dolganow
Expires: February 4, 2016                                 Alcatel-Lucent
                                                          August 3, 2015

 Simulating "Partial Mesh of MP2MP P-Tunnels" with Ingress Replication
         draft-ietf-bess-mvpn-bidir-ingress-replication-01.txt

Abstract

   RFC 6513 described a method to support bidirectional C-flow using
   "Partial Mesh of MP2MP P-Tunnels".  This document specifiess how
   partial mesh of MP2MP P-Tunnels can be simulated with Ingress
   Replication, instead of a real MP2MP tunnel.  This enables a Service
   Provider to use Ingress Replication to offer transparent BIDIR-PIM
   [RFC 5015] service to its VPN customers.  These specifications update
   RFC6514.

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 February 4, 2016.

Copyright 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

Zhang, et al.           Expires February 4, 2016                [Page 1]
Internet-Draft           C-Bidir support with IR             August 2015

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Requirements Language  . . . . . . . . . . . . . . . . . . . .  4
   3.  Operation  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Control State  . . . . . . . . . . . . . . . . . . . . . .  5
     3.2.  Forwarding State . . . . . . . . . . . . . . . . . . . . .  7
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 12
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

Zhang, et al.           Expires February 4, 2016                [Page 2]
Internet-Draft           C-Bidir support with IR             August 2015

1.  Introduction

   Section 11.2 of RFC 6513, "Partitioned Sets of PEs", describes two
   methods of carrying bidirectional C-flow traffic over a provider core
   without using the core as RPL or requiring Designated Forwarder
   election.

   With these two methods, all PEs of a particular VPN are separated
   into partitions, with each partition being all the PEs that elect the
   same PE as the Upstream PE wrt the C-RPA.  A PE must discard
   bidirectional C-flow traffic from PEs that are not in the same
   partition as the PE itself.

   In particular, Section 11.2.3 of RFC 6513, "Partial Mesh of MP2MP
   P-Tunnels", guarantees the above discard behavior without using an
   extra PE Distinguisher label by having all PEs in the same partition
   join a single MP2MP tunnel dedicated to that partition and use it to
   transmit traffic.  All traffic arriving on the tunnel will be from
   PEs in the same partition, so it will be always accepted.

   RFC 6514 specifies BGP encodings and procedures used to implement
   MVPN as specified in RFC 6513, while the details related to MP2MP
   tunnels are specified in [draft-ietf-l3vpn-mvpn-bidir-08].

   [draft-ietf-l3vpn-mvpn-bidir-08] assumes that an MP2MP P-tunnel is
   realized either via PIM-Bidir, or via MP2MP mLDP.  Each of them would
Show full document text