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

Document Type Replaced Internet-Draft (bess WG)
Last updated 2015-01-02 (latest revision 2014-07-01)
Replaces draft-zzhang-l3vpn-mvpn-bidir-ingress-replication
Replaced by RFC 7740
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-bess-mvpn-bidir-ingress-replication
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

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-l3vpn-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 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.)