IETF Logo Mail Archive

Re: [Lsr] A new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 09 March 2020 21:06 UTC

Return-Path: <ginsberg@cisco.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 3DA013A173B for <lsr@ietfa.amsl.com>; Mon, 9 Mar 2020 14:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 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, 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=AbgqHqNE; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=jaFzbcbh
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 iUVan5N4qH89 for <lsr@ietfa.amsl.com>; Mon, 9 Mar 2020 14:06:48 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CA823A172E for <lsr@ietf.org>; Mon, 9 Mar 2020 14:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15166; q=dns/txt; s=iport; t=1583788008; x=1584997608; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=aD9+TQNCofNqZdLf4xxSnYhKjJNGXPRMT5xn6IEHorY=; b=AbgqHqNEUyMnr5xTXQKN08ru3stBIm+9T8zMlaHpUrCo39+yqW292PiS fCQyl/eGzX32X8B4SWBRVDsU5V06DA7rd/HVDukfEe7pktW/MMUtHCIID WG3oUGZ174qhvjA1PLJPnemVTPbRIEhEYvVAWZcPndkXELC9nHmwYsHuX o=;
X-IPAS-Result: A0CACgBVfmVe/5hdJa1lHAEBAQEBBwEBEQEEBAEBgXuBJS9QBWxYIAQLKoVzgWgDimtOghGQJoMKA4RigUKBEANUCQEBAQwBASUIAgQBAYMNgTYCgg4kOBMCAwEBAQMCAwEBAQEFAQEBAgEFBG2FVgyFYwEBAQEDEhsTAQE4DwIBCBEEAQEoBzIUCQgBAQQBEggagwWBfU0DLgEOnEsCgTmIYoIngn8BAQWBMwIOQYMDGIIMAwaBOIwsGoFBP4EQAUeCTT6CZAEBAgEBGIEPPCQHCYMNgiyWWiSZKgqCPIdSh3eHOYJJiCGQS452iHySVQIEAgQFAg4BAQWBaSKBWHAVGoMNUBgNjh2Dc4UUhUF0AoEnjUABAQ
IronPort-PHdr: 9a23:Dz4H0RZ0wCgXQegBMudygOX/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavlbiohFslYW3du/mqwNg5eH8OtLwSI8Ge/5jMTBBjzcBFtKLSpSKjVicn/l/io/IHeaBlJgzz7Zq5uKBKxrkPascxEyYBjMa02jBDOpzNEfOlNjWVvORqfkg396cG54JMGkWxItugk9tJcXKmyZKk+QbFCRDQhKHwupcA=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.70,534,1574121600"; d="scan'208,217";a="432916245"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Mar 2020 21:06:47 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 029L6kOa002517 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Mar 2020 21:06:46 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Mar 2020 16:06:45 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 9 Mar 2020 16:06:45 -0500
Received: from NAM11-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.1473.3 via Frontend Transport; Mon, 9 Mar 2020 16:06:45 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=I/iXXdJ7P3AKk3NHFbBpxLj++o+6DpXBPDUDjv+HLWmPoc9P+zCTjli1g39hMTTBsAwaXctCtFXKOl4gb7Gf8+8jEfVjMBEKNY9DkMlM3l8uBZJbYX60bx9zBu1QjwTItmGe4Z4FTPJijihajrGHRQpFsTyYG5nDLvX+cb3qsPQq7glDBKv0CW2A7PDNjl/JV/9KvClw8WgAfdZQ/6+l+V77yubmoaleS+iQ8Yals9pQeLtSXbSszs/teq5l//7zK12CAEAMOPyYMU/+q2zREw52MhfvU2qun1bYDzR34TSoOFRb7SPovE/gA/n/FYM/FkYwUWG/ifsTkcVrwx9MXg==
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=PgYjxX2pav24n/MZL8v0cn3odp/bt8eE/KVVyiV9b3k=; b=IOUkDYDEQJNfNkTc877wvbYr8Uf35YQZ5wKeEmWYlWn5T2kOPZBNJgMNwzQVMePfIX6c6zSgwEDiX+q0DgBvdgJwN7QSp3f6L4E/9xlyDcdyJW0XN38d40i9KeFiqChFkiEmbKMehEBNzMufljMdvimb4/MbYb1V0THaPBPVZPfoBJ3AaCmTubulXBCWBjhKvbaU+8yk6OL5PxhD3A+2SZiCsqzi6tk3SuOvWEsbavnaDLAbJQZEoHP4zIMSf5lUNgMzNdmyH4OAZhIC0iMoTjbrcJKacYsNgGqJistoMt5a+mc6ZFl934wpZfgu/5eRT/8p5bVJvWsyiyLBsmprug==
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=PgYjxX2pav24n/MZL8v0cn3odp/bt8eE/KVVyiV9b3k=; b=jaFzbcbhjXVaoFBU3IMwGutozv0Yzmh2p7ubXHaYwKt3EfKZfE1TSu4Jf9+uqR9kh/4EE9HPwdCnPk2jWHcQKvCHo6USV+w5U9moam/AeHXHYbViAK9u6vX3UA7Sq9PnJUTmstMg4Lb1I3Klp69HZlpv0xpHPidqZ9g7ySr0k9w=
Received: from MW3PR11MB4619.namprd11.prod.outlook.com (2603:10b6:303:5b::15) by MW3PR11MB4745.namprd11.prod.outlook.com (2603:10b6:303:5e::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17; Mon, 9 Mar 2020 21:06:44 +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.2793.013; Mon, 9 Mar 2020 21:06:44 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: wangyali <wangyali11@huawei.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: A new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02
Thread-Index: AdX160PqpEiNp0glSrmxOyus22HBcgAah/Pw
Date: Mon, 09 Mar 2020 21:06:44 +0000
Message-ID: <MW3PR11MB4619361A2CA3A402A44914E5C1FE0@MW3PR11MB4619.namprd11.prod.outlook.com>
References: <1520992FC97B944A9979C2FC1D7DB0F404DB1AD4@dggeml524-mbx.china.huawei.com>
In-Reply-To: <1520992FC97B944A9979C2FC1D7DB0F404DB1AD4@dggeml524-mbx.china.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: [2001:420:c0c8:1002::5c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9c49ad59-ecd5-43d7-efee-08d7c46dc608
x-ms-traffictypediagnostic: MW3PR11MB4745:
x-microsoft-antispam-prvs: <MW3PR11MB474566144559507158517081C1FE0@MW3PR11MB4745.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0337AFFE9A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(396003)(136003)(376002)(39860400002)(366004)(199004)(189003)(7696005)(66946007)(64756008)(66446008)(6506007)(66556008)(52536014)(53546011)(5660300002)(66476007)(316002)(55016002)(66574012)(9686003)(2906002)(86362001)(966005)(478600001)(71200400001)(33656002)(110136005)(81156014)(8676002)(8936002)(81166006)(76116006)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:MW3PR11MB4745; H:MW3PR11MB4619.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
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: rPPwpi2Kow/oTyq89cLATyWJ4cuOlytDXVSHWjFGDlYCJAs4kW+w1MIh0x3FTwI+9ek2XRE8k/uccKSfJ5Odl5dQQmubsa5cjmQqlKnoS36kLmmEfbHAWVx5fco1op4KlAKyry87sitVThYJHlxjiaVgZcIANk4DUogNxs5GAeEQCdHV5nX1hpN+vqgmiweEk7QGB9v0ia32K3t7oGjjJw031dy+StqjpNNud+rlZToJObC/sy3O6b/wamNMW8772vldLUgFqivbAqXHXo8qdra9LRrB27XRjtUEtkVzacAA3gdDu/h07aO4FnIB4iyFNahJs76P/UP1jSR4SRj/cyuzyM6b6BURPIcK1v7HLYuS+WFNv9oNNxqs7i37HFnkuZ4UwWhfazOneA1ZMKSVXIaohpiTdj05z/LyaBQzUXST0DQhj5ib9G1R9lXCjy7OzhVIBvA7EX3Cp5nSYFNKP1dks4ITJqZ982DDHEQh2I/E8uhACxWu8MP0I3u+GyyMbsH5NgPYrsaSM77dt8okaQ==
x-ms-exchange-antispam-messagedata: 6wmWr5Ugi8cW+vtXye4bwZ90i/TXBhXyaCe5ZuYzedqnpc21IAi+1hHZLleSd9tFgLf9WrtA5Ip5sLrw/SzHu0Tz+ZGpa+BRBUvKHH+gUG69fh3aXOkIg/LGMChj0BymjoxGjebOo4gAtq96gCbGcPvHqRZ9lIFi92hGeFQfs8o=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR11MB4619361A2CA3A402A44914E5C1FE0MW3PR11MB4619namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9c49ad59-ecd5-43d7-efee-08d7c46dc608
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2020 21:06:44.7435 (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: dqagN8CDhnjmjU96N5VjiKHu78c98s0lDaJhk4ZOpA/O4H8b/LTQDgRSNbqD3euld2n2eHsmpDM2OrIYPkovKA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW3PR11MB4745
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/5GdFCy7zg8eCIGvQZpmAbOtrTjQ>
Subject: Re: [Lsr] A new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02
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: Mon, 09 Mar 2020 21:06:50 -0000

Yali -

What is missing for me is an explanation of why IFIT Capability information is something that is appropriate to be sent using IGP Router Capability advertisements.

Generally speaking, we prefer to restrict IGP advertisements to information which is of direct use to the protocol. However, it is fair to say that we have relaxed this restriction in some cases e.g.:

https://www.iana.org/go/rfc7883
https://www.iana.org/go/rfc8491

However, even in these cases the information advertised is of value to some entity executing on the protocol peers - even if not directly by the IGP itself.

I see no such value add here i.e., the IFIT capability information may well be of value to a controller but I do not see any use case for any entity on protocol peers.
So why should we use IGPs to send this information to all other IGP peers when none of them can make use of this information?

    Les


From: Lsr <lsr-bounces@ietf.org> On Behalf Of wangyali
Sent: Monday, March 09, 2020 1:21 AM
To: lsr@ietf.org
Subject: [Lsr] A new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02

Dear all,

I'm Yali. Following is a new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02 I submitted recently.

Please let me know your questions and comments. Thank you.

>>>>>>>>>

Name:               draft-liu-lsr-isis-ifit-node-capability

Revision:  02

Title:                  IS-IS Extensions for Advertising IFIT Node Capability

Document date:       2020-03-09

Group:               Individual Submission

Pages:               7

URL:            https://www.ietf.org/internet-drafts/draft-liu-lsr-isis-ifit-node-capability-02.txt

Status:         https://datatracker.ietf.org/doc/draft-liu-lsr-isis-ifit-node-capability/

Htmlized:       https://tools.ietf.org/html/draft-liu-lsr-isis-ifit-node-capability-02

Htmlized:       https://datatracker.ietf.org/doc/html/draft-liu-lsr-isis-ifit-node-capability

Diff:           https://www.ietf.org/rfcdiff?url2=draft-liu-lsr-isis-ifit-node-capability-02



Abstract:

   This 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 [RFC7981], 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.


Best Regards,
Yali WANG
E: wangyali11@huawei.com<mailto:wangyali11@huawei.com>

v2.23.0 | Report a Bug | By Email