idnits 2.17.1 draft-li-idr-link-bandwidth-ext-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-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 date (24 October 2021) is 915 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 178, but not defined Summary: 1 error (**), 0 flaws (~~), 2 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: 27 April 2022 Huawei Technologies 6 24 October 2021 8 Extension of Link Bandwidth Extended Community 9 draft-li-idr-link-bandwidth-ext-00 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 27 April 2022. 44 Copyright Notice 46 Copyright (c) 2021 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 Simplified BSD License text 55 as described in Section 4.e of the Trust Legal Provisions and are 56 provided without warranty as described in the Simplified 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. The combination of unit type and unsigned integer value is 88 used to describe the link bandwidth value. This is easier for 89 operators to use and understand, and can avoid configuration and 90 computation errors. 92 2. Link Bandwidth Extended Community 94 The type of Link Bandwidth Extended Community is 0x40, and the 95 subtype is 0x04. In the attribute value, the global administrator 96 subfield is set to the AS number of the route to which the Link 97 Bandwidth attribute is added. In the local administrator subfield, 98 the link bandwidth value [I-D.ietf-idr-link-bandwidth] is set to the 99 IEEE floating-point type. 101 This document retains the basic format of Link Bandwidth Extended 102 Community, uses several special subtypes to identify different 103 bandwidth units, and uses a combination of units and integers to 104 accurately represent a specific bandwidth value. 106 * bps Link Bandwidth, subtype is TBD. The value of bandwidth in the 107 Local Administrator subfield is an unsigned integer. The unit of 108 this type of link bandwidth is bps. 110 * Kbps Link Bandwidth, subtype is TBD. The value of bandwidth in 111 the Local Administrator subfield is an unsigned integer. The unit 112 of this type of link bandwidth is Kbps. 114 * Mbps Link Bandwidth, subtype is TBD. The value of bandwidth in 115 the Local Administrator subfield is an unsigned integer. The unit 116 of this type of link bandwidth is Mbps. 118 * Gbps Link Bandwidth, subtype is TBD. The value of bandwidth in 119 the Local Administrator subfield is an unsigned integer. The unit 120 of this type of link bandwidth is Gbps. 122 * Tbps Link Bandwidth, subtype is TBD. The value of bandwidth in 123 the Local Administrator subfield is an unsigned integer. The unit 124 of this type of link bandwidth is Tbps. 126 We can use different unit bandwidth values to identify the required 127 bandwidth. 129 The subtypes defined here can be used for both optional transitive 130 and non-transitive extended community attributes. 132 3. Deployment Considerations 134 In network deployment, a routing policy may be used to match the link 135 bandwidth advertised by BGP link bandwidth extended community, based 136 on the mechanisms of this document, the operator can specify the 137 bandwidth in different units as required, so that exact value 138 matching can be achieved. 140 Bandwidths of different units may be used together. For example, an 141 link bandwidth extended community with the type Gbps and value 1, and 142 another link bandwidth extended community with the type Mbps and 143 value 500 may be used to represent 1.500 Gbps. However, it is 144 RECOMMENDED to use a single link bandwidth extended community with 145 the type Mbps and value 1500 Mbps to achieve the same purpose. 147 4. IANA Considerations 149 This document defines a specific application of the two-octet AS 150 specific extended community. IANA is requested to assign new sub- 151 types for both non-transitive and transitive extended communities. 153 SubType Description 154 ------- ------------------------------- 155 TBD Link Bandwidth EC in bps unit 156 TBD Link Bandwidth EC in Kbps unit 157 TBD Link Bandwidth EC in Mbps unit 158 TBD Link Bandwidth EC in Gbps unit 159 TBD Link Bandwidth EC in Tbps unit 161 5. Security Considerations 163 There are no additional security risks introduced by this design. 165 6. Acknowledgements 167 7. References 169 7.1. Normative References 171 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 172 Requirement Levels", BCP 14, RFC 2119, 173 DOI 10.17487/RFC2119, March 1997, 174 . 176 7.2. References 178 [I-D.ietf-idr-link-bandwidth] 179 Mohapatra, P. and R. Fernando, "BGP Link Bandwidth 180 Extended Community", Work in Progress, Internet-Draft, 181 draft-ietf-idr-link-bandwidth-07, 5 March 2018, 182 . 185 Authors' Addresses 186 Wenyan Li 187 Huawei Technologies 188 Huawei Campus, No. 156 Beiqing Road 189 Beijing 190 100095 191 China 193 Email: liwenyan@huawei.com 195 Haibo Wang 196 Huawei Technologies 197 Huawei Campus, No. 156 Beiqing Road 198 Beijing 199 100095 200 China 202 Email: rainsword.wang@huawei.com 204 Jie Dong 205 Huawei Technologies 206 Huawei Campus, No. 156 Beiqing Road 207 Beijing 208 100095 209 China 211 Email: jie.dong@huawei.com