<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-li-idr-link-bandwidth-ext-01"
     ipr="trust200902">
  <front>
    <title abbrev="Abbreviated-Title">Extension of Link Bandwidth Extended
    Community</title>

    <author fullname="Wenyan Li" initials="W" surname="Li">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Campus, No. 156 Beiqing Road</street>

          <city>Beijing</city>

          <code>100095</code>

          <region/>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>liwenyan@huawei.com</email>
      </address>
    </author>

    <author fullname="Haibo Wang" initials="H" surname="Wang">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Campus, No. 156 Beiqing Road</street>

          <city>Beijing</city>

          <code>100095</code>

          <region/>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>rainsword.wang@huawei.com</email>
      </address>
    </author>

    <author fullname="Jie Dong" initials="J" surname="Dong">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Campus, No. 156 Beiqing Road</street>

          <city>Beijing</city>

          <code>100095</code>

          <region/>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>jie.dong@huawei.com</email>
      </address>
    </author>

    <date day="5" month="March" year="2022"/>

    <abstract>
      <t><xref target="I-D.ietf-idr-link-bandwidth"/> defines a BGP link
      bandwidth extended community attribute, which can enable devices to
      implement unequal-cost load-balancing. However, the bandwidth value
      encapsulated by the extended community attribute is of the
      floating-point type, which is inconvenient to use. In this document, a
      set of new types of link bandwidth extended community are introduced to
      facilitate the configuration and calculation of link bandwidth.</t>
    </abstract>

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>In <xref target="I-D.ietf-idr-link-bandwidth"/>, the link bandwidth
      extended community attribute is added to implement unequal-cost load
      balancing based on the bandwidth on a path. As defined in the draft, the
      bandwidth of a link is expressed in 4-octets in IEEE floating-point
      format.</t>

      <t>In practice, the use of this floating-point format may result errors
      in configuration and computation. When an operator needs to manually
      specify the bandwidth, you also need to consider the conversion from the
      bandwidth value to the floating-point number. This mode is not
      user-friendly, especially when the routing policy is used for bandwidth
      matching.</t>

      <t>This document introduce a more intuitive expression of link bandwidth
      in BGP. It uses an unsigned long integer value to describe the link
      bandwidth value. This is easier for operators to use and understand, and
      can avoid configuration and computation errors.</t>
    </section>

    <section title="Link Bandwidth Extended Community">
      <t>The type of Link Bandwidth Extended Community is 0x40, and the
      subtype is 0x04. In the attribute value, the global administrator
      subfield is set to the AS number of the route to which the Link
      Bandwidth attribute is added. In the local administrator subfield, the
      link bandwidth value <xref target="I-D.ietf-idr-link-bandwidth"/> is set
      to the IEEE floating-point type.</t>

      <t>A new type of IPv6 Address Specific Extended Community<xref
      target="RFC5701"/> is added in this document. The ASN field of this
      attribute is set to the AS number of the route to which the link
      bandwidth attribute is added. The Link Bandwidth value field (8 bytes)
      is set to the link bandwidth. The following extended contents are
      added:<figure>
          <artwork><![CDATA[0                   1                   2                   3 
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 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x03 or 0x43 |   Sub-Type    |            Reserved            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     8 bytes Link Bandwidth value (cont.)                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     8 bytes Link Bandwidth value (cont.)                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         4 bytes ASN                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         Reserved                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
        </figure><list style="symbols">
          <t>The value of the high-order octet of the extended Type, refer to
          <xref target="RFC4360"/>, It is recommended that 0x03 and 0x43 be
          used.</t>

          <t>New Link Bandwidth, subtype is TBD. The value of the Link
          Bandwidth subfield is an unsigned long integer, in bytes per
          second.</t>
        </list></t>

      <t>The subtypes defined here can be used for both optional transitive
      and non-transitive extended community attributes.</t>
    </section>

    <section title="Deployment Considerations">
      <t>The extended link bandwidth extended community attribute in this
      document should not be used together with the standard link bandwidth
      extended community attribute. If a route carries both the standard link
      bandwidth extended community attribute and the unit link bandwidth
      extended community attribute, the standard link bandwidth extended
      community attribute is ignored.</t>

      <t>In actual deployment, if a routing policy is used to match link
      bandwidth attributes, you can directly perform exact value matching.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document defines a specific application of the two-octet AS
      specific extended community. IANA is requested to assign new sub-types
      for both non-transitive and transitive extended communities.</t>

      <t><figure align="center">
          <artwork><![CDATA[SubType  Description
-------  -------------------------------
  TBD    Link Bandwidth EC in bytes per second
]]></artwork>
        </figure></t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>There are no additional security risks introduced by this design.</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t/>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>
    </references>

    <references title="References">
      <?rfc include="reference.I-D.ietf-idr-link-bandwidth"?>
      <?rfc include="reference.RFC.5701"?>
      <?rfc include="reference.RFC.4360"?>
    </references>
  </back>
</rfc>
