Skip to main content

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)
Expired & archived
Authors Zhaohui (Jeffrey) Zhang , Yakov Rekhter , Andrew Dolganow
Last updated 2015-01-02 (Latest revision 2014-07-01)
Replaces draft-zzhang-l3vpn-mvpn-bidir-ingress-replication
Replaced by draft-ietf-bess-mvpn-bidir-ingress-replication
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-bess-mvpn-bidir-ingress-replication
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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 (Jeffrey) Zhang
Yakov Rekhter
Andrew Dolganow

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