Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress Replication
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: <firstname.lastname@example.org>, The IESG <email@example.com>, <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com Subject: Protocol Action: 'Simulating "Partial Mesh of MP2MP P-Tunnels" with Ingress Replication' to Proposed Standard (draft-ietf-bess-mvpn-bidir-ingress-replication-04.txt) The IESG has approved the following document: - 'Simulating "Partial Mesh of MP2MP P-Tunnels" with Ingress Replication' (draft-ietf-bess-mvpn-bidir-ingress-replication-04.txt) as Proposed Standard This document is the product of the BGP Enabled Services Working Group. The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-bidir-ingress-replication/
Technical Summary This specifies an alternate technique than what has already been described to transport Bidir-PIM multicast traffic of a multicast VPN across a provider network. 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. Working Group Summary No controversy or rough consensus decisions. Document Quality The document is of good technical quality. There is no known implementation yet, but one vendor has mentioned plans for implementing these specs. Personnel Thomas Morin is the doc shepherd. Alvaro Retana is the responsible AD.