Browse Prior Art Database

Ingress Replication Tunnels in Multicast VPN (RFC7988)

IP.com Disclosure Number: IPCOM000247868D
Original Publication Date: 2016-Oct-01
Included in the Prior Art Database: 2016-Oct-08
Document File: 46 page(s) / 56K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Rosen: AUTHOR [+4]

Abstract

RFCs 6513, 6514, and other RFCs describe procedures by which a Service Provider (SP) may offer Multicast VPN (MVPN) service to its customers. These procedures create point-to-multipoint (P2MP) or multipoint-to-multipoint (MP2MP) tunnels, called "P-tunnels" (provider tunnels), across the SP's backbone network. Customer multicast traffic is carried through the P-tunnels.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                     E. Rosen, Ed. Request for Comments: 7988                        Juniper Networks, Inc. Updates: 6513, 6514                                       K. Subramanian Category: Standards Track                               Sproute Networks ISSN: 2070-1721                                                 Z. Zhang                                                   Juniper Networks, Inc.                                                             October 2016

               Ingress Replication Tunnels in Multicast VPN

Abstract

   RFCs 6513, 6514, and other RFCs describe procedures by which a

   Service Provider may offer Multicast VPN (MVPN) service to its

   customers.  These procedures create point-to-multipoint (P2MP) or

   multipoint-to-multipoint (MP2MP) trees across the Service Provider's

   backbone.  One type of P2MP tree that may be used is known as an

   "Ingress Replication (IR) tunnel".  In an IR tunnel, a parent node

   need not be directly connected to its child nodes.  When a parent

   node has to send a multicast data packet to its n child nodes, it

   does not use Layer 2 multicast, IP multicast, or MPLS multicast to do

   so.  Rather, it makes n individual copies, and then unicasts each

   copy, through an IP or MPLS unicast tunnel, to exactly one child

   node.  While the prior MVPN specifications allow the use of IR

   tunnels, those specifications are not always very clear or explicit

   about how the MVPN protocol elements and procedures are applied to IR

   tunnels.  This document updates RFCs 6513 and 6514 by adding

   additional details that are specific to the use of IR tunnels.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7988.

 Rosen, et al.                Standards Track                    [Page 1]
 RFC 7988                   IR Tunnels in MVPN               October 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP...