draft-ietf-bess-pta-flags-01.txt   draft-ietf-bess-pta-flags-02.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: February 7, 2016 August 6, 2015 Expires: August 5, 2016 February 2, 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-01.txt draft-ietf-bess-pta-flags-02.txt
Abstract Abstract
RFC6514 defines the "P-Multicast Service Interface Tunnel (PMSI The BGP-based control procedures for Multicast Virtual Private
Tunnel) attribute". This attribute contains an octet of "flags". Networks make use of a BGP attribute known as the "P-Multicast
Only one flag is defined in that RFC, but there is now a need to Service Interface (PMSI) Tunnel" attribute. The attribute contains a
define additional flags. Since the RFC did not create a registry for one-octet "Flags" field. The purpose of this document is to
the assignment of flag bits, this document updates the RFC by establish an IANA registry for the assignment of the bits in this
creating a registry for that purpose. This document also defines a field. Since the Flags field contains only eight bits, this document
new BGP Extended Community, "Additional PMSI Tunnel Attribute Flags", also defines a new BGP Extended Community, "Additional PMSI Tunnel
that can be used to carry additional flags for the PMSI Tunnel Attribute Flags", that can be used to carry additional flags for the
attribute. PMSI Tunnel attribute. This document updates RFC 6514.
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 February 7, 2016. This Internet-Draft will expire on August 5, 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
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 . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
5. Normative References . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
[RFC6514] defines the "P-Multicast Service Interface Tunnel (PMSI A BGP attribute known as the "P-Multicast Service Interface (PMSI)
Tunnel) attribute". This attribute contains an octet of "flags". Tunnel" attribute is defined in [RFC6514]. This attribute contains a
Only one flag is defined in that RFC, but there is now a need to one-octet of "Flags" field. Only one flag is defined in that RFC,
define additional flags. Since the RFC did not create a registry for but there is now a need to define additional flags. However, that
the assignment of flag bits, this document creates a registry for RFC did not create an IANA registry for the assignment of bits in the
that purpose. In addition, there may be a need to define more than Flags field. This document creates a registry for that purpose. In
eight flags. Therefore this document defines a new BGP Extended addition, there may be a need to define more than eight flags.
Community, "Additional PMSI Tunnel Attribute Flags", that can be used Therefore this document defines a new BGP Extended Community,
to carry additional flags for the PMSI Tunnel attribute. A registry "Additional PMSI Tunnel Attribute Flags", that can be used to carry
is also created for this extended community, allowing IANA to additional flags for the PMSI Tunnel attribute. A registry is also
allocate bits from the extended community's six-octet value field. created for this Extended Community, allowing IANA to assign 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
[RFC6514] defines only a single octet in the PMSI Tunnel attribute to In [RFC6514], only a single octet in the PMSI Tunnel attribute is
use for bit flags. This allows eight flags, which is unlikely to be defined to carry bit flags. This allows eight flags, which is
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 "Additional PMSI Tunnel Attribute Flags". It also defines a new bit
flag in the PMSI Tunnel Attribute flags field, called the "Extension" flag in the PMSI Tunnel Attribute flags field, called the "Extension"
flag. flag.
The "Additional PMSI Tunnel Attribute Flags" Extended Community MUST The Additional PMSI Tunnel Attribute Flags Extended Community MUST
NOT be added to a BGP UPDATE message unless that message is also NOT be carried by a given BGP UPDATE message unless the following
carrying a PMSI Tunnel attribute. Further, when an "Additional PMSI conditions both hold:
Tunnel Attribute Flags" Extended Community is added to a BGP UPDATE
message, the "Extension" flag of the PMSI Tunnel attribute flags o the given BGP UPDATE message is also carrying a PMSI Tunnel
field MUST be set. If at any time the "Additional PMSI Tunnel attribute, and
Attribute Flags" Extended Community is removed from the UPDATE
message, the "Extension" flag in the PMSI Tunnel attribute MUST be o the Extension flag of that PMSI Tunnel attribute's Flags field is
cleared. set.
If a given BGP UPDATE message is carrying a PMSI Tunnel attribute,
but is not carrying an Additional PMSI Tunnel Attribute Flags
Extended Community, then the Extension flag in the PMSI Tunnel
attribute MUST be clear.
If a BGP speaker receives an UPDATE message that contains an If a BGP speaker receives an UPDATE message that contains an
"Additional PMSI Tunnel Attribute Flags" Extended Community, but that Additional PMSI Tunnel Attribute Flags Extended Community, but either
UPDATE message does not contain a PMSI Tunnel attribute, or the (a) that UPDATE message does not contain a PMSI Tunnel attribute, or
"Extension" flag of the PMSI Tunnel attribute is not set, the (b) the Extension flag of the PMSI Tunnel attribute is not set, then
Extended Community SHOULD be removed and SHOULD NOT be redistributed. the Extended Community SHOULD be removed and SHOULD NOT be
The BGP UPDATE message MUST be processed (and if necessary, redistributed. The BGP UPDATE message MUST be processed (and if
redistributed) as if the Extended Community had not been present. necessary, redistributed) as if the Extended Community had not been
present.
If a BGP speaker receives an UPDATE message that contains a PMSI Suppose a BGP speaker receives an UPDATE message that contains a PMSI
Tunnel attribute and does not contain an "Additional PMSI Tunnel Tunnel attribute, but does not contain an Additional PMSI Tunnel
Attribute Flags" Extended Community, but the Extension flag of the Attribute Flags Extended Community. If the Extension flag of the
PMSI Tunnel attribute is set, the "treat-as-withdraw" procedure of PMSI Tunnel attribute is set, then the "treat-as-withdraw" procedure
[ERRORS] MUST be applied. of [RFC7606] MUST be applied.
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 Tunnel (PMSI Tunnel) Attribute Flags" in the Service Interface (PMSI) Tunnel Attribute Flags" in the "Border
"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
4 unassigned 4 unassigned
5 unassigned 5 unassigned
6 unassigned 6 unassigned
7 Leaf Information Required (LIR) RFC6514 7 Leaf Information Required (L) RFC6514
PMSI Tunnel Attribute Flags PMSI Tunnel Attribute Flags
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 "Transitive IANA is also requested to assign a codepoint, from the "First Come,
Opaque Extended Community Sub-Types" registry for "Additional PMSI First Served" range of the Transitive Opaque Extended Community Sub-
Tunnel Attribute Flags". Types registry, for "Additional PMSI Tunnel Attribute Flags".
[TO BE REMOVED: This registration should take place at the following
location: http://www.iana.org/assignments/bgp-extended-communities
/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".
Initially, bits 0-47 are unassigned. This registry belongs with the [TO BE REMOVED: The creation of the registry should take place at the
BGP Extended Communities registries. following location: http://www.iana.org/assignments/bgp-extended-
communities/bgp-extended-communities.xhtml]
The initial registry should be as follows:
4. Security Considerations Bit Flag Name Reference
No security considerations are raised by this document. 0-47 unassigned
5. Normative References Additional PMSI Tunnel Attribute Flags
[ERRORS] Chen, E., Scudder, J., Mohapatra, P., and K. Patel, 4. Acknowledgments
"Revised Error Handling for BGP UPDATE Messages",
internet-draft draft-ietf-idr-error-handling-19, April The authors wish to thank Martin Vigoureux for his review of this
2015. document.
5. Security Considerations
This document establishes an IANA registry, and defines a new
transitive opaque Extended Community.
Establishment of an IANA registry does not raise any security
considerations.
While the document defines a new Extended Community for carrying bit
flags, it does not define any of the bit flags in that Extended
Community. Therefore no security considerations are raised.
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>.
[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>.
[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
Patel, "Revised Error Handling for BGP UPDATE Messages",
RFC 7606, DOI 10.17487/RFC7606, August 2015,
<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
Westford, Massachusetts 01886 Westford, Massachusetts 01886
United States United States
Email: erosen@juniper.net Email: erosen@juniper.net
Thomas Morin Thomas Morin
Orange Orange
2, avenue Pierre-Marzin 2, avenue Pierre-Marzin
22307 Lannion Cedex 22307 Lannion Cedex
France France
Email: thomas.morin@orange.com Email: thomas.morin@orange.com
 End of changes. 21 change blocks. 
65 lines changed or deleted 98 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/