<?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-liu-lsr-isis-ifit-node-capability-02"
     ipr="trust200902">
  <front>
    <title abbrev="draft-liu-lsr-isis-ifit-node-capability-02">IS-IS
    Extensions for Advertising IFIT Node Capability </title>

    <author fullname="Min Liu" initials="M." role="editor" surname="Liu">
      <organization>Huawei</organization>

      <address>
        <postal>
          <street>156 Beiqing Rd., Haidian District</street>

          <city>Beijing</city>

          <region/>

          <code/>

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

        <phone/>

        <facsimile/>

        <email>lucy.liumin@huawei.com</email>

        <uri/>
      </address>
    </author>

    <author fullname="Yali Wang" initials="Y." role="editor" surname="Wang">
      <organization>Huawei</organization>

      <address>
        <postal>
          <street>156 Beiqing Rd., Haidian District</street>

          <city>Beijing</city>

          <region/>

          <code/>

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

        <phone/>

        <facsimile/>

        <email>wangyali11@huawei.com</email>

        <uri/>
      </address>
    </author>
	
	<author fullname="Ran Pang" initials="R." role="editor" surname="Pang">
      <organization>China Unicom</organization>

      <address>
        <postal>
          <street>9 Shouti South Rd., Haidian District</street>

          <city>Beijing</city>

          <region/>

          <code/>

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

        <phone/>

        <facsimile/>

        <email>pangran@chinaunicom.com</email>

        <uri/>
      </address>
    </author>

    <date day="09" month="March" year="2020"/>

    <workgroup>Link State Routing Working Group</workgroup>

    <abstract>
      <t>This document defines a way for an Intermediate System to 
	  Intermediate System (IS-IS) routers to advertise IFIT(in-situ Flow
      Information Telemetry) capabilities. This document extends a new optional sub-TLV in
      the IS-IS Router CAPABILITY TLV <xref target="RFC7981"/>, which allows a
      router to announce its IFIT node capabilities within an IS-IS level or
      the entire routing domain. Such advertisements enable IFIT applications in the network domain.</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>IFIT provides a complete framework architecture and a reflection-loop
      working solution for on-path flow telemetry <xref
      target="I-D.song-opsawg-ifit-framework"/>. At present, there are a
      family of emerging on-path flow telemetry techniques, including In-situ
      OAM (IOAM) <xref target="I-D.ietf-ippm-ioam-data"/>, PBT <xref
      target="I-D.song-ippm-postcard-based-telemetry"/> , IOAM Direct Export
      (DEX) <xref target="I-D.ioamteam-ippm-ioam-direct-export"/> , Enhanced Alternate Marking (EAM) <xref target="I-D.zhou-ippm-enhanced-alternate-marking"/>, etc. 
	  IFIT is a solution focusing on network domains. The "network domain" consists of a set of network devices
      or entities within a single administration. For example, a network
      domain can be one or more IGP routing domains. 
	  The family of emerging on-path flow telemetry techniques may be selectively or partially implemented in different vendors' devices as an emerging feature for various use cases of application-aware network operations.
	  Hence, in order to enable IFIT applications in an operational network domain, IFIT node capabilities SHOULD be advertised by every Intermediate System to Intermediate System (IS-IS) router in the network domain.</t>

      <section title="IFIT Domain">
        <t>IFIT is expected to be deployed in a specific domain referred as the IFIT domain. An IFIT domain may cross multiple 
		network domains. One network domain may consists of multiple IFIT domain. 
		Within the IFIT domain, the IFIT data
        fields of flow information head MAY be updated by network nodes that the packet traverses.</t>
      </section>

      <section title="IFIT Node Capability Information">
        <t>Each IFIT node is configured with a node-id which uniquely identifies a node within the associated IFIT domain. 
		To accommodate the different use cases or requirements of in-situ flow
        information telemetry, IFIT data fields updated by network nodes fall into different categories
        which are referred as different IFIT option types, including IOAM Trace Option-Types <xref target="I-D.ietf-ippm-ioam-data"/>, IOAM Edge-to-Edge (E2E) Option-Type <xref target="I-D.ietf-ippm-ioam-data"/>, IOAM DEX Option-Type <xref target="I-D.ioamteam-ippm-ioam-direct-export"/> and Enhanced Alternate Marking (EAM) Option-Type <xref target="I-D.zhou-ippm-enhanced-alternate-marking"/>. So IFIT Option Types SHOULD be carried in IFIT node capability advertisment.</t>
      </section>
    </section>

    <section title="Advertisement of the IFIT Node Capabilities in ISIS">
      <t>The IS-IS Extensions for Advertising Router Information TLV named
      IS-IS Router CAPABILITY TLV <xref target="RFC7981"/>, which allows a router to announce its capabilities within an IS-IS level or the entire routing domain, has been chosen for IFIT node capabilities advertisement. IS-IS Router CAPABILITY TLV is formed of multiple sub-TLVs <xref target="RFC5305"/>.</t>

      <section title="IFIT Node Capability Sub-TLV">
        <t>According to the format of IS-IS Router CAPABILITY TLV <xref target="RFC7981"/>, the IFIT Node Capability sub-TLV is composed of three fields, a
        one-octet Type field, a one-octet Length field, and zero or more
        octets of Value. The Type field indicates the type of items in the
        Value field. The Length field indicates the length of the Value field
        in octets. The Value field indicates the IFIT Node Capability, which is a 2-octet IFIT Option Type-enabled Flag.</t>

        <t>The IFIT Node-capability Sub-TLV has the following format: </t>

        <t><figure align="center"
            title="Fig. 1 IFIT Node Capability Sub-TLV Format">
            <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
    +---------------+---------------+-------------------------------+
    |      Type     |    Length     |IFIT Option Type-enabled Flag  |     
    +---------------+---------------+-------------------------------+

]]></artwork>
          </figure></t>

        <t>Type: To be assigned by IANA</t>

        <t>Length: A 8-bit field that indicates the length of the value
        portion in octets. </t>
		
        <t>IFIT Option Type-enabled Flag: A 2-octet field that is defined as following:</t>

        <t><figure>
            <artwork><![CDATA[
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
     +-------------------------------+
     |p|i|d|e|m|       Reserved      |  
     +-------------------------------+

]]></artwork>
          </figure>Where: </t>

        <t>p-Flag: iOAM Pre-allocated Trace Option Type-enabled flag. If p bit is set (1), the router is capable of iOAM Pre-allocated Trace <xref target="I-D.ietf-ippm-ioam-data"/>.</t>

        <t>i-Flag: iOAM Incremental Trace Option Type-enabled flag. If i bit is set (1), the router is capable of iOAM Incremental Tracing <xref target="I-D.ietf-ippm-ioam-data"/>.</t>

        <t>d-Flag: iOAM DEX Option Type-enabled flag. If d bit is set (1), the
        router is capable of iOAM DEX <xref
        target="I-D.ioamteam-ippm-ioam-direct-export"/>.</t>

        <t>e-Flag: iOAM E2E Option Type-enabled flag. If e bit is set (1), the router is capable of iOAM E2E processing <xref
        target="I-D.ietf-ippm-ioam-data"/>. </t>

        <t>m-Flag: Enhanced Alternative Marking enabled flag. If m bit is set (1), then the router is capable of processing Enhanced Alternative Marking packets <xref
        target="I-D.zhou-ippm-enhanced-alternate-marking"/>.</t>
		
		<t>Reserved: Must be set to zero upon transmission and ignored upon receipt.</t>

        <t>An IFIT node SHALL be capable of more than one IFIT option types. So for this case, IFIT Option Type-enabled Flag bitmap SHOULD has more than one bit being set.</t>
      </section>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t/>

      <t>Note to RFC Editor: this section may be removed on publication as an RFC.</t>

      <section title="Sub-TLVs for the IS-IS Router CAPABILITY TLV (242)">
        <t>This document makes the following registrations for a Sub-TLV type of the new Sub-TLV proposed in Section 3 of this document from the "Sub-TLVs for TLV 242 (IS-IS Router CAPABILITY TLV)" registry.</t>

        <texttable align="center">
          <ttcol>Type</ttcol>

          <ttcol>Description</ttcol>

          <c>TBD</c>

          <c>IFIT Node Capability</c>
        </texttable>
      </section>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>This document introduces new sub-TLVs for the existing IS-IS Router
      capability TLV. It does not introduce any new security risks to ISIS.
      </t>
    </section>

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

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

      <reference anchor="RFC7981"
                 target="https://www.rfc-editor.org/info/rfc7981">
        <front>
          <title>IS-IS Extensions for Advertising Router Information</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>

      <reference anchor="RFC5305"
                 target="https://www.rfc-editor.org/info/rfc5305">
        <front>
          <title>IS-IS Extensions for Traffic Engineering</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>
    </references>

    <references title="Informative References">
      <reference anchor="I-D.song-opsawg-ifit-framework"
                 target="https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/">
        <front>
          <title>In-situ Flow Information Telemetry Framework</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>

      <reference anchor="I-D.ietf-ippm-ioam-data">
        <front>
          <title>Data Fields for In-situ OAM</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>

      <reference anchor="I-D.song-ippm-postcard-based-telemetry"
                 target="https://datatracker.ietf.org/doc/draft-song-ippm-postcard-based-telemetry/">
        <front>
          <title>Postcard-based On-Path Flow Data Telemetry</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>

      <reference anchor="I-D.ioamteam-ippm-ioam-direct-export"
                 target="https://datatracker.ietf.org/doc/draft-ioamteam-ippm-ioam-direct-export/">
        <front>
          <title>In-situ OAM Direct Exporting</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>

      <reference anchor="I-D.zhou-ippm-enhanced-alternate-marking"
                 target="https://datatracker.ietf.org/doc/draft-zhou-ippm-enhanced-alternate-marking/">
        <front>
          <title>Enhanced Alternate Marking Method</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>
    </references>
  </back>
</rfc>
