draft-ietf-pim-join-attributes-for-lisp-04.txt   draft-ietf-pim-join-attributes-for-lisp-05.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: December 16, 2016 I. Kouvelas Expires: April 13, 2017 I. Kouvelas
Arista Networks Inc. Arista Networks Inc.
D. Farinacci D. Farinacci
lispers.net lispers.net
June 14, 2016 October 10, 2016
PIM Join Attributes for LISP Environments PIM Join Attributes for LISP Environments
draft-ietf-pim-join-attributes-for-lisp-04.txt draft-ietf-pim-join-attributes-for-lisp-05.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 receiver ETR's RLOC address to
the control plane of the root ITR. the control plane of the root ITR.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 December 16, 2016. This Internet-Draft will expire on April 13, 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 23 skipping to change at page 2, line 23
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 ETR RLOC Attribute . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Normative References . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
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.
skipping to change at page 3, line 7 skipping to change at page 3, line 8
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.
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. It determines the downstream
destination for unicast head-end replication and identifies the destination for unicast head-end replication and identifies the
receiver ETR that needs to be notified should the root of the receiver ETR that needs to be notified should the root of the
distribution tree move to another site. distribution tree move to another 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.
2. Requirements Notation 2. Requirements Notation
skipping to change at page 3, line 35 skipping to change at page 3, line 36
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,
can carry multiple type-length-value (TLV) attributes. These can carry multiple type-length-value (TLV) attributes. These
attributes apply to the individual Join/Prune sources on which they attributes apply to the individual Join/Prune sources on which they
are stored. are stored.
The attributes defined in this document conform to the format of the The attributes defined in this document conform to the format of the
encoding type defined in [RFC5384]. The attributes would typically encoding type defined in [RFC5384]. The attributes would typically
be the same for all the sources in the Join/Prune message. Hence we be the same for all the sources in the Join/Prune message. Hence we
RECOMMEND using the hierarchical Join/Prune attribute scheme defined RECOMMEND using the hierarchical Join/Prune attribute scheme defined
in [I-D.ietf-pim-hierarchicaljoinattr]. This hirarchichal system in [RFC7887]. This hirarchichal system allows attributes to be
allows attributes to be conveyed on the Upstream Neighbor Address conveyed on the Upstream Neighbor Address field, thus enabling the
field, thus enabling the efficient application of a single attribute efficient application of a single attribute instance to all the
instance to all the sources in the Join/Prune message. sources in the Join/Prune message.
LISP xTRs do not exchange PIM Hello Messages and hence no Hello LISP xTRs do not exchange PIM Hello Messages and hence no Hello
option is defined to negotiate support for these attributes. Systems option is defined to negotiate support for these attributes. Systems
that support unicast head-end replication are assumed to support that support unicast head-end replication are assumed to support
these attributes. these attributes.
4. The Transport Attribute 4. The Transport Attribute
It is essential that a mechanism be provided by which the desired It is essential that a mechanism be provided by which the desired
transport can be conveyed by receiver sites. Root sites with transport can be conveyed by receiver sites. Root sites with
skipping to change at page 4, line 30 skipping to change at page 4, line 31
E-bit: End-of-Attributes bit. Specifies whether this attribute is E-bit: End-of-Attributes bit. Specifies whether this attribute is
the last. Set to zero if there are more attributes. Set to 1 if the last. Set to zero if there are more attributes. Set to 1 if
this is the last attribute. this is the last attribute.
Type: The Transport Attribute type is TBD. Type: The Transport Attribute type is TBD.
Length: The length of the Transport Attribute value. MUST be set Length: The length of the Transport Attribute value. MUST be set
to 1. to 1.
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. The values from 2 to 255 may be
assigned in the future.
4.2. Using the Transport Attribute 4.2. Using the Transport Attribute
Hierarchical Join/Prune attribute instances Hierarchical Join/Prune attribute instances [RFC7887] SHOULD be used
[I-D.ietf-pim-hierarchicaljoinattr] SHOULD be used when the same when the same Transport Attribute is to be applied to all the sources
Transport Attribute is to be applied to all the sources within the within the Join/Prune message or all the sources within a group set.
Join/Prune message or all the sources within a group set. The root The root ITR MUST accept Transport Attributes in the Upstream
ITR MUST accept Transport Attributes in the Upstream Neighbor Neighbor Encoded-Unicast address, Encoded-Group addresses, and
Encoded-Unicast address, Encoded-Group addresses, and Encoded-Source 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 ITR MUST discard all affected Join/Prune the attribute, the root ITR MUST discard all affected Join/Prune
sources. sources. The root ITR MUST also discard all affected Join/Prune
sources if the transport attribute value is unknown.
5. Receiver ETR RLOC Attribute 5. Receiver ETR RLOC Attribute
When a receiver ETR requests unicast head-end replication for a given When a receiver ETR requests unicast head-end replication for a given
(root-EID,G) entry, the PIM control plane of the root ITR must (root-EID,G) entry, the PIM control plane of the root ITR must
maintain an output interface list ("oif-list") entry for the receiver maintain an output interface list ("oif-list") entry for the receiver
ETR and its corresponding RLOC address. This allows the root ITR to ETR and its corresponding RLOC address. This allows the root ITR to
perform unicast LISP-encapsulation of multicast data packets to each perform unicast LISP-encapsulation of multicast data packets to each
and every receiver ETR that has requested unicast head-end and every receiver ETR that has requested unicast head-end
replication. replication.
The PIM control plane of the root ITR could potentially determine the The PIM control plane of the root ITR could potentially determine the
RLOC address of the receiver ETR from the outer source address field RLOC address of the receiver ETR from the outer source address field
of LISP-encapsulated Join/Prune message. However, receiver ETRs are of LISP-encapsulated Join/Prune message. However, receiver ETRs are
subject to URPF checks by the network providers on each core-facing subject to uRPF checks by the network providers on each core-facing
interface. The outer source address must therefore be the RLOC of interface. The outer source address must therefore be the RLOC of
the core-facing interface used to physically transmit the LISP- the core-facing interface used to physically transmit the LISP-
encapsulated Join/Prune message. Due to policy and load balancing encapsulated Join/Prune message. Due to policy and load balancing
considerations, that may not be the RLOC on which the receiver site considerations, that may not be the RLOC on which the receiver site
wishes to receive a particular flow. This document specifies a Join/ wishes to receive a particular flow. This document specifies a Join/
Prune attribute that conveys the appropriate receiver RLOC address to Prune attribute that conveys the appropriate receiver RLOC address to
the PIM control plane of the root ITR. the PIM control plane of the root ITR.
To support root-EID mobility, receiver ETRs must also be tracked by To support root-EID mobility, receiver ETRs must also be tracked by
the LISP control plane of the root ITR, regardless of the underlying the LISP control plane of the root ITR, regardless of the underlying
skipping to change at page 6, line 25 skipping to change at page 6, line 25
the last. Set to zero if there are more attributes. Set to 1 if the last. Set to zero if there are more attributes. Set to 1 if
this is the last attribute. this is the last attribute.
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 [RFC7761].
Receiver RLOC: The RLOC address on which the receiver ETR 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 [RFC7887] SHOULD be used
[I-D.ietf-pim-hierarchicaljoinattr] SHOULD be used when the same when the same Receiver RLOC attribute is to be applied to all the
Receiver RLOC attribute is to be applied to all the sources within sources within the message or all the sources within a group set.
the message or all the sources within a group set. The root ITR MUST The root ITR MUST accept Transport Attributes in the Upstream
accept Transport Attributes in the Upstream Neighbor Encoded-Unicast Neighbor Encoded-Unicast address, Encoded-Group addresses, and
address, Encoded-Group addresses, and Encoded-Source addresses. 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 ITR MUST discard all affected instance of the attribute, the root ITR MUST discard all affected
Join/Prune sources. Join/Prune sources. The root ITR MUST also discard all affected
Join/Prune sources if the address family is unknown, or the address
length is incorrect for the specified address family.
6. Security Considerations 6. Security Considerations
Security of the Join Attribute is only guaranteed by the security of Security of Join/Prune Attributes is only guaranteed by the security
the PIM packet. The attributes specified herein do not enhance or of 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. See [RFC5384] for general security
considerations for Join/Prune attributes.
7. IANA Considerations 7. IANA Considerations
Two new PIM Join/Prune attribute types need to be assigned. Type 5 Two new PIM Join/Prune attribute types need to be assigned. Type 5
is being requested for the Transport Attribute. Type 6 is being is being requested for the Transport Attribute. Type 6 is being
requested for the Receiver RLOC Attribute. requested for the Receiver RLOC Attribute.
8. Normative References A registry needs to be created for the Join/Prune Transport
attribute. The name of the registry should be PIM Join/Prune
[AFI] IANA, , "Address Family Numbers", Transport Types. The registration policy is IETF Review, and the
http://www.iana.org/assignments/address-family-numbers. values are in the range 0-255. This document assigns the value 0 for
multicast and 1 for unicast.
[I-D.ietf-pim-hierarchicaljoinattr] 8. References
Venaas, S., Arango, J., and I. Kouvelas, "Hierarchical
Join/Prune Attributes", draft-ietf-pim-
hierarchicaljoinattr-08 (work in progress), April 2016.
[I-D.portoles-lisp-eid-mobility] 8.1. Normative References
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,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601,
DOI 10.17487/RFC4601, August 2006,
<http://www.rfc-editor.org/info/rfc4601>.
[RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
Independent Multicast (PIM) Join Attribute Format", Independent Multicast (PIM) Join Attribute Format",
RFC 5384, DOI 10.17487/RFC5384, November 2008, RFC 5384, DOI 10.17487/RFC5384, November 2008,
<http://www.rfc-editor.org/info/rfc5384>. <http://www.rfc-editor.org/info/rfc5384>.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", RFC 6830, Locator/ID Separation Protocol (LISP)", RFC 6830,
DOI 10.17487/RFC6830, January 2013, DOI 10.17487/RFC6830, January 2013,
<http://www.rfc-editor.org/info/rfc6830>. <http://www.rfc-editor.org/info/rfc6830>.
[RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The [RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The
Locator/ID Separation Protocol (LISP) for Multicast Locator/ID Separation Protocol (LISP) for Multicast
Environments", RFC 6831, DOI 10.17487/RFC6831, January Environments", RFC 6831, DOI 10.17487/RFC6831, January
2013, <http://www.rfc-editor.org/info/rfc6831>. 2013, <http://www.rfc-editor.org/info/rfc6831>.
[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <http://www.rfc-editor.org/info/rfc7761>.
[RFC7887] Venaas, S., Arango, J., and I. Kouvelas, "Hierarchical
Join/Prune Attributes", RFC 7887, DOI 10.17487/RFC7887,
June 2016, <http://www.rfc-editor.org/info/rfc7887>.
8.2. Informative References
[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-01 (work in progress), October 2016.
Authors' Addresses Authors' Addresses
Jesus Arango Jesus Arango
Cisco Systems Cisco Systems
170 Tasman Drive 170 Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: jearango@cisco.com Email: jearango@cisco.com
 End of changes. 22 change blocks. 
51 lines changed or deleted 63 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/