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

The information below is for an old version of the document
Document Type Expired Internet-Draft (bess WG)
Last updated 2015-07-20 (latest revision 2015-01-14)
Replaces draft-ietf-l3vpn-mvpn-bidir-ingress-replication
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Thomas Morin
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Thomas Morin" <thomas.morin@orange.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-bess-mvpn-bidir-ingress-replication-00.txt

Abstract

RFC 6513 described a method to support bidirectional C-flow using "Partial Mesh of MP2MP P-Tunnels". This document describes 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 service to its VPN customers.

Authors

Zhaohui Zhang (zzhang@juniper.net)
Yakov Rekhter (yakov@juniper.net)
Andrew Dolganow (andrew.dolganow@alcatel-lucent.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)