IS-IS
Extensions for Advertising iFIT Node Capability Huawei156 Beiqing Rd., Haidian DistrictBeijingChinalucy.liumin@huawei.comHuawei156 Beiqing Rd., Haidian DistrictBeijingChinawangyali11@huawei.comLink State Routing Working GroupThis 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 , 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.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 RFC 2119.iFIT provides a complete framework architecture and a reflection-loop
working solution for on-path flow telemetry . At present, there are a
family of emerging on-path flow telemetry techniques, including In-situ
OAM (IOAM) , PBT , IOAM Direct Export
(DEX) , Enhanced Alternate Marking (EAM) , 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.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.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 , IOAM Edge-to-Edge (E2E) Option-Type , IOAM DEX Option-Type and Enhanced Alternate Marking (EAM) Option-Type . So iFIT Option Types SHOULD be carried in iFIT node capability advertisment.The IS-IS Extensions for Advertising Router Information TLV named
IS-IS Router CAPABILITY TLV , 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 .According to the format of IS-IS Router CAPABILITY TLV , 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.The iFIT Node-capability Sub-TLV has the following format: Type: To be assigned by IANALength: A 8-bit field that indicates the length of the value
portion in octets. iFIT Option Type-enabled Flag: A 2-octet field that is defined as following:Where: 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 .i-Flag: iOAM Incremental Trace Option Type-enabled flag. If i bit is set (1), the router is capable of iOAM Incremental Tracing .d-Flag: iOAM DEX Option Type-enabled flag. If d bit is set (1), the
router is capable of iOAM DEX .e-Flag: iOAM E2E Option Type-enabled flag. If e bit is set (1), the router is capable of iOAM E2E processing . m-Flag: Enhanced Alternative Marking enabled flag. If m bit is set (1), then the router is capable of processing Enhanced Alternative Marking packets .Reserved: Must be set to zero upon transmission and ignored upon receipt.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.Note to RFC Editor: this section may be removed on publication as an RFC.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.TypeDescriptionTBDiFIT Node CapabilityThis document introduces new sub-TLVs for the existing IS-IS Router
capability TLV. It does not introduce any new security risks to ISIS.
IS-IS Extensions for Advertising Router InformationIS-IS Extensions for Traffic EngineeringIn-situ Flow Information Telemetry FrameworkData Fields for In-situ OAMPostcard-based On-Path Flow Data TelemetryIn-situ OAM Direct ExportingEnhanced Alternate Marking Method