Ingress Replication Tunnels in Multicast VPN
RFC 7988

Document Type RFC - Proposed Standard (October 2016; No errata)
Last updated 2016-10-06
Replaces draft-rosen-l3vpn-ir
Stream IETF
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Thomas Morin
Shepherd write-up Show (last changed 2016-04-25)
IESG IESG state RFC 7988 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to aretana@cisco.com
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
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 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  What is an IR P-tunnel? . . . . . . . . . . . . . . . . . . .   5
   3.  How are IR P-tunnels identified?  . . . . . . . . . . . . . .   7
   4.  How to Join an IR P-Tunnel  . . . . . . . . . . . . . . . . .   9
     4.1.  Advertised IR P-Tunnels . . . . . . . . . . . . . . . . .   9
       4.1.1.  If the Leaf Information Required Bit Is Set . . . . .  10
       4.1.2.  If the Leaf Information Required Bit Is Not Set . . .  10
     4.2.  Unadvertised IR P-Tunnels . . . . . . . . . . . . . . . .  11
   5.  The PTA's Tunnel Identifier Field . . . . . . . . . . . . . .  11
   6.  A Note on IR P-Tunnels and Discarding Packets from the Wrong
       PE  . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   7.  The PTA's MPLS Label Field  . . . . . . . . . . . . . . . . .  14
     7.1.  Leaf A-D Route Originated by an Egress PE . . . . . . . .  14
     7.2.  Leaf A-D Route Originated by an Intermediate Node . . . .  16
     7.3.  Intra-AS I-PMSI A-D Route . . . . . . . . . . . . . . . .  17
   8.  How A Child Node Prunes Itself from an IR P-Tunnel  . . . . .  17
   9.  Parent Node Actions upon Receiving Leaf A-D Route . . . . . .  18
   10. Use of Timers When Switching UMH  . . . . . . . . . . . . . .  19
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  20
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
      12.1. Normative References . . . . . . . . . . . . . . . . . .  21
      12.2. Informative References . . . . . . . . . . . . . . . . .  21
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

Rosen, et al.                Standards Track                    [Page 2]
RFC 7988                   IR Tunnels in MVPN               October 2016
Show full document text