draft-ietf-pim-join-attributes-for-lisp-06.txt   rfc8059.txt 
Network Working Group J. Arango Internet Engineering Task Force (IETF) J. Arango
Internet-Draft S. Venaas Request for Comments: 8059 S. Venaas
Intended status: Experimental Cisco Systems Category: Experimental Cisco Systems
Expires: June 8, 2017 I. Kouvelas ISSN: 2070-1721 I. Kouvelas
Arista Networks Inc. Arista Networks Inc.
D. Farinacci D. Farinacci
lispers.net lispers.net
December 5, 2016 January 2017
PIM Join Attributes for LISP Environments PIM Join Attributes
draft-ietf-pim-join-attributes-for-lisp-06.txt for Locator/ID Separation Protocol (LISP) Environments
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 Locator/ID Separation Protocol
allow the receiver site to select between unicast and multicast (LISP) sites. These attributes allow the receiver site to select
underlay transport and to convey the RLOC (Routing Locator) address between unicast and multicast underlying transport and to convey the
of the receiver ETR (Egress Tunnel Router) to the control plane of RLOC (Routing Locator) address of the receiver ETR (Egress Tunnel
the root ITR (Ingress Tunnel Router). 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 document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for examination, experimental implementation, and
evaluation.
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 This document defines an Experimental Protocol for the Internet
and may be updated, replaced, or obsoleted by other documents at any community. This document is a product of the Internet Engineering
time. It is inappropriate to use Internet-Drafts as reference Task Force (IETF). It represents the consensus of the IETF
material or to cite them other than as "work in progress." community. It has received public review and has been approved for
publication by the Internet Engineering Steering Group (IESG). Not
all documents approved by the IESG are a candidate for any level of
Internet Standard; see Section 2 of RFC 7841.
This Internet-Draft will expire on June 8, 2017. 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/rfc8059.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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
skipping to change at page 2, line 24 skipping to change at page 2, line 33
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
3. PIM Join/Prune Attributes . . . . . . . . . . . . . . . . . . 3 3. PIM Join/Prune Attributes . . . . . . . . . . . . . . . . . . 3
4. The Transport Attribute . . . . . . . . . . . . . . . . . . . 4 4. The Transport Attribute . . . . . . . . . . . . . . . . . . . 4
4.1. Transport Attribute Format . . . . . . . . . . . . . . . 4 4.1. Transport Attribute Format . . . . . . . . . . . . . . . 4
4.2. Using the Transport Attribute . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
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. The term EID is ETR on the receiver site to an ITR on the root site. The term "EID"
short for Endpoint ID. 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
EID,G) state that needs to be established in the root site, but (root-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 receiver's 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. The term "transport" in this document is intentionally somewhat
Currently it is used just to indicate whether multicast or head-end vague. Currently, it is used just to indicate whether multicast or
replication is used. Which means that the outer destination address head-end replication is used; this means that the outer destination
is either a unicast or multicast address. Future documents may address is either a unicast or multicast address. Future documents
specify how other types of delivery, encapsulation or underlay are may specify how other types of delivery, encapsulation, or underlay
used. are used.
Knowledge of the receiver ETR's RLOC address is also essential to the Knowledge of the receiver ETR's RLOC address is essential to the
control plane of the root ITR. The RLOC address determines the control plane of the root ITR. The RLOC address determines the
downstream destination for unicast head-end replication and downstream destination for unicast head-end replication and
identifies the receiver ETR that needs to be notified should the root identifies the receiver ETR that needs to be notified should the root
ITR of the distribution tree move to another site. The root ITR can ITR of the distribution tree move to another site. The root ITR can
change when the source EID is roaming to another LISP site. change when the source EID is roaming to another LISP site.
Service providers may implement uRPF policies requiring that the Service providers may implement unicast reverse path forwarding
outer source address of the LISP-encapsulated Join/Prune message be (uRPF) policies requiring that the outer source address of the LISP-
the address of the receiver ETR's core-facing interface used to encapsulated Join/Prune message be the address of the receiver ETR's
physically transmit the message. However, due to policy and load core-facing interface used to physically transmit the message.
balancing considerations, the outer source address may not be the However, due to policy and load-balancing considerations, the outer
RLOC on which the receiver site wishes to receive a particular flow. source address may not be the RLOC on which the receiver site wishes
This document specifies a Join/Prune attribute that conveys the to receive a particular flow. This document specifies a Join/Prune
appropriate receiver ETR's RLOC address to the control plane of the attribute that conveys the appropriate receiver ETR's RLOC address to
root ITR. the control plane of the root ITR.
This document uses terminology defined in [RFC6830], such as EID, This document uses terminology defined in [RFC6830], such as EID,
RLOC, ITR and ETR. 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,
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 [RFC7887]. This hirarchichal system allows attributes to be in [RFC7887]. This hierarchical system allows attributes to be
conveyed on the Upstream Neighbor Address field, thus enabling the conveyed in the Upstream Neighbor Address field, thus enabling the
efficient application of a single attribute instance to all the efficient application of a single attribute 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 Tunnel Routers (xTRs) do not exchange PIM Hello Messages, and
option is defined to negotiate support for these attributes. Systems hence no Hello option is defined to negotiate support for these
that support unicast head-end replication are assumed to support attributes. Systems that support unicast head-end replication are
these attributes. assumed to support 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
multicast connectivity will want to leverage multicast replication. multicast connectivity will want to leverage multicast replication.
However, not all receiver sites can be expected to have multicast However, not all receiver sites can be expected to have multicast
connectivity. It is thus desirable that root sites be prepared to connectivity. It is thus desirable that root sites be prepared to
support (root-EID,G) state with a mixture of multicast and unicast support (root-EID,G) state with a mixture of multicast and unicast
output state. This document specifies a Join/Prune attribute that output state. This document specifies a Join/Prune attribute that
allows the receiver to select the desired underlying transport. allows the receiver to select the desired underlying transport.
4.1. Transport Attribute Format 4.1. Transport Attribute Format
0 1 2 0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|F|E| Type = TBD| Length = 1 | Transport | |F|E| Type = 5 | Length = 1 | Transport |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
F-bit: The Transitive bit. Specifies whether the attribute is F bit: The Transitive bit. Specifies whether the 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.
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 5.
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 zero for
multicast. Set to 1 for unicast. The values from 2 to 255 may be multicast. Set to 1 for unicast. The values from 2 to 255 may be
assigned in the future. assigned in the future.
4.2. Using the Transport Attribute 4.2. Using the Transport Attribute
Hierarchical Join/Prune attribute instances [RFC7887] SHOULD be used Hierarchical Join/Prune attribute instances [RFC7887] SHOULD be used
when the same Transport Attribute is to be applied to all the sources when the same Transport Attribute is to be applied to all the sources
within the Join/Prune message or all the sources within a group set. within the Join/Prune message or all the sources within a group set.
The root ITR MUST accept Transport Attributes in the Upstream The root ITR MUST accept Transport Attributes in the Upstream
Neighbor Encoded-Unicast address, Encoded-Group addresses, and Neighbor Encoded-Unicast address, Encoded-Group addresses, and
Encoded-Source addresses. Encoded-Source 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. The root ITR MUST also discard all affected Join/Prune sources. The root ITR MUST also discard all affected Join/Prune
sources if the transport attribute value is unknown. 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 outgoing interface list ("oif-list") entry for the
ETR and its corresponding RLOC address. This allows the root ITR to receiver ETR and its corresponding RLOC address. This allows the
perform unicast LISP-encapsulation of multicast data packets to each root ITR to perform unicast LISP-encapsulation of multicast data
and every receiver ETR that has requested unicast head-end packets to each and every receiver ETR that has requested unicast
replication. head-end 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 the LISP-encapsulated Join/Prune message. However, receiver ETRs
subject to uRPF checks by the network providers on each core-facing are subject to uRPF checks by the network providers on each core-
interface. The outer source address must therefore be the RLOC of facing interface. The outer source address must therefore be the
the core-facing interface used to physically transmit the LISP- RLOC of the core-facing interface used to physically transmit the
encapsulated Join/Prune message. Due to policy and load balancing LISP-encapsulated Join/Prune message. Due to policy and load-
considerations, that may not be the RLOC on which the receiver site balancing considerations, that may not be the RLOC on which the
wishes to receive a particular flow. This document specifies a Join/ receiver site wishes to receive a particular flow. This document
Prune attribute that conveys the appropriate receiver RLOC address to specifies a Join/Prune attribute that conveys the appropriate
the PIM control plane of the root ITR. receiver RLOC address to 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
transport. When the root-EID moves to a new root ITR in a different transport. When the root-EID moves to a new root ITR in a different
LISP site, the receiver ETRs do not know the root-EID has moved and LISP site, the receiver ETRs do not know the root-EID has moved and
therefore do not know the RLOC of the new root ITR. This is true for therefore do not know the RLOC of the new root ITR. This is true for
both unicast and multicast transport modes. The new root ITR does both unicast and multicast transport modes. The new root ITR does
not have any receiver ETR state. Therefore, it is the responsability not have any receiver ETR state. Therefore, it is the responsibility
of the old root ITR to inform the receiver ETRs that the root-EID has of the old root ITR to inform the receiver ETRs that the root-EID has
moved. When the old root ITR detects that the root-EID has moved, it moved. When the old root ITR detects that the root-EID has moved, it
sends a LISP SMR message to each receiver ETR. The receiver ETRs do sends a LISP Solicit-Map-Request (SMR) message to each receiver ETR.
a mapping database lookup to retrieve the RLOC of the new root ITR. The receiver ETRs do a mapping database lookup to retrieve the RLOC
of the new root ITR. The old root ITR detects that the root-EID has
The old root ITR detects that the root-EID has moved when it receives moved when it receives a Map-Notify from the Map-Server. The
a Map-Notify from the Map-Server. The transmission of the Map-Notify transmission of the Map-Notify is triggered when the new root ITR
is triggered when the new root ITR registers the root-EID registers the root-EID [EID-MOBILITY]. When a receiver ETR
[I-D.portoles-lisp-eid-mobility]. When a receiver ETR determines determines that the root ITR has changed, it will send a LISP-
that the root ITR has changed it will send a LISP-encapsulated PIM encapsulated PIM prune message to the old root xTR and a LISP-
prune message to the old root XTR and a LISP-encapsulated PIM join encapsulated PIM join message to the new root xTR.
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 = 6 | 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.
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 Receiver RLOC Attribute type is TBD+1. Type: The Receiver RLOC Attribute type is 6.
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 1 octet
octet to account for the Address Family field. 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 [RFC7761]. 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 [RFC7887] SHOULD be used Hierarchical Join/Prune attribute instances [RFC7887] SHOULD be used
when the same Receiver RLOC attribute is to be applied to all the when the same Receiver RLOC Attribute is to be applied to all the
sources within the message or all the sources within a group set. sources within the message or all the sources within a group set.
The root ITR MUST accept Transport Attributes in the Upstream The root ITR MUST accept Transport Attributes in the Upstream
Neighbor Encoded-Unicast address, Encoded-Group addresses, and Neighbor Encoded-Unicast 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. The root ITR MUST also discard all affected Join/Prune sources. The root ITR MUST also discard all affected
Join/Prune sources if the address family is unknown, or the address Join/Prune sources if the address family is unknown or the address
length is incorrect for the specified address family. length is incorrect for the specified address family.
6. Security Considerations 6. Security Considerations
Security of Join/Prune Attributes is only guaranteed by the security Security of Join/Prune attributes is only guaranteed by the security
of 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. See [RFC5384] for general security other attributes it wishes. See [RFC5384] for general security
considerations for Join/Prune attributes. 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 have been assigned: value 5
is being requested for the Transport Attribute. Type 6 is being for the Transport Attribute and value 6 for the Receiver RLOC
requested for the Receiver RLOC Attribute. Attribute.
A registry needs to be created for the Join/Prune Transport The "PIM Join/Prune Transport Types" registry has been created for
attribute. The name of the registry should be PIM Join/Prune the Join/Prune Transport attribute. The registration policy is IETF
Transport Types. The registration policy is IETF Review, and the Review [RFC5226], and the values are in the range 0-255. This
values are in the range 0-255. This document assigns the value 0 for document assigns value 0 for multicast and value 1 for unicast.
multicast and 1 for unicast.
8. References 8. References
8.1. Normative References 8.1. Normative References
[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>.
skipping to change at page 8, line 22 skipping to change at page 8, line 41
Multicast - Sparse Mode (PIM-SM): Protocol Specification Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <http://www.rfc-editor.org/info/rfc7761>. 2016, <http://www.rfc-editor.org/info/rfc7761>.
[RFC7887] Venaas, S., Arango, J., and I. Kouvelas, "Hierarchical [RFC7887] Venaas, S., Arango, J., and I. Kouvelas, "Hierarchical
Join/Prune Attributes", RFC 7887, DOI 10.17487/RFC7887, Join/Prune Attributes", RFC 7887, DOI 10.17487/RFC7887,
June 2016, <http://www.rfc-editor.org/info/rfc7887>. June 2016, <http://www.rfc-editor.org/info/rfc7887>.
8.2. Informative References 8.2. Informative References
[I-D.portoles-lisp-eid-mobility] [EID-MOBILITY]
Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino, Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino,
F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a
Unified Control Plane", draft-portoles-lisp-eid- Unified Control Plane", Work in Progress, draft-portoles-
mobility-01 (work in progress), October 2016. lisp-eid-mobility-01, October 2016.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
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 United States of America
Email: jearango@cisco.com Email: jearango@cisco.com
Stig Venaas Stig Venaas
Cisco Systems Cisco Systems
170 Tasman Drive 170 Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA United States of America
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 United States of America
Email: kouvelas@arista.com Email: kouvelas@arista.com
Dino Farinacci Dino Farinacci
lispers.net lispers.net
San Jose, CA San Jose, CA
USA United States of America
Email: farinacci@gmail.com Email: farinacci@gmail.com
 End of changes. 47 change blocks. 
121 lines changed or deleted 126 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/