draft-ietf-pim-join-attributes-for-lisp-05.txt   draft-ietf-pim-join-attributes-for-lisp-06.txt 
Network Working Group J. Arango Network Working Group J. Arango
Internet-Draft S. Venaas Internet-Draft S. Venaas
Intended status: Experimental Cisco Systems Intended status: Experimental Cisco Systems
Expires: April 13, 2017 I. Kouvelas Expires: June 8, 2017 I. Kouvelas
Arista Networks Inc. Arista Networks Inc.
D. Farinacci D. Farinacci
lispers.net lispers.net
October 10, 2016 December 5, 2016
PIM Join Attributes for LISP Environments PIM Join Attributes for LISP Environments
draft-ietf-pim-join-attributes-for-lisp-05.txt draft-ietf-pim-join-attributes-for-lisp-06.txt
Abstract Abstract
This document defines two PIM Join/Prune attributes that support the This document defines two PIM Join/Prune attributes that support the
construction of multicast distribution trees where the root and construction of multicast distribution trees where the root and
receivers are located in different LISP sites. These attributes receivers are located in different LISP sites. These attributes
allow the receiver site to select between unicast and multicast allow the receiver site to select between unicast and multicast
underlay transport and to convey the receiver ETR's RLOC address to underlay transport and to convey the RLOC (Routing Locator) address
the control plane of the root ITR. of the receiver ETR (Egress Tunnel Router) to the control plane of
the root ITR (Ingress Tunnel Router).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 13, 2017. This Internet-Draft will expire on June 8, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 15 skipping to change at page 2, line 16
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
3. PIM Join/Prune Attributes . . . . . . . . . . . . . . . . . . 3 3. PIM Join/Prune Attributes . . . . . . . . . . . . . . . . . . 3
4. The Transport Attribute . . . . . . . . . . . . . . . . . . . 3 4. The Transport Attribute . . . . . . . . . . . . . . . . . . . 4
4.1. Transport Attribute Format . . . . . . . . . . . . . . . 4 4.1. Transport Attribute Format . . . . . . . . . . . . . . . 4
4.2. Using the Transport Attribute . . . . . . . . . . . . . . 4 4.2. Using the Transport Attribute . . . . . . . . . . . . . . 5
5. Receiver ETR RLOC Attribute . . . . . . . . . . . . . . . . . 5 5. Receiver ETR RLOC Attribute . . . . . . . . . . . . . . . . . 5
5.1. Receiver RLOC Attribute Format . . . . . . . . . . . . . 5 5.1. Receiver RLOC Attribute Format . . . . . . . . . . . . . 6
5.2. Using the Receiver RLOC Attribute . . . . . . . . . . . . 6 5.2. Using the Receiver RLOC Attribute . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The construction of multicast distribution trees where the root and The construction of multicast distribution trees where the root and
receivers are located in different LISP sites [RFC6830] is defined in receivers are located in different LISP sites [RFC6830] is defined in
[RFC6831]. Creation of (root-EID,G) state in the root site requires [RFC6831]. Creation of (root-EID,G) state in the root site requires
that unicast LISP-encapsulated Join/Prune messages be sent from an that unicast LISP-encapsulated Join/Prune messages be sent from an
ETR on the receiver site to an ITR on the root site. ETR on the receiver site to an ITR on the root site. The term EID is
short for Endpoint ID.
[RFC6831] specifies that (root-EID,G) data packets are to be LISP- [RFC6831] specifies that (root-EID,G) data packets are to be LISP-
encapsulated into (root-RLOC,G) multicast packets. However, a wide encapsulated into (root-RLOC,G) multicast packets. However, a wide
deployment of multicast connectivity between LISP sites is unlikely deployment of multicast connectivity between LISP sites is unlikely
to happen any time soon. In fact, some implementations are initially to happen any time soon. In fact, some implementations are initially
focusing on unicast transport with head-end replication between root focusing on unicast transport with head-end replication between root
and receiver sites. and receiver sites.
The unicast LISP-encapsulated Join/Prune message specifies the (root- The unicast LISP-encapsulated Join/Prune message specifies the (root-
EID,G) state that needs to be established in the root site, but EID,G) state that needs to be established in the root site, but
conveys nothing about the receivers capability or desire to use conveys nothing about the receivers capability or desire to use
multicast as the underlying transport. This document specifies a multicast as the underlying transport. This document specifies a
Join/Prune attribute that allows the receiver ETR to select the Join/Prune attribute that allows the receiver ETR to select the
desired transport. desired transport.
The term transport in this document is intentionally somewhat vague.
Currently it is used just to indicate whether multicast or head-end
replication is used. Which means that the outer destination address
is either a unicast or multicast address. Future documents may
specify how other types of delivery, encapsulation or underlay are
used.
Knowledge of the receiver ETR's RLOC address is also essential to the Knowledge of the receiver ETR's RLOC address is also essential to the
control plane of the root ITR. It determines the downstream control plane of the root ITR. The RLOC address determines the
destination for unicast head-end replication and identifies the downstream destination for unicast head-end replication and
receiver ETR that needs to be notified should the root of the identifies the receiver ETR that needs to be notified should the root
distribution tree move to another site. ITR of the distribution tree move to another site. The root ITR can
change when the source EID is roaming to another LISP site.
Service providers may implement uRPF policies requiring that the Service providers may implement uRPF policies requiring that the
outer source address of the LISP-encapsulated Join/Prune message be outer source address of the LISP-encapsulated Join/Prune message be
the address of the receiver ETR's core-facing interface used to the address of the receiver ETR's core-facing interface used to
physically transmit the message. However, due to policy and load physically transmit the message. However, due to policy and load
balancing considerations, the outer source address may not be the balancing considerations, the outer source address may not be the
RLOC on which the receiver site wishes to receive a particular flow. RLOC on which the receiver site wishes to receive a particular flow.
This document specifies a Join/Prune attribute that conveys the This document specifies a Join/Prune attribute that conveys the
appropriate receiver ETR's RLOC address to the control plane of the appropriate receiver ETR's RLOC address to the control plane of the
root ITR. root ITR.
This document uses terminology defined in [RFC6830], such as EID,
RLOC, ITR and ETR.
2. Requirements Notation 2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. PIM Join/Prune Attributes 3. PIM Join/Prune Attributes
PIM Join/Prune attributes are defined in [RFC5384] by introducing a PIM Join/Prune attributes are defined in [RFC5384] by introducing a
new Encoded-Source type that, in addition to the Join/Prune source, new Encoded-Source type that, in addition to the Join/Prune source,
 End of changes. 13 change blocks. 
15 lines changed or deleted 28 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/