idnits 2.17.1 draft-ietf-idr-eag-distribution-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC7308]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 7, 2015) is 3060 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-idr-ls-distribution' is defined on line 164, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Working Group Z. Wang 3 Internet-Draft Q. Wu 4 Intended status: Standards Track Huawei 5 Expires: June 9, 2016 J. Tantsura 6 Ericsson 7 December 7, 2015 9 Distribution of MPLS-TE Extended admin Group Using BGP 10 draft-ietf-idr-eag-distribution-01 12 Abstract 14 As MPLS-TE network grows, administrative Groups advertised as a 15 fixed-length 32-bit Bitmask is quite constraining. "Extended 16 Administrative Group" IGP TE extensions sub-TLV defined in [RFC7308] 17 is introduced to provide for additional administrative groups (link 18 colors) beyond the current limit of 32. This document describes 19 extensions to BGP protocol, that can be used to distribute extended 20 administrative groups in MPLS-TE. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on June 9, 2016. 39 Copyright Notice 41 Copyright (c) 2015 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Conventions used in this document . . . . . . . . . . . . . . 2 58 3. Carrying Extended Administrative Groups in BGP . . . . . . . 2 59 3.1. AG and EAG coexistence . . . . . . . . . . . . . . . . . 3 60 3.2. Desire for unadvertised EAG bits . . . . . . . . . . . . 3 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 62 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 63 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 64 7. Normative References . . . . . . . . . . . . . . . . . . . . 4 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 MPLS-TE advertises 32 administrative groups (commonly referred to as 70 "colors" or "link colors") using the Administrative Group sub-TLV of 71 the Link TLV defined in OSPFv2 (RFC3630), OSPFv3 (RFC5329) and ISIS 72 (RFC5305). 74 As MPLS-TE network grows, administrative Groups advertised as a 75 fixed-length 32-bit Bitmask is quite constraining. "Extended 76 Administrative Group" IGP TE extensions sub-TLV defined in [RFC7308] 77 is introduced to provide for additional administrative groups (link 78 colors) beyond the current limit of 32. 80 This document proposes new BGP Link attribute TLVs that can be 81 announced as attribute in the BGP-LS attribute (defined in [I.D-ietf- 82 idr-ls-distribution]) to distribute extended administrative groups in 83 MPLS-TE. 85 2. Conventions used in this document 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in RFC2119 [RFC2119]. 91 3. Carrying Extended Administrative Groups in BGP 93 This document proposes one new BGP link attribute TLVs that can be 94 announced as attribute in the BGP-LS attribute (defined in [I.D-ietf- 95 idr-ls-distribution]) to distribute extended administrative groups. 97 The extensions in this document build on the ones provided in BGP-LS 98 [I.D-ietf-idr-ls-distribution] and BGP-4 [RFC4271]. 100 BGP-LS attribute defined in [I.D-ietf-idr-ls-distribution] has nested 101 TLVs which allow the BGP-LS attribute to be readily extended. Link 102 attribute TLVs defined in section 3.2.2 of [I-D.ietf-idr-ls- 103 distribution]are TLVs that may be encoded in the BGP-LS attribute 104 with a link NLRI. Each 'Link Attribute' is a Type/Length/ Value 105 (TLV) triplet formatted as defined in Section 3.1 of [I-D.ietf-idr- 106 ls-distribution]. 108 This document proposes one new TLV as a link attribute: 110 Type Value 112 TBD1 Extended Admin Group (EAG) 114 The EAG TLV is used in addition to the Administrative Groups when a 115 node wants to advertise more than 32 colors for a link. The EAG TLV 116 is optional. The format and semantics of the 'value' fields in EAG 117 TLVs correspond to the format and semantics of value fields in IGP 118 extension sub-TLVs, defined in [RFC7308]. 120 +------------+---------------------+--------------+-----------------+ 121 | TLV Code | Description | IS-IS | Defined in: | 122 | Point | | TLV/Sub-TLV | | 123 +------------+---------------------+--------------+-----------------+ 124 | xxxx | Extended | 22/xx | [RFC7308] | 125 | | Admin Group | | | 126 +------------+---------------------+--------------+-----------------+ 128 Table 1: 'EAG' Link Attribute TLV 130 3.1. AG and EAG coexistence 132 Similar to section 2.3.1 of [RFC7308],if a BGP speaker advertises 133 both AG and EAG then AG and EAG should be dealt with in the same way 134 as AG and EAG carried in the Extended Administrative Group (EAG) sub- 135 TLV [RFC7308] for both OSPF [RFC3630] and ISIS [RFC5305]. 137 3.2. Desire for unadvertised EAG bits 139 Unlike AGs, EAGs are advertised as any non-zero-length-bit Bitmask. 140 the EAG length may be longer for some links than for others. Similar 141 to section 2.3.2 of [RFC7308], if a BGP peer wants to only use links 142 where the specific bits of an EAG is set to 1 but the specific bits 143 of this EAG is not advertised, then the implementation SHOULD process 144 these desire and unadvertised EAG bits in accordance with rule 145 defined in section 2.3.2 of [RFC7308]. 147 4. Security Considerations 149 This document does not introduce security issues beyond those 150 discussed in [I.D-ietf-idr-ls-distribution] and [RFC4271]. 152 5. IANA Considerations 154 IANA maintains the registry for the TLVs. BGP Extended Admin Group 155 link attribute TLV will require one new type code defined in this 156 document. 158 6. Acknowledgments 160 The authors gratefully acknowledge the review made by Eric Osborne. 162 7. Normative References 164 [I-D.ietf-idr-ls-distribution] 165 Gredler, H., "North-Bound Distribution of Link-State and 166 TE Information using BGP", ID draft-ietf-idr-ls- 167 distribution-13, October 2015. 169 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 170 Requirement Levels", March 1997. 172 [RFC3630] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 173 (TE) Extensions to OSPF Version 2", RFC 3630, September 174 2003. 176 [RFC4271] Rekhter, Y., "A Border Gateway Protocol 4 (BGP-4)", 177 RFC 4271, January 2006. 179 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 180 Engineering", RFC 5305, October 2008. 182 [RFC7308] Osborne, E., "Extended Administrative Groups in MPLS-TE", 183 ID RFC7308, July 2014. 185 Authors' Addresses 186 Zitao Wang 187 Huawei 188 101 Software Avenue, Yuhua District 189 Nanjing, Jiangsu 210012 190 China 192 Email: wangzitao@huawei.com 194 Qin Wu 195 Huawei 196 101 Software Avenue, Yuhua District 197 Nanjing, Jiangsu 210012 198 China 200 Email: bill.wu@huawei.com 202 Jeff Tantsura 203 Ericsson 204 300 Holger Way 205 San Jose, CA 95134 206 US 208 Email: jeff.tantsura@ericsson.com