draft-ietf-pim-join-attributes-for-lisp-02.txt   draft-ietf-pim-join-attributes-for-lisp-03.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: January 7, 2016 I. Kouvelas Expires: November 21, 2016 I. Kouvelas
Arista Networks Inc. Arista Networks Inc.
July 6, 2015 May 20, 2016
PIM Join Attributes for LISP Environments PIM Join Attributes for LISP Environments
draft-ietf-pim-join-attributes-for-lisp-02.txt draft-ietf-pim-join-attributes-for-lisp-03.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 transport and to convey the receiver RLOC address to the control
plane of the root xTR. plane of the root xTR.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 January 7, 2016. This Internet-Draft will expire on November 21, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
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 3, line 32 skipping to change at page 3, line 32
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.venaas-pim-hierarchicaljoinattr]. This hirarchichal system in [I-D.ietf-pim-hierarchicaljoinattr]. This hirarchichal system
allows attributes to be conveyed on the Upstream Neighbor Address allows attributes to be conveyed on the Upstream Neighbor Address
field, thus enabling the efficient application of a single attribute field, thus enabling the efficient application of a single attribute
instance to all the sources in the Join/Prune message. instance to all the 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
skipping to change at page 4, line 10 skipping to change at page 4, line 10
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 = 5 | Length = 1 | Transport | |F|E| Type = TBD| 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 5. 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.
4.2. Using the Transport Attribute 4.2. Using the Transport Attribute
Hierarchical Join/Prune attribute instances Hierarchical Join/Prune attribute instances
[I-D.venaas-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 xTR 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 xTR MUST discard all affected Join/Prune
sources. sources.
skipping to change at page 5, line 31 skipping to change at page 5, line 31
not be the RLOC on which the receiver site wishes to receive a not be the RLOC on which the receiver site wishes to receive a
particular flow. This document specifies a Join/Prune attribute that particular flow. This document specifies a Join/Prune attribute that
conveys the appropriate receiver RLOC address to the control plane of conveys the appropriate receiver RLOC address to the control plane of
the root xTR. the 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 = 6 | 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.
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 6. 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 xTR 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.venaas-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 xTR 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 xTR MUST discard all affected
Join/Prune sources. Join/Prune sources.
skipping to change at page 6, line 40 skipping to change at page 6, line 40
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 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.venaas-pim-hierarchicaljoinattr] [I-D.ietf-pim-hierarchicaljoinattr]
Venaas, S., Kouvelas, I., and J. Arango, "Hierarchical Venaas, S., Arango, J., and I. Kouvelas, "Hierarchical
Join/Prune Attributes", draft-venaas-pim- Join/Prune Attributes", draft-ietf-pim-
hierarchicaljoinattr-00 (work in progress), February 2013. hierarchicaljoinattr-08 (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, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<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, August 2006. 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", RFC Independent Multicast (PIM) Join Attribute Format",
5384, November 2008. RFC 5384, DOI 10.17487/RFC5384, November 2008,
<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, January Locator/ID Separation Protocol (LISP)", RFC 6830,
2013. DOI 10.17487/RFC6830, January 2013,
<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, January 2013. Environments", RFC 6831, DOI 10.17487/RFC6831, January
2013, <http://www.rfc-editor.org/info/rfc6831>.
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. 19 change blocks. 
24 lines changed or deleted 31 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/