Multicast VPN Using BIER
draft-ietf-bier-mvpn-07
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (bier WG)
|
|
Last updated |
|
2017-08-01
(latest revision 2017-07-26)
|
|
Replaces |
|
draft-rosen-l3vpn-mvpn-bier
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
(wg milestone:
Mar 2018 - Published as propose...
)
Doc Shepherd Follow-up Underway
|
|
Document shepherd |
|
Nabeel Cocker
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Nabeel Cocker <nabeel.cocker@nokia.com>
|
Internet Engineering Task Force E. Rosen, Ed.
Internet-Draft Juniper Networks, Inc.
Intended status: Experimental M. Sivakumar
Expires: January 27, 2018 Cisco Systems, Inc.
S. Aldrin
Google, Inc.
A. Dolganow
Nokia
T. Przygienda
Juniper Networks, Inc.
July 26, 2017
Multicast VPN Using BIER
draft-ietf-bier-mvpn-07
Abstract
The Multicast Virtual Private Network (MVPN) specifications require
the use of multicast tunnels ("P-tunnels") that traverse a Service
Provider's backbone network. The P-tunnels are used for carrying
multicast traffic across the backbone. A variety of P-tunnel types
are supported. Bit Index Explicit Replication (BIER) is a new
architecture that provides optimal multicast forwarding through a
"multicast domain", without requiring intermediate routers to
maintain any per-flow state or to engage in an explicit tree-building
protocol. This document specifies the protocol and procedures that
allow MVPN to use BIER as the method of carrying multicast traffic
over an SP backbone network.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 27, 2018.
Rosen, et al. Expires January 27, 2018 [Page 1]
Internet-Draft MVPN with BIER July 2017
Copyright Notice
Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Use of the PMSI Tunnel Attribute in x-PMSI A-D Routes . . . . 5
2.1. MPLS Label . . . . . . . . . . . . . . . . . . . . . . . 6
2.2. Explicit Tracking . . . . . . . . . . . . . . . . . . . . 8
2.2.1. Using the LIR Flag . . . . . . . . . . . . . . . . . 9
2.2.2. Using the LIR-pF Flag . . . . . . . . . . . . . . . . 9
3. Use of the PMSI Tunnel Attribute in Leaf A-D routes . . . . . 10
4. Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Encapsulation and Transmission . . . . . . . . . . . . . 11
4.2. Disposition . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.1. At a BFER that is an Egress PE . . . . . . . . . . . 13
4.2.2. At a BFER that is a P-tunnel Segmentation Boundary . 13
5. Contributor Addresses . . . . . . . . . . . . . . . . . . . . 13
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
[RFC6513] and [RFC6514] specify the protocols and procedures that a
Service Provider (SP) can use to provide Multicast Virtual Private
Network (MVPN) service to its customers. Multicast tunnels are
created through an SP's backbone network; these are known as
"P-tunnels". The P-tunnels are used for carrying multicast traffic
Show full document text