<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-idr-fsv2-scheduling-00" category="std" consensus="true" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="BGP FSv2 Scheduling">BGP Flow Specification Version 2 Extensions for Scheduling</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-idr-fsv2-scheduling-00"/>
    <author initials="L." surname="Zhang" fullname="Li Zhang" role="editor">
      <organization>Huawei</organization>
      <address>
        <postal>
          <street>Beiqing Road</street>
          <city>Beijing</city>
          <country>China</country>
        </postal>
        <email>zhangli344@huawei.com</email>
      </address>
    </author>
    <author initials="T." surname="Zhou" fullname="Tianran Zhou">
      <organization>Huawei</organization>
      <address>
        <email>zhoutianran@huawei.com</email>
      </address>
    </author>
    <author initials="Z." surname="Li" fullname="Zhenqiang Li">
      <organization>China Mobile</organization>
      <address>
        <email>lizhenqiang@chinamobile.com</email>
      </address>
    </author>
    <author initials="J." surname="Dong" fullname="Jie Dong">
      <organization>Huawei</organization>
      <address>
        <email>jie.dong@huawei.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <area>General</area>
    <workgroup>IDR</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 48?>

<t>BGP Flow Specification allows conveying flow specifications and associated traffic actions/rules to perform different actions based on traffic characteristics. Existing traffic filter rules and actions in FSv2 remain effective perpetually; once delivered to the headend, the rules and actions are permanent for traffic.  However, some operators wish to perform different actions for specific flows at specific time.</t>
      <t>This document extends BGP FSv2 with a scheduling time component to match the arrival time of packets. Based on this component, the headend can perform different actions for specific traffic at different times.</t>
    </abstract>
  </front>
  <middle>
    <?line 55?>

<section anchor="intro">
      <name>Introduction</name>
      <t><xref target="RFC8955"/> and <xref target="RFC8956"/> define BGP <xref target="RFC4271"/> Flow Specification (FSv1), which allows conveying flow specifications and associated traffic actions/rules. BGP FlowSpec rules are encoded within the MP_REACH_NLRI and MP_UNREACH_NLRI attributes <xref target="RFC4760"/>. Associated actions are encoded in Extended Community attributes <xref target="RFC4360"/>.
FSv2<xref target="I-D.ietf-idr-fsv2-ip-basic"/> is an update of FSv1, it addresses the issues collected during the deployment of FSv1 and provides flexible TLV-based encoding.</t>
      <t>Existing traffic filter rules and actions in FSv2 remain effective perpetually; once delivered to the headend, the rules and actions are permanent for traffic.  However, some operators wish to perform different actions for specific flows at specific time.</t>
      <t>In tidal networks such as IP carrier backbone networks, traffic varies periodically. Traffic surges during daily rush hours (typically 20:00–22:00) may lead to congestion on certain links. To mitigate such peak-time congestion, operators wish to divert some traffic onto alternative paths or limit the rate of selected flows, with these policies required to be automatically enabled and disabled at specified times.</t>
      <t>This document extends BGP FSv2 with a scheduling time component to match the arrival time of packets. Based on this component, the headend can perform different actions for specific traffic at different times (e.g., diverting traffic to different paths).</t>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        <?line -18?>

</section>
    </section>
    <section anchor="flowspecv2-extensions-for-scheduling">
      <name>FlowSpecv2 Extensions for Scheduling</name>
      <t>In <xref section="3.1.1" sectionFormat="of" target="I-D.ietf-idr-fsv2-ip-basic"/>, it defines a list of FSv2 filter family types, including the value 200 assigned for the time filter family type. The format of time filter is shown below:</t>
      <figure anchor="ref-to-fig1">
        <name>Format of time filter in FSv2</name>
        <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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FSv2 Filter Family type =200  |   Fsv2 filter Family length   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             FSv2 Filter Component TLVs (variable)             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
      </figure>
      <t>This document defines a new FSv2 filter component, the scheduling time component, for the FSv2 time filter family. It matches packet arrival times to trigger specific actions.</t>
      <t>The value 100 is recommended as the type value for the scheduling time component.</t>
      <t>Encoding: &lt;scheduling time (variable)+&gt;</t>
      <t>Scheduling time information: time criteria used to filter packets, contains a list of Scheduling Time information. The format of scheduling time information is specified in <xref target="scheduling-time-information"/>.</t>
      <section anchor="scheduling-time-information">
        <name>Scheduling Time Information</name>
        <t>The format of scheduling time information is shown as follows:</t>
        <figure anchor="ref-to-fig2">
          <name>Format of Scheduling Time Information</name>
          <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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Schedule-id  |    Length     |  Flags    |P|S|   Reserved    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          Start Time                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          Start Time                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      End Time (Duration)                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      End Time (Duration)                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     Frequency (Optional)                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   Recurrence Count(Optional)                  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>
        <ul spacing="normal">
          <li>
            <t>Schedule-id: 8-bit value, a unique identifier to distinguish each schedule within a Filter Component. This value is allocated by the FlowSpec originator.</t>
          </li>
          <li>
            <t>length: 8 bits, length of the current scheduling time information in bytes.</t>
          </li>
          <li>
            <t>Flags: 8 bits. Currently only 2 bits are defined; remaining bits are reserved. The reserved bit should be set to 0 and ignored by the receiver.  </t>
            <ul spacing="normal">
              <li>
                <t>P (Period format): 1-bit flag indicating the interpretation of the period definition. If P=1, the period is defined by a start time field and an end time field. If P=0, the period is defined by a start time field plus a duration value.</t>
              </li>
              <li>
                <t>S (Schedule type): 1-bit flag indicating the schedule recurrence type. If S=0, the schedule has only one instance; the Frequency and Recurrence Count fields <bcp14>MUST NOT</bcp14> be present in the sub-TLV. If S=1, the schedule has multiple recurring instances; the Frequency and Recurrence Count fields <bcp14>MUST</bcp14> be present.</t>
              </li>
            </ul>
          </li>
          <li>
            <t>Start Time: 64-bit value, representing the number of seconds since the epoch. It specifies the start time for traffic matching. The epoch is 1 January 1970 at 00:00 UTC.</t>
          </li>
          <li>
            <t>End Time (Duration): 64-bit value. If flag P=1, this field specifies the endtime for traffic matching. If flag P=0, this field carries the number of seconds offset from the Start Time and specifies the duration of traffic matching.</t>
          </li>
          <li>
            <t>Frequency (optional): 32-bit value. It defines the number of seconds between the start time of one schedule instance and the start time of the next instance. This field indicates the recurrence interval for all instances of this schedule. This field <bcp14>MUST NOT</bcp14> be present if S=0.</t>
          </li>
          <li>
            <t>Recurrence Count (optional): 32-bit value, specifying the total number of repetitions. For example, if set to 2, the schedule repeats twice using the specified Frequency. This field <bcp14>MUST NOT</bcp14> be present if S=0. Value of 0 means repeat infinitely.</t>
          </li>
        </ul>
        <t>Multiple instances of Scheduling Time Information may occur in a scheduling time component TLV. Multiple Scheduling Time Information within the same time component are OR'ed. if any time window matches the packet arrival time, the Time Filter matches.</t>
      </section>
    </section>
    <section anchor="procedures">
      <name>Procedures</name>
      <section anchor="receiving-procedures">
        <name>Receiving Procedures</name>
        <t>When a BGP speaker receives a FSv2 NLRI containing a Scheduling Time Component in the Time Filter Family (type 200):</t>
        <ul spacing="normal">
          <li>
            <t>It validates each scheduling time information in the Scheduling Time Component TLV. Invalid scheduling time information in the component (e.g., inconsistent S flag and optional fields, EndTime ≤ StartTime) <bcp14>SHOULD</bcp14> be silently discarded (other scheduling time information within the same component still valid). If all scheduling time information in the component are invalid, the entire Time Filter is considered not matching.</t>
          </li>
          <li>
            <t>The speaker installs the FlowSpec rule into the local policy. The rule is persistent in the BGP RIB until receiving a explicit withdrawn.</t>
          </li>
          <li>
            <t>The forwarding plane evaluates packet arrival time against the scheduling time component.</t>
          </li>
          <li>
            <t>Other FSv2 filter families in the same NLRI are AND'ed with the Time Filter result.</t>
          </li>
        </ul>
      </section>
      <section anchor="matching-procedures">
        <name>Matching Procedures</name>
        <t>A packet matches this FlowSpec rule if and only if:</t>
        <ul spacing="normal">
          <li>
            <t>All non-Time filter families match; AND</t>
          </li>
          <li>
            <t>At least one valid Scheduling Time Information in the Scheduling time Component matches the packet arrival UTC time.</t>
          </li>
          <li>
            <t>When the time windows of a scheduling time component expire, the filter will stop matching incoming packets. The expiration will NOT trigger automatic BGP withdrawal until the corresponding explict withdrawal is received.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <t>All headend nodes executing scheduling FlowSpec rules with a time filter <bcp14>MUST</bcp14> be synchronized to a common UTC time source. Synchronization loss may cause unexpected action execution, even leading to packet loss.</t>
      <t>The controller originating these FlowSpec NLRI is responsible for converting operator local-time schedules into UTC epoch timestamps. Forwarding nodes only process UTC timestamps and have no awareness of local time zones.</t>
      <t>A large number of time filters will increase forwarding-plane matching state and CPU overhead for time-window evaluation. Operators <bcp14>SHOULD</bcp14> limit the numbers of time filters on device.</t>
    </section>
    <section anchor="compatibility">
      <name>Compatibility</name>
      <t>According to the description in <xref section="3.2" sectionFormat="of" target="I-D.ietf-idr-fsv2-ip-basic"/>, BGP speakers that implement FSv2 but do NOT support the Time Filter Family or the Scheduling Time Component will check the syntax, but do not handle the semantic meaning unknown filter component.</t>
      <t>Existing FSv2 NLRIs without the time filter family are unaffected by this extension.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>BGP Flow Specification inherits the security properties of BGP, including risks of route hijacking, malicious NLRI injection, and tampering of flow rules. The extensions defined in this document add time-based matching criteria to FlowSpec rules and do not introduce fundamentally new security classes of threats. Existing security best practices for BGP FlowSpec <xref target="RFC8955"/> and <xref target="I-D.ietf-idr-fsv2-ip-basic"/> remain fully applicable.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>IANA is requested to create a new registry named "Flow Specification v2 Time Component Types". Within this registry, IANA is requested to assign type value 100 for the Scheduling Time Component:</t>
      <table>
        <thead>
          <tr>
            <th align="left">Type</th>
            <th align="left">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">0</td>
            <td align="left">Reserved</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">1-99</td>
            <td align="left">Unassigned</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">100</td>
            <td align="left">Scheduling Time Component</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
      </table>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC8955" target="https://www.rfc-editor.org/info/rfc8955" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8955.xml">
          <front>
            <title>Dissemination of Flow Specification Rules</title>
            <author fullname="C. Loibl" initials="C." surname="Loibl"/>
            <author fullname="S. Hares" initials="S." surname="Hares"/>
            <author fullname="R. Raszuk" initials="R." surname="Raszuk"/>
            <author fullname="D. McPherson" initials="D." surname="McPherson"/>
            <author fullname="M. Bacher" initials="M." surname="Bacher"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute (intra-domain and inter-domain) traffic Flow Specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix.</t>
              <t>It also specifies BGP Extended Community encoding formats, which can be used to propagate Traffic Filtering Actions along with the Flow Specification NLRI. Those Traffic Filtering Actions encode actions a routing system can take if the packet matches the Flow Specification.</t>
              <t>This document obsoletes both RFC 5575 and RFC 7674.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8955"/>
          <seriesInfo name="DOI" value="10.17487/RFC8955"/>
        </reference>
        <reference anchor="RFC8956" target="https://www.rfc-editor.org/info/rfc8956" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8956.xml">
          <front>
            <title>Dissemination of Flow Specification Rules for IPv6</title>
            <author fullname="C. Loibl" initials="C." role="editor" surname="Loibl"/>
            <author fullname="R. Raszuk" initials="R." role="editor" surname="Raszuk"/>
            <author fullname="S. Hares" initials="S." role="editor" surname="Hares"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>"Dissemination of Flow Specification Rules" (RFC 8955) provides a Border Gateway Protocol (BGP) extension for the propagation of traffic flow information for the purpose of rate limiting or filtering IPv4 protocol data packets.</t>
              <t>This document extends RFC 8955 with IPv6 functionality. It also updates RFC 8955 by changing the IANA Flow Spec Component Types registry.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8956"/>
          <seriesInfo name="DOI" value="10.17487/RFC8956"/>
        </reference>
        <reference anchor="RFC4760" target="https://www.rfc-editor.org/info/rfc4760" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4760.xml">
          <front>
            <title>Multiprotocol Extensions for BGP-4</title>
            <author fullname="T. Bates" initials="T." surname="Bates"/>
            <author fullname="R. Chandra" initials="R." surname="Chandra"/>
            <author fullname="D. Katz" initials="D." surname="Katz"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="January" year="2007"/>
            <abstract>
              <t>This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, L3VPN, etc.). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4760"/>
          <seriesInfo name="DOI" value="10.17487/RFC4760"/>
        </reference>
        <reference anchor="I-D.ietf-idr-fsv2-ip-basic" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-fsv2-ip-basic-10" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-idr-fsv2-ip-basic.xml">
          <front>
            <title>BGP Flow Specification Version 2 - for Basic IP</title>
            <author fullname="Susan Hares" initials="S." surname="Hares">
              <organization>Huawei</organization>
            </author>
            <author fullname="Donald E. Eastlake 3rd" initials="D. E." surname="Eastlake">
              <organization>Independent</organization>
            </author>
            <author fullname="Jie Dong" initials="J." surname="Dong">
              <organization>Huawei Technologies</organization>
            </author>
            <author fullname="Chaitanya Yadlapalli" initials="C." surname="Yadlapalli">
              <organization>ATT</organization>
            </author>
            <author fullname="Sven Maduschke" initials="S." surname="Maduschke">
              <organization>Verizon</organization>
            </author>
            <author fullname="Jeff Haas" initials="J." surname="Haas">
              <organization>HPE</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>BGP flow specification version 1 (FSv1), defined in RFC 8955, RFC 8956, and RFC 9117, describes the distribution of traffic filter policy (traffic filters and actions) distributed via BGP. During the deployment of BGP FSv1 a number of issues were detected, so version 2 of the BGP flow specification (FSv2) protocol addresses these issues. In order to provide a clear demarcation between FSv1 and FSv2, a different NLRI encapsulates FSv2. The IDR WG requires two implementation. Early feedback on implementations of FSv2 indicate that FSv2 has a correct design direction, but that breaking FSv2 into a progression of documents would aid deployment of the draft (basic and adding user ordered actions). This document specifies the basic FSv2 NLRI with user ordering of filters added to FSv1 IP Filters and FSv2 actions.</t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-idr-fsv2-ip-basic-10"/>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC4271" target="https://www.rfc-editor.org/info/rfc4271" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4271.xml">
          <front>
            <title>A Border Gateway Protocol 4 (BGP-4)</title>
            <author fullname="Y. Rekhter" initials="Y." role="editor" surname="Rekhter"/>
            <author fullname="T. Li" initials="T." role="editor" surname="Li"/>
            <author fullname="S. Hares" initials="S." role="editor" surname="Hares"/>
            <date month="January" year="2006"/>
            <abstract>
              <t>This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol.</t>
              <t>The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced.</t>
              <t>BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths.</t>
              <t>This document obsoletes RFC 1771. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4271"/>
          <seriesInfo name="DOI" value="10.17487/RFC4271"/>
        </reference>
        <reference anchor="RFC4360" target="https://www.rfc-editor.org/info/rfc4360" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4360.xml">
          <front>
            <title>BGP Extended Communities Attribute</title>
            <author fullname="S. Sangli" initials="S." surname="Sangli"/>
            <author fullname="D. Tappan" initials="D." surname="Tappan"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="February" year="2006"/>
            <abstract>
              <t>This document describes the "extended community" BGP-4 attribute. This attribute provides a mechanism for labeling information carried in BGP-4. These labels can be used to control the distribution of this information, or for other applications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4360"/>
          <seriesInfo name="DOI" value="10.17487/RFC4360"/>
        </reference>
      </references>
    </references>
    <?line 215?>



  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+1azXIbxxG+o4rvMKEOJm0AASDasij/0aRo0UWJDEnZZadS
rsHuABhxsbOe2SUEUXLlmnNeIIc8SR7FT5Kve2YXuwAIyRU7ByeUqgDMb0//
fN3TPZ1OZ6uV6zxR++LLr87FcWJm4jJTkR7pSObapOIbZR19DsTjl7lK6bsT
I2PFZTRRcZHodLzVksOhVTdhjcubQaMzNlEqp9ghtnKUd7TKRx0d287I3Qw6
rhrY6fW2WmboTKJy5fa3WkUWS/+NPvEBitTY2Pm+cHm81XLFcKodEXQ1z7D8
yeOr463WVktndl/ktnD5oNd72BuAPKvkvvhKpcrKZKs1M/Z6bE2RYc7RxVbr
Ws3RFONXmiubqrxzRJTSWrLIJ8ZibwFGCaFTty9Ou+L7iaSTCeEPdqoXLcaO
ZapfMfP2xZNCzpSmdjWVOtkXr2hcou/v7X0x4b5uZKbUbw0JQcU6N5Z+u9wq
lYOlSv8I7ogLI2Nqj3Q+59YX2m8YmSLNiSmHE53KBqVXRKkpFoReaZlamVat
byXWFLmf0qR2scX3XZx+scH3E5X+iBnj0NrcgCkUT81QJ6q2TaJfldO+iGjI
lEes7PV1VxyZOt+/1qpqectRXmjVjTG0cY6tVmrsFFNuSL2gOemo8bvb7dJH
p9MRcgiByIiVYqt1h63IBG0OEklv1JyENqIxrj7GCZnGQjpnIg11jqGocoRO
gbWp+4+2SJQTuRGZskSNiPVopKxK83KIGEqHidivnBtNJNGmrHa5jlwXpkrf
QEA5YqQTdAu/OFMQ1tKpN1hLfEqFwl4RnZ+2z1Re4EjzR9grUiJWCTos0WxE
PlFiomSs0rjNP1aXhtXRKlOZEvEEGYGarhBPzExhrbZwZqqEwTAJvXdipt1k
8+FpnZKjzF9slC9acj1VLLSriXYC0FNMabYi7IrdAqBmOp8IKRbwwzMhumlm
mF4QAU2IJnw4aa2+kYkfY0Yik9G1ysHoLytR0HbV7HadPyKCxb3jgSptyGsj
aVdXaeJUxzGZz1brHgGWNXHBK4nbe5p+vqGu29s/XBwffvzwww/fvGGhVA0f
oSFWI50qZsbt7edo3xs86KN9jUrvgFv93baYTTR48aspeLdyN7RdqTxQGJVG
JsYsko9OmY1Pz3+4eHxw+OSHZ6cXJ7w6Wp4/q7fludXDAs4inHPvwUe9N2+6
4mBBRl0ry02wATs1+n5optMiBbg2V2Pu3OfVtlqkOdjgpHPUbXoxnXVglDoC
DzUxQHjfRapC/GsLDXnHsVXOkXHjUHBchSJOJgkMDvvHhWUtnJChZYmZs96G
BfjUmTU3OsakUaJe6mGixNXpNx0PBnwizO8Kkv7/zR//TqA9OobRwqGTx3fC
FaTCTpycwyRh0eDIEIY8hMlWg9oVz24kRjgiRYO1EXGiK65CpyvsGJ1BaDFc
zBwsAPHwmDjHTj7P/BQx6O33ej//9e+DAT53gSlzkYBxdEqYERZhM8P/SNmc
ZAAwuoZ9XAF/dK7HpEZMeKbkdSeAVDmvvYZ3MUkp95wtz2JSdEjSgVR68cp8
4uAzsRt28RIMCutU0EjmbtsjJQY4zDKJjogpVv1Y6KAKQ8BjkRtym/7EKpVQ
zpiVIdYu/KiERLMqQPu9obTYUd1xtx2EUDdBlkw5ltm/GxT13j1x4flJTHDi
FHFQIcfK80cJhKeC4lMntp8+v7zabvtP8eyMv188/tPzk4vHR/T98snB6Wn1
pRVGXD45e356tPi2mHl49vTp42dHfjJaRaOptf304Dv0kCC3z86vTs6eHZxu
Cx34WImNLN0rgqYAOrOKAde1AFYRoNQj7ZeH5//6R38vIPSg338ItAxuqf9g
Dz9miAL9biaFHvmfENG8JTNov6VVoGGQVKZzmUA3YcxuYmYphGhVt9V6/8/E
mb/si0+GUdbf+yw00IEbjSXPGo3Ms9WWlcmeiWua1mxTcbPRvsTpJr0H3zV+
l3yvNX7yeULuu9P/+PPPWkGHKl96s/GixrB4e3upfMhwv9vv9slUNvo0dl8+
ZgDaAjJc6ZgGpWcZySlBIGBPQSw6jZIiLt0ZTLJQwMEeRQV6nBK0kDdAF1vq
6hJAP3T6WJx2qg/TpciHCifmMP2nn35CpN8Tq3/9NW2DNW33eX4ffffFnvhQ
fCQeiI/Fw1/SttX6oPMf/ttqvfZMPfZHPV5wRHxK/BOvQeuxW7A9jEhUOgZQ
ov9XoqL+V6fosAJehB4AO/KRhO+7jRm/DhUs1dt9cc+qUSc3nZEeQ5ycrPh0
+3i9boRoZvvNqm9Z6G+qZg3dXfIHdzqbdqW2PHtVd7viJPfuiOIGdj4Nn8TX
OsSW47GqOZPgYbol3Htz6UPcmhwttp/6CFX6yJHVwQ8q6bmTZF70cYgNASDL
AxcC/OAzGnq51F9diOlO7Ze2mu6ZUhTOu//AgeBr2xScUBhTB4raqldLqy5b
+jKBtaFs+VUIoQnGaskjGt2pjeZ4nX3r8u4ntSVv721aopTIu5PHwCQJdvmi
9LtDp5KZ4FPs0UicltjDv48TOXb8/fz1JfVfIG60NxDYb4ROjb/LXCLyZSnf
/fc/QMVjhFC8/85RYVk7d9cP/P1TcUxXFdyO52LnLCMaZPJfp+JCRYVF3I9L
9CElazdR8pv5zsEa37kBGr0Lfb9u8Pvi484QkSD7HsTeokg1eCs0rk85obL1
lxxOPRR0G1USN7OAmapM6ciVYIKcANDT+zTKnwA8I07aDOfe35Z5IgPnqVO6
73Y9eT7yAWUClMH7hEiI4gLM82zPN8M2Isl5Hq6j73sAK9frikO/AmIsvpIM
uJkvPD6eiB+F1AmtXfXZAHreu5W/qJ9cRJHEdFdyiq+vPb7wICw2dnFguH1F
N0gmitTifXEuds45FRHc0e6+6LM4RqAYp4g5/xZC7uoe5s8Y2OFTGZ5y7b3v
yUicf9pv17spaPJnI2pw+WY4C9GOSvy9HndlujMvWsNSvV+2VJYUFCjEAR+8
CtQOfSl2SgXkuGfjoStFswt787cJkHZZklaNmsBPs1Ap/YOAJZeY8MjrWwUa
dNZl8/W0O1HeLEmYGQkZXSFl6YphBxFy2Lm/ZudpkeQ6q4ilM5Q0uF9MxIKA
oMULF7QvPtqrW61VYWTJtbSYDmGMnPhB7IYlnWbOoU9lJppwVFsGXj4Erctx
kdfzoS8nIa/KyaQCffG1TAtp56L/8EGPkiY9yomJ51eHgdw1nqJJNzOSZR60
Fct6DWoSBp3cQNVijV5jDZ8MdHeww4xGZKoja6Y8oubeSTBNAipNJpNbJiAg
zMIjmdIP7Iv7g8ZpF/eV9UQNVT5TKl2WBkaQNleaVqoUU7o6ltdWL/NqXEBi
z5ZgXoGGmlExutClhthMCZlKc/2iFAkHChoLrjUYNs3AmhUlv4tD7cD2eanF
uckp01vxCWqucu0vVgIOT6iXcgpza9OGAXkH7WXYyJQEguczDQIKV+FKdemo
RPeuxxLfsE8DQT0xVTJ1YRPyQITBCpdGOvrTEg0anNx0c6E8sonALk6KbciQ
MgxV629aslZycXKqlhcix3Z28R55NZxOpnM/YAY1MbPq2svov3r19azmLYP3
DxP8LU2cWxOBMHCvyoiSByQ6m13fThSdlzLEjjLiVNXwzpIcCV/MuSQUrqG0
gFw59SKNEc5bJyzkVHb4nj3o9Xb5Ftchm8RpNL9JaEQ2d4UVDBZ37uzdQ8pL
vstKC0GEFDNQGtqNaIvaLj2yce40mEzwEG1CV97757/904MX/doVIWdJkYhO
fIyD2A1YSLmGHYM97Ua6ltVlQSACQIACn2yXUZcw4hcdkXRNe960A7Dn2jbl
xJl8MCDmmlRq8ibQdtgJlTrCdpUkrhlOWo+RoZ5FQWfiaxzzELlxP9eASkYH
Ukn/Lk6+RAiMswYN9LqmXmZUJMmZP7GVs7RGDo48A4NpZJZIILUiOGONWmM0
Qo4pk5K/Jccj/PpnLLGVpCx5prqYfMEUvDx4dvReKLSu2ACMDYhRZlCeBr4u
meJBSfPC9sGrJeaOFvl8PQqWdAB1SE3auVrOoBGtvNgjoi4MzqleRomkVHmd
2ghiq3aXN+1uA1AhIFkUEDuCoabKUnucY1zeBLcQPxTVK2042oysweUmqxSU
bXfKWlCWqDhiormlcWEO+ZQyXViV2Fj1St0C0V4DvfnAdzrQwfrl9TCvD/X5
RMLKOMDuGVcPPVwcBmPyVXwWMGgoq2OpocqzegkPzaFjjQNLVfxQs6unR8sg
1c3TaGJNql/53KEkxk1x3JLzwpnCUhhyWY30/EiMc+zzIlk4OGdELZmvUvr0
aUkZlUTVDeRGNVYWjymlTEt4W7liZtFbiSShcCFcKoO/dzWAYGNhthFfHRfd
KejhBxC+vlcWYD18+AJtGVI4Dy50Oh8NcxY4RyTio5ISCzxz2UgyMjGcteSI
H81GNJE3CNfANUxTKQ2CLnrQ4l1fQQO9Pz0QibTjetxYk4bzygUVtLCrOiZ1
PCZVWoq9cx86Hp4/FwYnJm3wwTXlSoPrDxjG98mzqhwd3MuivuyJcSvUQHix
ukHIFXSSTBWrDQEH+ZxPE0GzS2H69xFUVsxKe6+XswbvUMyqxQ4EAxSNUWjI
VQKGz2GB8Nuw+bkiy4zN7woSQv79bi/PrEZvdO0ReI6o5GW73IGc1gT8Tfx1
y6mpTMnEKVSkxYr0OqWM8nKhott45FEFPd72TJHfVVsj2C9SyY88ymSDdr7s
TvXCIIFLCsPpJcwqJNzx8E2n8D2U/fDHCNOhyxlZiY9mMbVeGbTaXXO7BcG4
E+sXMFN0tKF/5EBN4YL5pS+8eH1pmOxB8X3ZjPzzo/CgyCNoVfksEw+r1erY
5y3Cy5lK26vKBrRs+WESvWTw4tLhxRVYW6SxpBX50QMVlaqDR4nkhz58G7J0
qag9yatGDWHc4BEBGAX8ZFaNR1Hr3nBtfHoUHvGMCiJIZoT/VNsJUj05eHaw
RqLcrP2TDhDkgZmggUyfj2XVGKTj+k6PLmOxvUb+UMDl8JYqwdtd8W0ZJfIW
fqG2WLuprw7X61tUBBu9zcY4qHjNG4rX4qiGDa9xi+AHF5DWa4zp8F/46Kz+
ojG+UPO6WbcQzVIij+t3Hj5Ez/O0KmrfMc7Xbe+GiDWz/D967Efvk8rf/t+/
AV1Oc86zLQAA

-->

</rfc>
