draft-ietf-bess-pta-flags-02.txt   draft-ietf-bess-pta-flags-03.txt 
BESS Working Group E. Rosen BESS Working Group E. Rosen
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Updates: 6514 (if approved) T. Morin Updates: 6514 (if approved) T. Morin
Intended status: Standards Track Orange Intended status: Standards Track Orange
Expires: August 5, 2016 February 2, 2016 Expires: November 4, 2016 May 3, 2016
Registry and Extensions for Registry and Extensions for
P-Multicast Service Interface Tunnel Attribute Flags P-Multicast Service Interface Tunnel Attribute Flags
draft-ietf-bess-pta-flags-02.txt draft-ietf-bess-pta-flags-03.txt
Abstract Abstract
The BGP-based control procedures for Multicast Virtual Private The BGP-based control procedures for Multicast Virtual Private
Networks make use of a BGP attribute known as the "P-Multicast Networks make use of a BGP attribute known as the "P-Multicast
Service Interface (PMSI) Tunnel" attribute. The attribute contains a Service Interface (PMSI) Tunnel" attribute. The attribute contains a
one-octet "Flags" field. The purpose of this document is to one-octet "Flags" field. The purpose of this document is to
establish an IANA registry for the assignment of the bits in this establish an IANA registry for the assignment of the bits in this
field. Since the Flags field contains only eight bits, this document field. Since the Flags field contains only eight bits, this document
also defines a new BGP Extended Community, "Additional PMSI Tunnel also defines a new BGP Extended Community, "Additional PMSI Tunnel
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 August 5, 2016. This Internet-Draft will expire on November 4, 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
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
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. Extending the PMSI Tunnel Attribute Flags Field . . . . . . . 2 2. Extending the PMSI Tunnel Attribute Flags Field . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. Normative References . . . . . . . . . . . . . . . . . . . . 5 6. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
A BGP attribute known as the "P-Multicast Service Interface (PMSI) A BGP attribute known as the "P-Multicast Service Interface (PMSI)
Tunnel" attribute is defined in [RFC6514]. This attribute contains a Tunnel" attribute is defined in [RFC6514]. This attribute contains a
one-octet of "Flags" field. Only one flag is defined in that RFC, one-octet "Flags" field. Only one flag is defined in that RFC, but
but there is now a need to define additional flags. However, that there is now a need to define additional flags. However, that RFC
RFC did not create an IANA registry for the assignment of bits in the did not create an IANA registry for the assignment of bits in the
Flags field. This document creates a registry for that purpose. In "Flags" field. This document creates a registry for that purpose.
addition, there may be a need to define more than eight flags. In addition, there may be a need to define more than eight flags.
Therefore this document defines a new BGP Extended Community, Therefore this document defines a new BGP Extended Community,
"Additional PMSI Tunnel Attribute Flags", that can be used to carry "Additional PMSI Tunnel Attribute Flags", that can be used to carry
additional flags for the PMSI Tunnel attribute. A registry is also additional flags for the PMSI Tunnel attribute. A registry is also
created for this Extended Community, allowing IANA to assign bits created for this Extended Community, allowing IANA to assign flag
from the Extended Community's six-octet value field. bits from the Extended Community's six-octet value field.
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].
2. Extending the PMSI Tunnel Attribute Flags Field 2. Extending the PMSI Tunnel Attribute Flags Field
In [RFC6514], only a single octet in the PMSI Tunnel attribute is In [RFC6514], only a single octet in the "PMSI Tunnel" attribute is
defined to carry bit flags. This allows eight flags, which is defined to carry bit flags. This allows eight flags, which is
unlikely to be sufficient for all future applications. unlikely to be sufficient for all future applications.
This document defines a new Transitive Opaque Extended Community, This document defines a new Transitive Opaque Extended Community
"Additional PMSI Tunnel Attribute Flags". It also defines a new bit ([RFC4360], [RFC7153]), "Additional PMSI Tunnel Attribute Flags". It
flag in the PMSI Tunnel Attribute flags field, called the "Extension" also defines a new bit flag in the "PMSI Tunnel" attribute Flags
flag. field, called the "Extension" flag.
The Additional PMSI Tunnel Attribute Flags Extended Community MUST The "Additional PMSI Tunnel Attribute Flags" Extended Community MUST
NOT be carried by a given BGP UPDATE message unless the following NOT be carried by a given BGP UPDATE message unless the following
conditions both hold: conditions both hold:
o the given BGP UPDATE message is also carrying a PMSI Tunnel o the given BGP UPDATE message is also carrying a "PMSI Tunnel"
attribute, and attribute, and
o the Extension flag of that PMSI Tunnel attribute's Flags field is o the "Extension" flag of that "PMSI Tunnel" attribute's "Flags"
set. field is set.
If a given BGP UPDATE message is carrying a PMSI Tunnel attribute, The six-octet value field of the "Additional PMSI Tunnel Attribute
but is not carrying an Additional PMSI Tunnel Attribute Flags Flags" Extended Community is considered to be a string of 48 bit
Extended Community, then the Extension flag in the PMSI Tunnel flags. As shown in Figure 1, the leftmost bit (the most significant
attribute MUST be clear. bit of the most significant octet) is bit 0, and the rightmost bit
(the least significant bit of the least significant octet) is bit 47.
If a BGP speaker receives an UPDATE message that contains an 0 1 2 3
Additional PMSI Tunnel Attribute Flags Extended Community, but either 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
(a) that UPDATE message does not contain a PMSI Tunnel attribute, or +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(b) the Extension flag of the PMSI Tunnel attribute is not set, then | | | | |
the Extended Community SHOULD be removed and SHOULD NOT be +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
redistributed. The BGP UPDATE message MUST be processed (and if
necessary, redistributed) as if the Extended Community had not been
present.
Suppose a BGP speaker receives an UPDATE message that contains a PMSI 3 4
Tunnel attribute, but does not contain an Additional PMSI Tunnel 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
Attribute Flags Extended Community. If the Extension flag of the +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
PMSI Tunnel attribute is set, then the "treat-as-withdraw" procedure | | |
of [RFC7606] MUST be applied. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Value Field of the Additional PMSI Tunnel Attribute Flags
Extended Community
A BGP speaker MUST NOT attach more than one "Additional PMSI Tunnel
Attribute Flags" Extended Community to a given BGP UPDATE. If a
given BGP UPDATE already contains an "Additional PMSI Tunnel
Attribute Flags" Extended Community, a BGP speaker MUST NOT attach
any additional such Extended Communities.
If a BGP speaker receives a BGP UPDATE with more than one "Additional
PMSI Tunnel Attribute Flags" Extended Communities attached, only the
flag settings in first occurrence of the Extended Community are
significant. Flag settings in subsequent occurrences of the Extended
Community MUST be ignored. When propagating the UPDATE, all
instances of the Extended Community other than the first SHOULD be
removed.
Suppose a BGP speaker receives an UPDATE message that contains a
"PMSI Tunnel" attribute, but does not contain an "Additional PMSI
Tunnel Attribute Flags" Extended Community. If the "Extension" flag
of the "PMSI Tunnel" attribute is set, the UPDATE is considered to be
malformed, and the "treat-as-withdraw" procedure of [RFC7606] MUST be
applied.
If a BGP speaker receives an UPDATE message that contains one or more
"Additional PMSI Tunnel Attribute Flags" Extended Communities, but
either (a) that UPDATE message does not contain a PMSI Tunnel
attribute, or (b) the Extension flag of the PMSI Tunnel attribute is
not set, then the Extended Community(ies) SHOULD be removed and
SHOULD NOT be redistributed. The BGP UPDATE message MUST be
processed (and if necessary, redistributed) as if the Extended
Community(ies) had not been present.
A BGP speaker that supports the current document, but does not
recognize a particular flag (either in the" PMSI Tunnel" attribute
"Flags" field or in the "Additional PMSI Tunnel Attribute Flags"
Extended Community) MUST simply ignore that flag. If the BGP speaker
propagates either the PMSI Tunnel attribute or the "Additional PMSI
Tunnel Attribute Flags" Extended Community or both along with the
UPDATE message, it SHOULD leave the setting of the flag unchanged.
It is possible that a particular application will require all members
of a particular set of BGP speakers to support a particular flag.
How it is determined whether all such BGP speakers support that flag
is outside the scope of this document.
In some situations, a BGP speaker may need to modify or replace the
"PMSI Tunnel" attribute before propagating an UPDATE. If the
"Extension" flag of the "PMSI Tunnel" attribute was set before the
attribute is modified or replaced, but that flag is no longer set
after the attribute is modified or replaced, any "Additional PMSI
Tunnel Attribute Flags" Extended Communities MUST be removed before
the UPDATE is propagated. If the PMSI Tunnel attribute is removed
entirely before an UPDATE is propagated, the "Additional PMSI Tunnel
Attribute Flags" Extended Communities (if any) MUST also be removed.
3. IANA Considerations 3. IANA Considerations
IANA is requested to create a new registry called "P-Multicast IANA is requested to create a new registry called "P-Multicast
Service Interface (PMSI) Tunnel Attribute Flags" in the "Border Service Interface (PMSI) Tunnel Attribute Flags" in the "Border
Gateway Protocol (BGP) Parameters" registry. Gateway Protocol (BGP) Parameters" registry.
Per [RFC6514] section 5, a PMSI Tunnel Attribute contains a "Flags" Per [RFC6514] section 5, a "PMSI Tunnel" attribute contains a "Flags"
octet. The Flags field is a single octet, with bits numbered, left- octet. The Flags field is a single octet, with bits numbered, left-
to-right, from 0 to 7. IANA is requested to initialize the registry to-right, from 0 to 7. IANA is requested to initialize the registry
as follows: as follows:
Bit Position Description Reference Bit Position Description Reference
(left to right) (left to right)
0 unassigned 0 unassigned
1 Extension This document 1 Extension This document
2 unassigned 2 unassigned
3 unassigned 3 unassigned
skipping to change at page 4, line 28 skipping to change at page 5, line 28
The registration procedure for this registry is Standards Action. The registration procedure for this registry is Standards Action.
IANA is also requested to assign a codepoint, from the "First Come, IANA is also requested to assign a codepoint, from the "First Come,
First Served" range of the Transitive Opaque Extended Community Sub- First Served" range of the Transitive Opaque Extended Community Sub-
Types registry, for "Additional PMSI Tunnel Attribute Flags". Types registry, for "Additional PMSI Tunnel Attribute Flags".
[TO BE REMOVED: This registration should take place at the following [TO BE REMOVED: This registration should take place at the following
location: http://www.iana.org/assignments/bgp-extended-communities location: http://www.iana.org/assignments/bgp-extended-communities
/bgp-extended-communities.xhtml#trans-opaque] /bgp-extended-communities.xhtml#trans-opaque]
IANA is further requested to establish a registry for the bit flags IANA is further requested to establish a registry for the bit flags
carried in the Additional PMSI Tunnel Attribute Flags extended carried in the "Additional PMSI Tunnel Attribute Flags" Extended
community. The bits shall be numbered 0-47, with 0 being the most Community. The bits shall be numbered 0-47, with 0 being the most
significant bit and 47 being the least significant bit. The significant bit and 47 being the least significant bit. The
registration policy for this registry shall be "Standards Action". registration policy for this registry shall be "Standards Action".
[TO BE REMOVED: The creation of the registry should take place at the [TO BE REMOVED: The creation of the registry should take place at the
following location: http://www.iana.org/assignments/bgp-extended- following location: http://www.iana.org/assignments/bgp-extended-
communities/bgp-extended-communities.xhtml] communities/bgp-extended-communities.xhtml]
The initial registry should be as follows: The initial registry should be as follows:
Bit Flag Name Reference Bit Flag Name Reference
0-47 unassigned 0-47 unassigned
Additional PMSI Tunnel Attribute Flags Additional PMSI Tunnel Attribute Flags
4. Acknowledgments 4. Acknowledgments
The authors wish to thank Martin Vigoureux for his review of this The authors wish to thank Martin Vigoureux for his review of this
document. document. We also thank Christian Huitema and Alexey Melnikov for
their review and comments.
5. Security Considerations 5. Security Considerations
This document establishes an IANA registry, and defines a new This document establishes an IANA registry, and defines a new
transitive opaque Extended Community. Transitive Opaque Extended Community ([RFC4360], [RFC7153]).
Establishment of an IANA registry does not raise any security Establishment of an IANA registry does not raise any security
considerations. considerations.
While the document defines a new Extended Community for carrying bit While this document defines a new Extended Community for carrying bit
flags, it does not define any of the bit flags in that Extended flags, it does not define any of the bit flags in that Extended
Community. Therefore no security considerations are raised. Community. Therefore no security considerations are raised.
This document defines a new flag, the "Extension" flag, in the "PMSI
Tunnel" attribute. If a particular UPDATE contains "PMSI Tunnel"
attribute with this flag set, but the UPDATE does not contain an
"Additional PMSI Tunnel Attribute Flags" Extended Community, then the
UPDATE is considered to be malformed, and the "treat-as-withdraw"
procedure of [RFC7606] is invoked. Thus one can cause an UPDATE to
be treated as a withdrawal by incorrectly setting this bit.
6. Normative References 6. 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>.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
February 2006, <http://www.rfc-editor.org/info/rfc4360>.
[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
Encodings and Procedures for Multicast in MPLS/BGP IP Encodings and Procedures for Multicast in MPLS/BGP IP
VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
<http://www.rfc-editor.org/info/rfc6514>. <http://www.rfc-editor.org/info/rfc6514>.
[RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP
Extended Communities", RFC 7153, DOI 10.17487/RFC7153,
March 2014, <http://www.rfc-editor.org/info/rfc7153>.
[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
Patel, "Revised Error Handling for BGP UPDATE Messages", Patel, "Revised Error Handling for BGP UPDATE Messages",
RFC 7606, DOI 10.17487/RFC7606, August 2015, RFC 7606, DOI 10.17487/RFC7606, August 2015,
<http://www.rfc-editor.org/info/rfc7606>. <http://www.rfc-editor.org/info/rfc7606>.
Authors' Addresses Authors' Addresses
Eric C. Rosen Eric C. Rosen
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
 End of changes. 22 change blocks. 
47 lines changed or deleted 118 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/