IETF Logo Mail Archive

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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 06 April 2020 15:06 UTC

Return-Path: <ginsberg@cisco.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 63DB03A0962; Mon, 6 Apr 2020 08:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.619
X-Spam-Level:
X-Spam-Status: No, score=-9.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=ErsQg3Wc; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=XNGST1BJ
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 SGc5p_-ot4Wa; Mon, 6 Apr 2020 08:06:18 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0BD93A0955; Mon, 6 Apr 2020 08:06:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17550; q=dns/txt; s=iport; t=1586185577; x=1587395177; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=/QPFHRiLDBpDueaJHSVdqka++pm1DM8f41eQScs9Ulc=; b=ErsQg3WcTrz69Oe5je1Cb1UAdvBoICja8OIzWVeprfez6Npy3GfHXSgo hXl3Tj0kown/yJiGSz3aMHMG6IuCRVNOzdm1nq02wk2rIK7fk1icpVy61 dpJvg85zhz4Yx0BiqxM/cqoyd3u4wUqbDiXJODf15qYHVDYHEqSMMWgE5 A=;
IronPort-PHdr: 9a23:+8db1BPp3SMT3h9GHg4l6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBj0LfjxZSEgE+xJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFAgAvRIte/5JdJa1mHQEBAQkBEQUFAYFpBgELAYEkLyQsBWxYIAQLKoQbg0UDimVOghGBAYhtiU+EYYEuFIEQA1QKAQEBDAEBLQIEAQGERAIXgjIkNgcOAgMBAQsBAQUBAQECAQUEbYVWDIVwAQEBAQMSEQoTAQE4DwIBBgIRAQMBASgDAgICHxEUAwYIAQEEARIIGoMFgX5NAy4BlEuQZwKBOYhidYEygn8BAQWFPQ0Lgg0JgTgBjDIagUE/gRFDghg1PoIegXY8NIJcMoIskQSGBIo2jnAsSAqCPZACgm2EWIJOiDiEXYwfjzeBUooQkEMCBAIEBQIOAQEFgVkNJYFXcBU7gmlQGA2OHYNzihwBOHSBKY4vAQE
X-IronPort-AV: E=Sophos;i="5.72,351,1580774400"; d="scan'208,217";a="746831066"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Apr 2020 15:06:15 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 036F6FCA015516 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 6 Apr 2020 15:06:15 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 6 Apr 2020 10:06:11 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 6 Apr 2020 10:06:11 -0500
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 6 Apr 2020 10:06:10 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=B4EEs0VnDjP/QF3N6nn05cbxs0vnpQCzTlBs9JhSn4CTDu7uKo43GlKLZBK2Jxbw8lOnxiP1hfqrhrtcAqbqWYjfzEHDeOUwoqswV9fHHbxfPSqgVQG0/6sVeaEm/3pKm7Yk70DHTF2W93mwG9up7ufaIu5ziY0cUU4IMx5pt0kJdKcXpI2bl7bowMCfjSqMHkM3ecf6Pzk0/zkXicHPmy6H3yIUIoDh8iAJeRACe6FtD+QNtkRr5gSD3PSZ06ZA4Xu40A6U08dbZlMWAeteDT0iSjZk1GHoV8VBZHzlMaqVS8pindxdU0NV6GxAaTjuDDnD+SJ5woZ8vqZ5AmjSpw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/QPFHRiLDBpDueaJHSVdqka++pm1DM8f41eQScs9Ulc=; b=OasbVhY4KNCcoElHeFJcxcfC2RA+b+Byi3sMA/78rLkjNZg678W8yA+3pcty9lGNT64DAQtO4V3CKHM2bykK2MkX9m62gcj+3QTHvoxVoZ6C7ZmFtVZJJjRaHTXGgz8c1HVY3O3s25HeToKdjxtQqKEGWFIXdXTqUHc8UBebEpdYbWQ/VMN+IwhtJPkApsLZn9pls5m8ZYSMzfOhL7BRW+G5bofB+7nUQf8H3pojlj8rLL8Zc9yTWAVYZhan9xsYSNIZL6EzVLlyNGbEdG8iUzZ2UOdxCZpOKutXfYPMBI7AMWKxSfo3agF3tt1Fk/gdJcBva4A29ta34tusjgxb9A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/QPFHRiLDBpDueaJHSVdqka++pm1DM8f41eQScs9Ulc=; b=XNGST1BJzRfvRii8Rsd6gw4GTvAYCHN+Fm/JMT3V0CWKZHvl3au+eroNKGEnTpdc8U29Gqt2e4c9uKCXFTnysyy418JRWJs6gUsYeCMzz6e0vM37upc+guscz0rOCw3ANCYfOcg+kUeKmHCTg3xl7eQ6cNLoLgYaYCarBUDETB0=
Received: from MW3PR11MB4619.namprd11.prod.outlook.com (2603:10b6:303:5b::15) by MW3PR11MB4572.namprd11.prod.outlook.com (2603:10b6:303:5e::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.19; Mon, 6 Apr 2020 15:06:10 +0000
Received: from MW3PR11MB4619.namprd11.prod.outlook.com ([fe80::b87d:76f6:5a2e:951c]) by MW3PR11MB4619.namprd11.prod.outlook.com ([fe80::b87d:76f6:5a2e:951c%3]) with mapi id 15.20.2878.017; Mon, 6 Apr 2020 15:06:10 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Tianran Zhou <zhoutianran@huawei.com>, 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: AdYMISbJWe8h8bS0Rki6HVv232b2lQAA0obA
Date: Mon, 06 Apr 2020 15:06:09 +0000
Message-ID: <MW3PR11MB4619DBDBD80BC52A92F51176C1C20@MW3PR11MB4619.namprd11.prod.outlook.com>
References: <4da3d82b084343bfa18de192b1f390b1@huawei.com>
In-Reply-To: <4da3d82b084343bfa18de192b1f390b1@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ginsberg@cisco.com;
x-originating-ip: [2602:306:36ca:6640:9c61:af70:7e80:9deb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b48a98c4-94b2-433f-3b59-08d7da3c0a39
x-ms-traffictypediagnostic: MW3PR11MB4572:
x-microsoft-antispam-prvs: <MW3PR11MB4572AAB0B6FF2E2F3B9B6D9EC1C20@MW3PR11MB4572.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0365C0E14B
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW3PR11MB4619.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(136003)(396003)(39860400002)(376002)(366004)(346002)(5660300002)(186003)(9686003)(55016002)(71200400001)(33656002)(81156014)(8936002)(8676002)(6506007)(81166006)(478600001)(110136005)(66946007)(52536014)(7696005)(66476007)(66556008)(64756008)(66446008)(2906002)(86362001)(76116006)(316002)(53546011)(142933001); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +CI25Ej5T/9K7mhFiecBRjG/9oOExlu4JBejSjTJnJcFuROqwwZLq1BtUpukth/V7m/izSCfGA3mM1j7YLAyVeb5TfNo78oVMmFannsPldu+CnOczxXIFm5byujEfuEfY3bK8Qrj711G3VH8XDPW4tssJ7QV1Yk5slEfDJORBXWzLmtIgGEPjSOgIdQB/gPFFLi8yRJ+Ly3IvTs7NuTMBCMu3sNOcZ7AeWK5u2/aCmvuexMwdNv76vXpBgR17DOdDuvM96+Ks6kv+/u713pfNCgd/ZcPwHtILfDVfk+F5bXP8VLu9SMxH/tKKLPRnKJLNbG7G7wKUfHNX0KxO/L1JJjJ+femjZxJIBVNOmKObTDA1CS9cIUNq5FFR3/3SKbTV5KkAMR29l6PM5jJvNVKXhwhjbT9sL37mhKriZjtN1j6Po/ZZEsjcdO44VQke7Ccr1W9MrNIxOm/ahkt6f3NGnVCCE6/dldbiweGWUwPmPx+0GX64eiAxjzhoXTl6Goi
x-ms-exchange-antispam-messagedata: wU8ujVv1r+AGkXTfkm/qnGPwLlDOke1EnA3+3/EUd5ERMgV3v2SLjDYo4gfua/tRer0kUlUe92VWuqOG/9qhUQ3IkzPLD4AYr110Tc/5neLrct0zIrunn+HTl1NhL/4GIfzzdFTq1A+ZcznNwI1MEoBsy2FoSX4xQ6y3AHZq629MKdRLDaPf28OjhYdodPk5UHKni8l92g7hOFBEniPswg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR11MB4619DBDBD80BC52A92F51176C1C20MW3PR11MB4619namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b48a98c4-94b2-433f-3b59-08d7da3c0a39
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Apr 2020 15:06:10.0032 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: RQehkovr2hrA5M+GmboMyoEBdxQ6QhwwOphcyFA0jh8PoVT14imRsqIZZlxpcwfXZ603Qpp6nC9vfPlzaf5UvA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW3PR11MB4572
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/i-hBCkadncvrPU3leekBbA5IS2g>
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 15:06:23 -0000

This discussion is interesting, but please do not ignore the considerable feedback from multiple folks indicating that this advertisement does not belong in the IGP at all (regardless of scope).
My opinion on that has not changed.

Thanx.

   Les



From: Lsr <lsr-bounces@ietf.org> On Behalf Of Tianran Zhou
Sent: Monday, April 06, 2020 7:48 AM
To: Greg Mirsky <gregimirsky@gmail.com>; draft-wang-lsr-ifit-node-capability-advertisement@ietf.org; lsr@ietf.org; draft-song-opsawg-ifit-framework@ietf.org; opsawg@ietf.org
Subject: Re: [Lsr] I,Scope of FIT Capability: a node or a link?

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<mailto:draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>; lsr@ietf.org<mailto:lsr@ietf.org>; draft-song-opsawg-ifit-framework@ietf.org<mailto:draft-song-opsawg-ifit-framework@ietf.org>; opsawg@ietf.org<mailto: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

v2.23.0 | Report a Bug | By Email