idnits 2.17.1 draft-wang-idr-eag-distribution-00.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 ([I-D.ietf-mpls-extended-admin-group]), 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 (September 20, 2014) is 3505 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 == Unused Reference: 'I-D.ietf-mpls-extended-admin-group' is defined on line 169, but no explicit reference was found in the text == Outdated reference: A later version (-13) exists of draft-ietf-idr-ls-distribution-03 Summary: 1 error (**), 0 flaws (~~), 4 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: March 24, 2015 September 20, 2014 7 Distribution of MPLS-TE Extended admin Group Using BGP 8 draft-wang-idr-eag-distribution-00 10 Abstract 12 As MPLS-TE network grows, administrative Groups advertised as a 13 fixed-length 32-bit Bitmask is quite constraining. "Extended 14 Administrative Group" IGP TE extensions sub-TLV defined in [I-D.ietf- 15 mpls-extended-admin-group] is introduced to provide for additional 16 administrative groups (link colors) beyond the current limit of 32. 17 This document describes extensions to BGP protocol, that can be used 18 to distribute extended administrative groups in MPLS-TE. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on March 24, 2015. 37 Copyright Notice 39 Copyright (c) 2014 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Conventions used in this document . . . . . . . . . . . . . . 2 56 3. Carrying Extended Administrative Groups in BGP . . . . . . . 2 57 3.1. AG and EAG coexistence . . . . . . . . . . . . . . . . . 3 58 3.2. Desire for unadvertised EAG bits . . . . . . . . . . . . 3 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 61 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 62 7. Normative References . . . . . . . . . . . . . . . . . . . . 4 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 65 1. Introduction 67 MPLS-TE advertises 32 administrative groups (commonly referred to as 68 "colors" or "link colors") using the Administrative Group sub-TLV of 69 the Link TLV defined in OSPFv2 (RFC3630), OSPFv3 (RFC5329) and ISIS 70 (RFC5305). 72 As MPLS-TE network grows, administrative Groups advertised as a 73 fixed-length 32-bit Bitmask is quite constraining. "Extended 74 Administrative Group" IGP TE extensions sub-TLV defined in [I-D.ietf- 75 mpls-extended-admin-group] is introduced to provide for additional 76 administrative groups (link colors) beyond the current limit of 32. 78 This document proposes new BGP Link attribute TLVs that can be 79 announced as attribute in the BGP-LS attribute (defined in [I.D-ietf- 80 idr-ls-distribution]) to distribute extended administrative groups in 81 MPLS-TE. 83 2. Conventions used in this document 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 87 document are to be interpreted as described in RFC2119 [RFC2119]. 89 3. Carrying Extended Administrative Groups in BGP 91 This document proposes one new BGP link attribute TLVs that can be 92 announced as attribute in the BGP-LS attribute (defined in [I.D-ietf- 93 idr-ls-distribution]) to distribute extended administrative groups. 94 The extensions in this document build on the ones provided in BGP-LS 95 [I.D-ietf-idr-ls-distribution] and BGP-4 [RFC4271]. 97 BGP-LS attribute defined in [I.D-ietf-idr-ls-distribution] has nested 98 TLVs which allow the BGP-LS attribute to be readily extended. Link 99 attribute TLVs defined in section 3.2.2 of [I-D.ietf-idr-ls- 100 distribution]are TLVs that may be encoded in the BGP-LS attribute 101 with a link NLRI. Each 'Link Attribute' is a Type/Length/ Value 102 (TLV) triplet formatted as defined in Section 3.1 of [I-D.ietf-idr- 103 ls-distribution]. 105 This document proposes one new TLV as a link attribute: 107 Type Value 109 TBD1 Extended Admin Group (EAG) 111 The EAG TLV is used in addition to the Administrative Groups when a 112 node wants to advertise more than 32 colors for a link. The EAG TLV 113 is optional. The format and semantics of the 'value' fields in EAG 114 TLVs correspond to the format and semantics of value fields in IGP 115 extension sub-TLVs, defined in [I-D.ietf-mpls-extended- admin-group]. 117 +------------+---------------------+--------------+-----------------+ 118 | TLV Code | Description | IS-IS | Defined in: | 119 | Point | | TLV/Sub-TLV | | 120 +------------+---------------------+--------------+-----------------+ 121 | xxxx | Extended | 22/xx |[I-D.ietf-mpls- | 122 | | Admin Group | |extended-admin | 123 | | | |-group | 124 +------------+---------------------+--------------+-----------------+ 126 Table 1: 'EAG' Link Attribute TLV 128 3.1. AG and EAG coexistence 130 Similar to section 2.3.1 of [I-D.ietf-mpls-extended- admin-group],if 131 a BGP speaker advertises both AG and EAG then AG and EAG should be 132 dealt with in the same way as AG and EAG carried in the Extended 133 Administrative Group (EAG) sub-TLV [I-D.ietf-mpls-extended- admin- 134 group] for both OSPF [RFC3630] and ISIS [RFC5305]. 136 3.2. Desire for unadvertised EAG bits 138 Unlike AGs, EAGs are advertised as any non-zero-length-bit Bitmask. 139 the EAG length may be longer for some links than for others. Similar 140 to section 2.3.2 of [I-D.ietf-mpls-extended- admin-group], if a BGP 141 peer wants to only use links where the specific bits of an EAG is set 142 to 1 but the specific bits of this EAG is not advertised, then the 143 implementation SHOULD process these desire and unadvertised EAG bits 144 in accordance with rule defined in section 2.3.2 of [I.D-ietf-mpls- 145 extended-admin- group]. 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-03, May 2013. 169 [I-D.ietf-mpls-extended-admin-group] 170 Osborne, E., "Extended Administrative Groups in MPLS-TE", 171 ID draft-ietf-mpls-extended-admin-group-07, May 2014. 173 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 174 Requirement Levels", March 1997. 176 [RFC3630] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 177 (TE) Extensions to OSPF Version 2", RFC 3630, September 178 2003. 180 [RFC4271] Rekhter, Y., "A Border Gateway Protocol 4 (BGP-4)", RFC 181 4271, January 2006. 183 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 184 Engineering", RFC 5305, October 2008. 186 Authors' Addresses 187 Zitao Wang 188 Huawei 189 101 Software Avenue, Yuhua District 190 Nanjing, Jiangsu 210012 191 China 193 Email: wangzitao@huawei.com 195 Qin Wu 196 Huawei 197 101 Software Avenue, Yuhua District 198 Nanjing, Jiangsu 210012 199 China 201 Email: bill.wu@huawei.com