[Lsr] Overview of two new drafts about IFIT node capability advertisement in ISIS and OSPF
wangyali <wangyali11@huawei.com> Sun, 01 March 2020 12:59 UTC
Return-Path: <wangyali11@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5C13A0E90 for <lsr@ietfa.amsl.com>; Sun, 1 Mar 2020 04:59:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IkMNcarF7x9l for <lsr@ietfa.amsl.com>; Sun, 1 Mar 2020 04:59:55 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06F1D3A094F for <lsr@ietf.org>; Sun, 1 Mar 2020 04:59:55 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id D175B96CBDFD96324B67 for <lsr@ietf.org>; Sun, 1 Mar 2020 12:59:51 +0000 (GMT)
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 1 Mar 2020 12:59:51 +0000
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.105]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0439.000; Sun, 1 Mar 2020 20:59:48 +0800
From: wangyali <wangyali11@huawei.com>
To: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Overview of two new drafts about IFIT node capability advertisement in ISIS and OSPF
Thread-Index: AdXvyTBRkXWM/5XkT0qPNc3dgpAoMw==
Date: Sun, 01 Mar 2020 12:59:47 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404DA66CE@dggeml524-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.66.87]
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F404DA66CEdggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/-SyLXxWLcaLI2NHC5ubgxISfGHk>
Subject: [Lsr] Overview of two new drafts about IFIT node capability advertisement in ISIS and OSPF
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Mar 2020 12:59:58 -0000
Hello all, I’m Yali. I respectively submitted two drafts (draft-liu-lsr-isis-ifit-node-capability-00 and draft-wang-lsr-ospf-ifit-node-capability-00) about extensions to ISIS and OSPF for advertising IFIT node capability. Following is an overview. Overview: IFIT provides a complete framework architecture and a reflection-loop working solution for on-path flow telemetry [I-D.song-opsawg-ifit-framework]. 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 a network domain, IFIT node capabilities SHOULD be advertised by every router in the network domain. 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. 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 [I-D.ietf-ippm-ioam-data], IOAM Edge-to-Edge (E2E) Option-Type [I-D.ietf-ippm-ioam-data], IOAM DEX Option-Type [I-D.ioamteam-ippm-ioam-direct-export] and Enhanced Alternate Marking (EAM) Option-Type [I-D.zhou-ippm-enhanced-alternate-marking]. So IFIT Option Types SHOULD be carried in IFIT node capability advertisement. Therefore, [draft-liu-lsr-isis-ifit-node-capability-00] extends a new optional sub-TLV in the IS-IS Router CAPABILITY TLV [RFC7981], named IFIT Node Capability sub-TLV, which allows a router to announce its IFIT node capabilities. And [draft-wang-lsr-ospf-ifit-node-capability-00] defines a new IFIT Node Capability TLV within the body of the OSPF RI Opaque LSA [RFC7770] to carry the IFIT node capabilities of the router. Please let me know if you have any comments. Best regards, Yali Wang