draft-ietf-idr-eag-distribution-06.txt   draft-ietf-idr-eag-distribution-07.txt 
IDR Working Group Z. Wang IDR Working Group Z. Wang
Internet-Draft Q. Wu Internet-Draft Q. Wu
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: September 20, 2018 J. Tantsura Expires: March 14, 2019 J. Tantsura
Nuage Networks Nuage Networks
March 19, 2018 September 10, 2018
Distribution of MPLS-TE Extended admin Group Using BGP Distribution of MPLS-TE Extended admin Group Using BGP
draft-ietf-idr-eag-distribution-06 draft-ietf-idr-eag-distribution-07
Abstract Abstract
As MPLS-TE network grows, administrative Groups advertised as a As MPLS-TE network grows, administrative Groups advertised as a
fixed-length 32-bit Bitmask is quite constraining. "Extended fixed-length 32-bit Bitmask is quite constraining. "Extended
Administrative Group" IGP TE extensions sub-TLV is introduced to Administrative Group" IGP TE extensions sub-TLV is introduced to
provide for additional administrative groups (link colors) beyond the provide for additional administrative groups (link colors) beyond the
current limit of 32. This document describes extensions to BGP current limit of 32. This document describes extensions to BGP
protocol, that can be used to distribute extended administrative protocol, that can be used to distribute extended administrative
groups in MPLS-TE. groups in MPLS-TE.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 September 20, 2018. This Internet-Draft will expire on March 14, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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. Conventions used in this document . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Carrying Extended Administrative Groups in BGP . . . . . . . 2 3. Carrying Extended Administrative Groups in BGP . . . . . . . 3
3.1. AG and EAG coexistence . . . . . . . . . . . . . . . . . 3 3.1. AG and EAG coexistence . . . . . . . . . . . . . . . . . 3
3.2. Desire for unadvertised EAG bits . . . . . . . . . . . . 3 3.2. Desire for unadvertised EAG bits . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
7. Normative References . . . . . . . . . . . . . . . . . . . . 4 7. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
MPLS-TE advertises 32 administrative groups (commonly referred to as MPLS-TE advertises 32 administrative groups (commonly referred to as
"colors" or "link colors") using the Administrative Group sub-TLV of "colors" or "link colors") using the Administrative Group sub-TLV of
the Link TLV defined in OSPFv2 (RFC3630), OSPFv3 (RFC5329) and ISIS the Link TLV defined in OSPFv2 (RFC3630), OSPFv3 (RFC5329) and ISIS
(RFC5305). (RFC5305).
As MPLS-TE network grows, administrative Groups advertised as a As MPLS-TE network grows, administrative Groups advertised as a
fixed-length 32-bit Bitmask is quite constraining. "Extended fixed-length 32-bit Bitmask is quite constraining. "Extended
Administrative Group" IGP TE extensions sub-TLV defined in [RFC7308] Administrative Group" IGP TE extensions sub-TLV defined in [RFC7308]
is introduced to provide for additional administrative groups (link is introduced to provide for additional administrative groups (link
colors) beyond the current limit of 32. colors) beyond the current limit of 32.
This document proposes new BGP Link attribute TLVs that can be This document proposes new BGP Link attribute TLVs that can be
announced as attribute in the BGP-LS attribute (defined in [I.D-ietf- announced as attribute in the BGP-LS attribute (defined in [I.D-ietf-
idr-ls-distribution]) to distribute extended administrative groups in idr-ls-distribution]) to distribute extended administrative groups in
MPLS-TE. MPLS-TE.
2. Conventions used in this document 2. Requirements Language
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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Carrying Extended Administrative Groups in BGP 3. Carrying Extended Administrative Groups in BGP
This document proposes one new BGP link attribute TLVs that can be This document proposes one new BGP link attribute TLVs that can be
announced as attribute in the BGP-LS attribute (defined in [I.D-ietf- announced as attribute in the BGP-LS attribute (defined in [I.D-ietf-
idr-ls-distribution]) to distribute extended administrative groups. idr-ls-distribution]) to distribute extended administrative groups.
The extensions in this document build on the ones provided in BGP-LS The extensions in this document build on the ones provided in BGP-LS
[RFC7752] and BGP-4 [RFC4271]. [RFC7752] and BGP-4 [RFC4271].
BGP-LS attribute defined in [RFC7752] has nested TLVs which allow the BGP-LS attribute defined in [RFC7752] has nested TLVs which allow the
BGP-LS attribute to be readily extended. Link attribute TLVs defined BGP-LS attribute to be readily extended. Link attribute TLVs defined
in section 3.2.2 of [I-D.ietf-idr-ls-distribution]are TLVs that may in section 3.2.2 of [I-D.ietf-idr-ls-distribution]are TLVs that may
be encoded in the BGP-LS attribute with a link NLRI. Each 'Link be encoded in the BGP-LS attribute with a link NLRI. Each 'Link
Attribute' is a Type/Length/ Value (TLV) triplet formatted as defined Attribute' is a Type/Length/ Value (TLV) triplet formatted as defined
in Section 3.1 of [I-D.ietf-idr-ls-distribution]. in Section 3.1 of [I-D.ietf-idr-ls-distribution].
skipping to change at page 4, line 43 skipping to change at page 5, line 5
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, October 2008. Engineering", RFC 5305, October 2008.
[RFC7308] Osborne, E., "Extended Administrative Groups in MPLS-TE", [RFC7308] Osborne, E., "Extended Administrative Groups in MPLS-TE",
ID RFC7308, July 2014. ID RFC7308, July 2014.
[RFC7752] Gredler, H., "North-Bound Distribution of Link-State and [RFC7752] Gredler, H., "North-Bound Distribution of Link-State and
TE Information using BGP", RFC 7752, March 2016. TE Information using BGP", RFC 7752, March 2016.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Authors' Addresses Authors' Addresses
Zitao Wang Zitao Wang
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: wangzitao@huawei.com Email: wangzitao@huawei.com
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: bill.wu@huawei.com Email: bill.wu@huawei.com
Jeff Tantsura Jeff Tantsura
Nuage Networks Nuage Networks
 End of changes. 12 change blocks. 
12 lines changed or deleted 18 lines changed or added

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