Re: [OPSAWG] I,Scope of FIT Capability: a node or a link?

Tianran Zhou <zhoutianran@huawei.com> Mon, 06 April 2020 14:48 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B854B3A093B; Mon, 6 Apr 2020 07:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 u0_Py7Mpg8SS; Mon, 6 Apr 2020 07:48:19 -0700 (PDT)
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 92B3E3A091A; Mon, 6 Apr 2020 07:48:19 -0700 (PDT)
Received: from lhreml727-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 50AE7D03BCED2ABC0E36; Mon, 6 Apr 2020 15:48:18 +0100 (IST)
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by lhreml727-chm.china.huawei.com (10.201.108.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 6 Apr 2020 15:48:17 +0100
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by nkgeml705-chm.china.huawei.com (10.98.57.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 6 Apr 2020 22:48:14 +0800
Received: from nkgeml707-chm.china.huawei.com ([10.98.57.157]) by nkgeml707-chm.china.huawei.com ([10.98.57.157]) with mapi id 15.01.1713.004; Mon, 6 Apr 2020 22:48:14 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Greg Mirsky <gregimirsky@gmail.com>, "draft-wang-lsr-ifit-node-capability-advertisement@ietf.org" <draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "draft-song-opsawg-ifit-framework@ietf.org" <draft-song-opsawg-ifit-framework@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: I,Scope of FIT Capability: a node or a link?
Thread-Index: AdYMISbJWe8h8bS0Rki6HVv232b2lQ==
Date: Mon, 06 Apr 2020 14:48:14 +0000
Message-ID: <4da3d82b084343bfa18de192b1f390b1@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.220.197]
Content-Type: multipart/alternative; boundary="_000_4da3d82b084343bfa18de192b1f390b1huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/XMd7rP9VAfk7ddTKXYvtzlcgehY>
Subject: Re: [OPSAWG] I,Scope of FIT Capability: a node or a link?
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2020 14:48:22 -0000

Hi Greg,

Thanks very much for your interest on both IFIT framework and IFIT capability draft. And thanks for your review comments.
Your perspective on both drafts are correct.
On the node or link capability, thanks for your suggestion.
I agree with both you and Jeff. The link capability can make the information more clear and accurate for different scenarios.
Why we only considered the node capability? That’s the trade off to reduce complexity. We just want to start from simple cases.
If the WG think link capability is necessary, we would like to add link capabilities to the update.

Cheers,
Tianran

发件人: Greg Mirsky [mailto:gregimirsky@gmail.com]
发送时间: 2020年4月5日 10:33
收件人: draft-wang-lsr-ifit-node-capability-advertisement@ietf.org; lsr@ietf.org; draft-song-opsawg-ifit-framework@ietf.org; opsawg@ietf.org
主题: I,Scope of FIT Capability: a node or a link?

Dear All,
I've read these two drafts with interest. In light of the discussion on the LSR WG list, I've been thinking about the scenarios where IFIT is being used.
draft-song-opsawg-ifit-framework defines the overall IFIT architecture that, as I understand it, applicable to different methods of collecting and transporting telemetry information. draft-wang-lsr-ifit-node-capability-advertisement is based on the view that IFIT is a node-wide capability advertised as a binary flag for each listed method of collecting telemetry information (Option-Type enabled Flag). On-path telemetry collection is performed in the fast path, i.e., at a link layer. But a node might include ports with different capabilities. How such a heterogeneous, IFIT-wise, node will advertise IFIT Capability? To better use available resources for telemetry information collection, it might be helpful to advertise IFIT as a capability of a link, not of a node?
What do you think?

Regards,
Greg