draft-ietf-pim-join-attributes-for-lisp-03.txt   draft-ietf-pim-join-attributes-for-lisp-04.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: November 21, 2016 I. Kouvelas Expires: December 16, 2016 I. Kouvelas
Arista Networks Inc. Arista Networks Inc.
May 20, 2016 D. Farinacci
lispers.net
June 14, 2016
PIM Join Attributes for LISP Environments PIM Join Attributes for LISP Environments
draft-ietf-pim-join-attributes-for-lisp-03.txt draft-ietf-pim-join-attributes-for-lisp-04.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
transport and to convey the receiver RLOC address to the control underlay transport and to convey the receiver ETR's RLOC address to
plane of the root xTR. the control plane of the root ITR.
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 November 21, 2016. This Internet-Draft will expire on December 16, 2016.
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 16 skipping to change at page 2, line 18
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 . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . 4
5. Receiver RLOC Attribute . . . . . . . . . . . . . . . . . . . 4 5. Receiver ETR RLOC Attribute . . . . . . . . . . . . . . . . . 5
5.1. Receiver RLOC Attribute Format . . . . . . . . . . . . . 5 5.1. Receiver RLOC Attribute Format . . . . . . . . . . . . . 5
5.2. Using the Receiver RLOC Attribute . . . . . . . . . . . . 6 5.2. Using the Receiver RLOC Attribute . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Normative References . . . . . . . . . . . . . . . . . . . . 6 8. Normative References . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 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
xTR on the receiver site to an xTR on the root site. ETR on the receiver site to an ITR on the root site.
[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 to select the desired Join/Prune attribute that allows the receiver ETR to select the
transport. desired transport.
Knowledge of the receiver RLOC is also essential to the control plane Knowledge of the receiver ETR's RLOC address is also essential to the
of the root xTR. It determines the downstream destination for control plane of the root ITR. It determines the downstream
unicast head-end replication and identifies the receiver xTR that destination for unicast head-end replication and identifies the
needs to be notified should the root of the distribution tree move to receiver ETR that needs to be notified should the root of the
another site. distribution tree move to another site.
The outer source address field of the encapsulated Join/Prune message Service providers may implement URPF policies requiring that the
contains an RLOC address of the receiver xTR. This source address is outer source address of the LISP-encapsulated Join/Prune message be
message to the root xTR RLOC destination. Due to policy and load the address of the receiver ETR's core-facing interface used to
balancing considerations, the selected source address may not be the physically transmit the message. However, due to policy and load
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 RLOC address to the control plane of the root appropriate receiver ETR's RLOC address to the control plane of the
xTR. root ITR.
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
skipping to change at page 4, line 35 skipping to change at page 4, line 38
Transport: The type of transport being requested. Set to 0 for Transport: The type of transport being requested. Set to 0 for
multicast. Set to 1 for unicast. multicast. Set to 1 for unicast.
4.2. Using the Transport Attribute 4.2. Using the Transport Attribute
Hierarchical Join/Prune attribute instances Hierarchical Join/Prune attribute instances
[I-D.ietf-pim-hierarchicaljoinattr] SHOULD be used when the same [I-D.ietf-pim-hierarchicaljoinattr] SHOULD be used when the same
Transport Attribute is to be applied to all the sources within the Transport Attribute is to be applied to all the sources within the
Join/Prune message or all the sources within a group set. The root Join/Prune message or all the sources within a group set. The root
xTR MUST accept Transport Attributes in the Upstream Neighbor ITR MUST accept Transport Attributes in the Upstream Neighbor
Encoded-Unicast address, Encoded-Group addresses, and Encoded-Source Encoded-Unicast address, Encoded-Group addresses, and Encoded-Source
addresses. addresses.
There MUST NOT be more than one Transport Attribute within the same There MUST NOT be more than one Transport Attribute within the same
encoded address. If an encoded address has more than one instance of encoded address. If an encoded address has more than one instance of
the attribute, the root xTR MUST discard all affected Join/Prune the attribute, the root ITR MUST discard all affected Join/Prune
sources. sources.
5. Receiver RLOC Attribute 5. Receiver ETR RLOC Attribute
The root xTR must know the receiver RLOC addresses of all receiver When a receiver ETR requests unicast head-end replication for a given
sites for a given (root-EID,G) so that it can perform unicast LISP- (root-EID,G) entry, the PIM control plane of the root ITR must
encapsulation of multicast data packets to each and every receiver maintain an output interface list ("oif-list") entry for the receiver
site that has requested unicast head-end replication. ETR and its corresponding RLOC address. This allows the root ITR to
perform unicast LISP-encapsulation of multicast data packets to each
and every receiver ETR that has requested unicast head-end
replication.
To support mobility of EIDs, the root xTR must keep track of ALL The PIM control plane of the root ITR could potentially determine the
receiver RLOCs even when the corresponding downstream site has not RLOC address of the receiver ETR from the outer source address field
requested unicast replication. The root xTR may detect that a local of LISP-encapsulated Join/Prune message. However, receiver ETRs are
multicast source "root-EID" has moved to a remote LISP site. Under subject to URPF checks by the network providers on each core-facing
such circumstances LISP sends a SMR message to all receiver xTRs, interface. The outer source address must therefore be the RLOC of
prompting them to update their map cache. This is only possible if the core-facing interface used to physically transmit the LISP-
LISP can obtain from PIM the set of all receiver RLOCS that have encapsulated Join/Prune message. Due to policy and load balancing
active Join state for the root-EID. considerations, that may not be the RLOC on which the receiver site
wishes to receive a particular flow. This document specifies a Join/
Prune attribute that conveys the appropriate receiver RLOC address to
the PIM control plane of the root ITR.
The outer source address field of the encapsulated Join/Prune message To support root-EID mobility, receiver ETRs must also be tracked by
contains an RLOC address of the receiver xTR. LISP xTRs, as edge the LISP control plane of the root ITR, regardless of the underlying
devices, are commonly subject to URPF checks by the network providers transport. When the root-EID moves to a new root ITR in a different
on each core-facing interface. The source address for the LISP site, the receiver ETRs do not know the root-EID has moved and
encapsulation header must therefore be the RLOC of the core-facing therefore do not know the RLOC of the new root ITR. This is true for
interface used to physically transmit the encapsulated Join/Prune both unicast and multicast transport modes. The new root ITR does
message. Due to policy and load balancing considerations, that may not have any receiver ETR state. Therefore, it is the responsability
not be the RLOC on which the receiver site wishes to receive a of the old root ITR to inform the receiver ETRs that the root-EID has
particular flow. This document specifies a Join/Prune attribute that moved. When the old root ITR detects that the root-EID has moved, it
conveys the appropriate receiver RLOC address to the control plane of sends a LISP SMR message to each receiver ETR. The receiver ETRs do
the root xTR. a mapping database lookup to retrieve the RLOC of the new root ITR.
The old root ITR detects that the root-EID has moved when it receives
a Map-Notify from the Map-Server. The transmission of the Map-Notify
is triggered when the new root ITR registers the root-EID
[I-D.portoles-lisp-eid-mobility]. When a receiver ETR determines
that the root ITR has changed it will send a LISP-encapsulated PIM
prune message to the old root XTR and a LISP-encapsulated PIM join
message to the new root XTR.
5.1. Receiver RLOC Attribute Format 5.1. Receiver RLOC Attribute Format
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|F|E|Type=TBD+1 | Length | Addr Family | Receiver RLOC |F|E|Type=TBD+1 | Length | Addr Family | Receiver RLOC
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...
F-bit: The Transitive bit. Specifies whether this attribute is F-bit: The Transitive bit. Specifies whether this attribute is
transitive or non-transitive. MUST be set to zero. This transitive or non-transitive. MUST be set to zero. This
attribute is ALWAYS non-transitive. attribute is ALWAYS non-transitive.
skipping to change at page 6, line 5 skipping to change at page 6, line 27
Type: The Receiver RLOC Attribute type is TBD+1. Type: The Receiver RLOC Attribute type is TBD+1.
Length: The length in octets of the attribute value. MUST be set Length: The length in octets of the attribute value. MUST be set
to the length in octets of the receiver RLOC address plus one to the length in octets of the receiver RLOC address plus one
octet to account for the Address Family field. octet to account for the Address Family field.
Addr Family: The PIM Address Family of the receiver RLOC as defined Addr Family: The PIM Address Family of the receiver RLOC as defined
in [RFC4601]. in [RFC4601].
Receiver RLOC: The RLOC address on which the receiver xTR wishes to Receiver RLOC: The RLOC address on which the receiver ETR wishes to
receiver the unicast-encapsulated flow."> receiver the unicast-encapsulated flow.">
5.2. Using the Receiver RLOC Attribute 5.2. Using the Receiver RLOC Attribute
Hierarchical Join/Prune attribute instances Hierarchical Join/Prune attribute instances
[I-D.ietf-pim-hierarchicaljoinattr] SHOULD be used when the same [I-D.ietf-pim-hierarchicaljoinattr] SHOULD be used when the same
Receiver RLOC attribute is to be applied to all the sources within Receiver RLOC attribute is to be applied to all the sources within
the message or all the sources within a group set. The root xTR MUST the message or all the sources within a group set. The root ITR MUST
accept Transport Attributes in the Upstream Neighbor Encoded-Unicast accept Transport Attributes in the Upstream Neighbor Encoded-Unicast
address, Encoded-Group addresses, and Encoded-Source addresses. address, Encoded-Group addresses, and Encoded-Source addresses.
There MUST NOT be more than one Receiver RLOC Attribute within the There MUST NOT be more than one Receiver RLOC Attribute within the
same encoded address. If an encoded address has more than one same encoded address. If an encoded address has more than one
instance of the attribute, the root xTR MUST discard all affected instance of the attribute, the root ITR MUST discard all affected
Join/Prune sources. Join/Prune sources.
6. Security Considerations 6. Security Considerations
Security of the Join Attribute is only guaranteed by the security of Security of the Join Attribute is only guaranteed by the security of
the PIM packet. The attributes specified herein do not enhance or the PIM packet. The attributes specified herein do not enhance or
diminish the privacy or authenticity of a Join/Prune message. A site diminish the privacy or authenticity of a Join/Prune message. A site
that legitimately or maliciously sends and delivers a Join/Prune that legitimately or maliciously sends and delivers a Join/Prune
message to another site will equally be able to append these and any message to another site will equally be able to append these and any
other attributes it wishes. other attributes it wishes.
skipping to change at page 6, line 47 skipping to change at page 7, line 23
8. Normative References 8. Normative References
[AFI] IANA, , "Address Family Numbers", [AFI] IANA, , "Address Family Numbers",
http://www.iana.org/assignments/address-family-numbers. http://www.iana.org/assignments/address-family-numbers.
[I-D.ietf-pim-hierarchicaljoinattr] [I-D.ietf-pim-hierarchicaljoinattr]
Venaas, S., Arango, J., and I. Kouvelas, "Hierarchical Venaas, S., Arango, J., and I. Kouvelas, "Hierarchical
Join/Prune Attributes", draft-ietf-pim- Join/Prune Attributes", draft-ietf-pim-
hierarchicaljoinattr-08 (work in progress), April 2016. hierarchicaljoinattr-08 (work in progress), April 2016.
[I-D.portoles-lisp-eid-mobility]
Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino,
F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a
Unified Control Plane", draft-portoles-lisp-eid-
mobility-00 (work in progress), April 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, Protocol Specification (Revised)", RFC 4601,
DOI 10.17487/RFC4601, August 2006, DOI 10.17487/RFC4601, August 2006,
<http://www.rfc-editor.org/info/rfc4601>. <http://www.rfc-editor.org/info/rfc4601>.
skipping to change at line 330 skipping to change at page 8, line 35
Email: stig@cisco.com Email: stig@cisco.com
Isidor Kouvelas Isidor Kouvelas
Arista Networks Inc. Arista Networks Inc.
5453 Great America Parkway 5453 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Email: kouvelas@arista.com Email: kouvelas@arista.com
Dino Farinacci
lispers.net
San Jose, CA
USA
Email: farinacci@gmail.com
 End of changes. 24 change blocks. 
54 lines changed or deleted 75 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/