idnits 2.17.1 draft-li-idr-link-bandwidth-ext-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 ([I-D.ietf-idr-link-bandwidth]), 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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (5 March 2022) is 783 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) == Missing Reference: 'I-D.ietf-idr-link-bandwidth' is mentioned on line 169, but not defined == Missing Reference: 'RFC5701' is mentioned on line 180, but not defined == Missing Reference: 'RFC4360' is mentioned on line 176, but not defined Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group W. Li 3 Internet-Draft H. Wang 4 Intended status: Standards Track J. Dong 5 Expires: 6 September 2022 Huawei Technologies 6 5 March 2022 8 Extension of Link Bandwidth Extended Community 9 draft-li-idr-link-bandwidth-ext-01 11 Abstract 13 [I-D.ietf-idr-link-bandwidth] defines a BGP link bandwidth extended 14 community attribute, which can enable devices to implement unequal- 15 cost load-balancing. However, the bandwidth value encapsulated by 16 the extended community attribute is of the floating-point type, which 17 is inconvenient to use. In this document, a set of new types of link 18 bandwidth extended community are introduced to facilitate the 19 configuration and calculation of link bandwidth. 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in RFC 2119 [RFC2119]. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on 6 September 2022. 44 Copyright Notice 46 Copyright (c) 2022 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 51 license-info) in effect on the date of publication of this document. 52 Please review these documents carefully, as they describe your rights 53 and restrictions with respect to this document. Code Components 54 extracted from this document must include Revised BSD License text as 55 described in Section 4.e of the Trust Legal Provisions and are 56 provided without warranty as described in the Revised BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Link Bandwidth Extended Community . . . . . . . . . . . . . . 3 62 3. Deployment Considerations . . . . . . . . . . . . . . . . . . 3 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 64 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 65 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 66 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 68 7.2. References . . . . . . . . . . . . . . . . . . . . . . . 4 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 71 1. Introduction 73 In [I-D.ietf-idr-link-bandwidth], the link bandwidth extended 74 community attribute is added to implement unequal-cost load balancing 75 based on the bandwidth on a path. As defined in the draft, the 76 bandwidth of a link is expressed in 4-octets in IEEE floating-point 77 format. 79 In practice, the use of this floating-point format may result errors 80 in configuration and computation. When an operator needs to manually 81 specify the bandwidth, you also need to consider the conversion from 82 the bandwidth value to the floating-point number. This mode is not 83 user-friendly, especially when the routing policy is used for 84 bandwidth matching. 86 This document introduce a more intuitive expression of link bandwidth 87 in BGP. It uses an unsigned long integer value to describe the link 88 bandwidth value. This is easier for operators to use and understand, 89 and can avoid configuration and computation errors. 91 2. Link Bandwidth Extended Community 93 The type of Link Bandwidth Extended Community is 0x40, and the 94 subtype is 0x04. In the attribute value, the global administrator 95 subfield is set to the AS number of the route to which the Link 96 Bandwidth attribute is added. In the local administrator subfield, 97 the link bandwidth value [I-D.ietf-idr-link-bandwidth] is set to the 98 IEEE floating-point type. 100 A new type of IPv6 Address Specific Extended Community[RFC5701] is 101 added in this document. The ASN field of this attribute is set to 102 the AS number of the route to which the link bandwidth attribute is 103 added. The Link Bandwidth value field (8 bytes) is set to the link 104 bandwidth. The following extended contents are added: 106 0 1 2 3 107 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 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | 0x03 or 0x43 | Sub-Type | Reserved | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | 8 bytes Link Bandwidth value (cont.) | 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | 8 bytes Link Bandwidth value (cont.) | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | 4 bytes ASN | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | Reserved | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 * The value of the high-order octet of the extended Type, refer to 121 [RFC4360], It is recommended that 0x03 and 0x43 be used. 123 * New Link Bandwidth, subtype is TBD. The value of the Link 124 Bandwidth subfield is an unsigned long integer, in bytes per 125 second. 127 The subtypes defined here can be used for both optional transitive 128 and non-transitive extended community attributes. 130 3. Deployment Considerations 132 The extended link bandwidth extended community attribute in this 133 document should not be used together with the standard link bandwidth 134 extended community attribute. If a route carries both the standard 135 link bandwidth extended community attribute and the unit link 136 bandwidth extended community attribute, the standard link bandwidth 137 extended community attribute is ignored. 139 In actual deployment, if a routing policy is used to match link 140 bandwidth attributes, you can directly perform exact value matching. 142 4. IANA Considerations 144 This document defines a specific application of the two-octet AS 145 specific extended community. IANA is requested to assign new sub- 146 types for both non-transitive and transitive extended communities. 148 SubType Description 149 ------- ------------------------------- 150 TBD Link Bandwidth EC in bytes per second 152 5. Security Considerations 154 There are no additional security risks introduced by this design. 156 6. Acknowledgements 158 7. References 160 7.1. Normative References 162 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 163 Requirement Levels", BCP 14, RFC 2119, 164 DOI 10.17487/RFC2119, March 1997, 165 . 167 7.2. References 169 [I-D.ietf-idr-link-bandwidth] 170 Mohapatra, P. and R. Fernando, "BGP Link Bandwidth 171 Extended Community", Work in Progress, Internet-Draft, 172 draft-ietf-idr-link-bandwidth-07, 5 March 2018, 173 . 176 [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended 177 Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, 178 February 2006, . 180 [RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community 181 Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009, 182 . 184 Authors' Addresses 185 Wenyan Li 186 Huawei Technologies 187 Huawei Campus, No. 156 Beiqing Road 188 Beijing 189 100095 190 China 191 Email: liwenyan@huawei.com 193 Haibo Wang 194 Huawei Technologies 195 Huawei Campus, No. 156 Beiqing Road 196 Beijing 197 100095 198 China 199 Email: rainsword.wang@huawei.com 201 Jie Dong 202 Huawei Technologies 203 Huawei Campus, No. 156 Beiqing Road 204 Beijing 205 100095 206 China 207 Email: jie.dong@huawei.com