IGP Extensions for In-situ Flow Information Telemetry (IFIT) Capability Advertisement
draft-wang-lsr-igp-extensions-ifit-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Yali Wang , Tianran Zhou , Fengwei Qin , Huanan Chen , Ran Pang | ||
Last updated | 2021-01-29 (Latest revision 2020-07-28) | ||
Replaces | draft-wang-lsr-ifit-node-capability-advertisement | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document extends Node and Link Attribute TLVs to Interior Gateway Protocols (IGP) to advertise supported In-situ Flow Information Telemetry (IFIT) capabilities at node and/or link granularity. An ingress router cannot insert IFIT-Data-Fields for packets going into a path unless an egress router has indicated via signaling that it has the capability to process IFIT-Data-Fields. In addition, such advertisements would be useful for ingress routers to gather each router's IFIT capability for achieving the computation of Traffic Engineering (TE) paths or loose TE paths that be able to fulfill the visibility of on-path OAM data.
Authors
Yali Wang
Tianran Zhou
Fengwei Qin
Huanan Chen
Ran Pang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)