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

"Acee Lindem (acee)" <acee@cisco.com> Wed, 08 April 2020 11:04 UTC

Return-Path: <acee@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 655823A12FB; Wed, 8 Apr 2020 04:04:34 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Bffxzv5V; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=leHtRDfv
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 dHA76RgedJ1W; Wed, 8 Apr 2020 04:04:32 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A860F3A12FC; Wed, 8 Apr 2020 04:04:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33885; q=dns/txt; s=iport; t=1586343871; x=1587553471; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ZwNbsrfkJ9LqctkxBb8J32JJD/emIx+9L9VjH3omOj0=; b=Bffxzv5VSMoI50FxCCfWspb0YRTbOGJcMuEY7Ivox+pwvRqIY24KoiLB SHJLOXkkjuwLoSr8eHFEqZbgAJB4jJpjoYOv7ijeD54nLhAez2Xz7RFY6 1Gbi6gtpiERW3SEdobLj6xwdmqtZsxJrx46Q9NzpSM1i49orrQGHMUV2c o=;
IronPort-PHdr: 9a23:9aPCXBf7Cw1GbtKC6GBp/nVglGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwKUD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFlcejNkO2QkpAcqLE0r+effhYiESF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BCAACoro1e/4sNJK1mGQEBAQEBAQEBAQEBAQEBAQEBEQEBAQEBAQEBAQEBgWoBAQEBAQELAYEkLyQsBWxYIAQLKgqEEoNFA4prToIRiXCOMIJSA1QKAQEBDAEBGAEKCgIEAQGERAIXgXAkNwYOAgMBAQsBAQUBAQECAQUEbYVWDIVwAQEBAQMBARARHQEBLAsBDwIBBgIRAwEBASEHAwICAh8GCxQJCAEBBAENBRsHgwQBgX5NAy4BDpRqkGcCgTmIYnWBMoJ/AQEFgUNBgzsNC4INAwaBOAGMMhqCAIEQASccgk0+gh5JAQECAQGCAQYHCYJcMoIskFI7hgWKPI8eSAqCPYd1iwOEPR2CTog6kQCPPIkogj2QRgIEAgQFAg4BAQWBaCOBV3AVOyoBgj5QGA2RIoNzhRSFQXQCgSeNGQGBDwEB
X-IronPort-AV: E=Sophos;i="5.72,358,1580774400"; d="scan'208,217";a="460217090"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Apr 2020 11:04:29 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 038B4T0O027035 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 Apr 2020 11:04:29 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 8 Apr 2020 06:04:29 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 8 Apr 2020 06:04:29 -0500
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 8 Apr 2020 06:04:29 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ILpajk3M4wHpLrqt3hnJc+gKO7afGf0pAIuhyZjBphVfzzf2ZXAlRdfVFs0PelsKUHft2n7QFfnbLWTTGZzhWMJHp8avxDTVf/ueWbLzeq4uWtELgmOe6GEphi3W02KAlKvKJz8r7XYf3A6hZxiWFbrqOnUq0y+2ENZmnaXaWFZmKPSMTPjjnnxO1JaO5o//l1Wj8srMlI+jeqqhgkujx0wu9J9lnBWbXi7jyOMQmHYaUeyMf8pyqeGZKs+pcMiaHicW4k05/H6KNy9DI64Akx16Oea54hwnh+N8lPK9FEKPO0f5bQLS32AEtwJ/6ympvDtSWwisBFsrIFYbTFUynA==
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=ZwNbsrfkJ9LqctkxBb8J32JJD/emIx+9L9VjH3omOj0=; b=iv24MBkS2CqCOzV+5W7aS6CYrvOiRbuwImxi5dORKN8iAR9ZlzHghPH8Wznk7HLIEtlwd00Z7rt+3Ac1KOtdDBoD0mWrDzGGenLdnhAFft35sYKzYw4x4WJ4UArEdyZcZz17rzQfW0fyUTyHYR7+9k29GcS1juQfCx7sAGjMQvcE6K/KzkjsSDqWFGISV0m3USnwVfQJfXZvKdkAHBkc51aX5qdBPFPPBcGj9/OoaQ9BvCbPnKM2GWx9w5rYtZYQpCoyOAePmmMnvJHkOKIVK3TRDXRZn7FhYEitwiPcGJDVAkW0Za4HdSO/wuCsoUn5klwlBxdGv6FTgpKs0mzmzg==
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=ZwNbsrfkJ9LqctkxBb8J32JJD/emIx+9L9VjH3omOj0=; b=leHtRDfvo2ACd4vVZLz5zI9FCd0FSCapuCoEkX8QPwesTOcTCiN0AKcpK5zoQCn6pDz0DEhXGpsGMBzFdIABOMJ3RkHaRTUvja8OnvWQDlG5YEvL/Usdjlg17jDq8IZ6tMMjG/+Nw+gVly+WDHRaKzz610/K8LbN4F+a+chAgyc=
Received: from BN8PR11MB3794.namprd11.prod.outlook.com (2603:10b6:408:8f::13) by BN8PR11MB3587.namprd11.prod.outlook.com (2603:10b6:408:8e::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15; Wed, 8 Apr 2020 11:04:27 +0000
Received: from BN8PR11MB3794.namprd11.prod.outlook.com ([fe80::55b2:c415:675f:5fb7]) by BN8PR11MB3794.namprd11.prod.outlook.com ([fe80::55b2:c415:675f:5fb7%3]) with mapi id 15.20.2878.018; Wed, 8 Apr 2020 11:04:27 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Tianran Zhou <zhoutianran@huawei.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>, Tony Li <tony1athome@gmail.com>
CC: Greg Mirsky <gregimirsky@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-song-opsawg-ifit-framework@ietf.org" <draft-song-opsawg-ifit-framework@ietf.org>, "draft-wang-lsr-ifit-node-capability-advertisement@ietf.org" <draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] I,Scope of FIT Capability: a node or a link?
Thread-Index: AdYMrIUGWe8h8bS0Rki6HVv232b2lQATRHCAAB2l8KAAAPAtAA==
Date: Wed, 08 Apr 2020 11:04:27 +0000
Message-ID: <D5FFD2C4-FBCB-414F-976B-438D8F498465@cisco.com>
References: <edb64d47da6a4b2e80b9cc276bce84be@huawei.com> <470F1857-3554-49BE-A212-F3A10F43280F@cisco.com> <a9f2fce8c3694471a023882dcc2fc81f@huawei.com>
In-Reply-To: <a9f2fce8c3694471a023882dcc2fc81f@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.35.20030802
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3b38f1c3-8c33-45c8-82a9-08d7dbac9ae9
x-ms-traffictypediagnostic: BN8PR11MB3587:
x-microsoft-antispam-prvs: <BN8PR11MB358777ED68C9E2E1BB358229C2C00@BN8PR11MB3587.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0367A50BB1
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN8PR11MB3794.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(346002)(376002)(136003)(39860400002)(366004)(396003)(6512007)(316002)(33656002)(53546011)(6506007)(66574012)(81156014)(36756003)(478600001)(966005)(26005)(81166007)(8676002)(86362001)(8936002)(6486002)(66556008)(5660300002)(71200400001)(66446008)(54906003)(66476007)(76116006)(186003)(91956017)(2616005)(2906002)(4326008)(66946007)(110136005)(64756008)(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: ow7xeew587f9kMNIOvM3Rz7Qx68iVcb0O6L8zyRW9CsNQffKln9j4XHDJcrWOIPT+Py5IK4bv8U9TxeY4CUP3b3j3mqD7pOCnVE6/EZGHsH7Ex6iSX+5hLgDPyoSaiiqPMVK2NAWkLS7hccKg+e8WFOXxE+PChl9/r1laShQOzOwsRufl32/QxbmLgpaHBdfwweex/rB89Q4eGKM4YQhfBIbUMCCB5+cwfjuCYLCIvNgBEPNUhHp24VEpmkEEgElHArn6LGPLdPAWcmENAE0HtZUph0AeluOLX1oXGQO7y3yEFYh3ssSGnwDm8dfhRJhhdoU5KcNnvMJejF+lPaYwk1+PTrRLJNZ/jyVTqERGhz2ylwNILPSRoZWPd3T7CYXZihN5K2j8DI7La9k46fv86IjNY/Lyfqdjhfk1meHR8aJCmbYPOsWN7BEVnaupTe1ARQV6h1zYlZ8+NOPpK3qxWPfCZUqpup+ixlvXPJoB0yAs0tFygGD8D/4BiVqkdiAsTIWbfCO5ARkVWOsWbYmAJo4J0JqIybm0EFSoNKQU4x3GM/1jray7zl/a9ILrAhX
x-ms-exchange-antispam-messagedata: UibWuTfmypgctiKnFZO80kTpI/4UpB3AJCYGCBaaYzKFKA/ANxyH1MgoWT9DSz4kpMhLXaZas7rp7rqy38ylU1TjicDfYqjEP4Cq9PX8VWNZkt88eudXRc4U6eMoRjIgyE/okt2MC7MEbrf8e7m11Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_D5FFD2C4FBCB414F976B438D8F498465ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3b38f1c3-8c33-45c8-82a9-08d7dbac9ae9
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2020 11:04:27.5247 (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: hzlH/3DmjzHOh6mU2t8eKSafQLSakpjrtUdhT/+jl2AwUmaTvFiWxNOn+nNlFzNr
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3587
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4tNTdFu7DMU1k85Wh8cbFnopwhI>
Subject: Re: [Lsr] I,Scope of FIT Capability: a node or a link?
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: Wed, 08 Apr 2020 11:04:35 -0000

Tianran,

You keep missing my point. Even if the potential transit nodes advertise the capability, the management function doesn’t know which nodes will be transited in the path. Hence, you’re second use case is misguided.

Acee

From: Lsr <lsr-bounces@ietf.org> on behalf of Tianran Zhou <zhoutianran@huawei.com>
Date: Wednesday, April 8, 2020 at 2:51 AM
To: Acee Lindem <acee@cisco.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>, Tony Li <tony1athome@gmail.com>
Cc: Greg Mirsky <gregimirsky@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-song-opsawg-ifit-framework@ietf.org" <draft-song-opsawg-ifit-framework@ietf.org>, "draft-wang-lsr-ifit-node-capability-advertisement@ietf.org" <draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Subject: Re: [Lsr] I,Scope of FIT Capability: a node or a link?

Hi Acee,

Tracing is of course useful.
Here we  also consider to combine the traffic engineering and monitoring. So the transit nodes are visible.
For the loose TE, the intermediate SR nodes construct the segment monitoring.

Tianran

From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Wednesday, April 8, 2020 4:29 AM
To: Tianran Zhou <zhoutianran@huawei.com>; Jeff Tantsura <jefftant.ietf@gmail.com>; Les Ginsberg (ginsberg) <ginsberg=40cisco.com@dmarc.ietf.org>; Tony Li <tony1athome@gmail.com>
Cc: Greg Mirsky <gregimirsky@gmail.com>; draft-song-opsawg-ifit-framework@ietf.org; lsr@ietf.org; opsawg@ietf.org; draft-wang-lsr-ifit-node-capability-advertisement@ietf.org
Subject: Re: [Lsr] I,Scope of FIT Capability: a node or a link?

Speaking as WG member:

With respect to your use case for transit router advertisement… What I was unsuccessfully trying to articulate to you during the interim was that the management system will typically not know the exact path between two endpoints so the use case is flawed. In fact, many times tracing is used by the management system to discover the path – as in traceroute…

Thanks,
Acee



From: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>
Date: Tuesday, April 7, 2020 at 3:22 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>, "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>>, Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>>
Cc: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>, "draft-song-opsawg-ifit-framework@ietf.org<mailto:draft-song-opsawg-ifit-framework@ietf.org>" <draft-song-opsawg-ifit-framework@ietf.org<mailto:draft-song-opsawg-ifit-framework@ietf.org>>, "lsr@ietf.org<mailto:lsr@ietf.org>" <lsr@ietf.org<mailto:lsr@ietf.org>>, "opsawg@ietf.org<mailto:opsawg@ietf.org>" <opsawg@ietf.org<mailto:opsawg@ietf.org>>, "draft-wang-lsr-ifit-node-capability-advertisement@ietf.org<mailto:draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>" <draft-wang-lsr-ifit-node-capability-advertisement@ietf.org<mailto:draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>>
Subject: RE: [Lsr] I,Scope of FIT Capability: a node or a link?

Hi Acee,

About the “IFIT specific information channel”, as in https://datatracker.ietf.org/doc/draft-qin-idr-sr-policy-ifit/
we propose to use bgp enabled sr-policy for IFIT auto deployment.
It’s reasonable to incorporate both traffic engineering and monitoring.

Thanks,
Tianran

发件人: Acee Lindem (acee) [mailto:acee@cisco.com]
发送时间: 2020年4月7日 2:54
收件人: Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>; Les Ginsberg (ginsberg) <ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>>; Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>>
抄送: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>; draft-song-opsawg-ifit-framework@ietf.org<mailto:draft-song-opsawg-ifit-framework@ietf.org>; lsr@ietf.org<mailto:lsr@ietf.org>; opsawg@ietf.org<mailto:opsawg@ietf.org>; Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>; draft-wang-lsr-ifit-node-capability-advertisement@ietf.org<mailto:draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>
主题: Re: [Lsr] I,Scope of FIT Capability: a node or a link?

Speaking as WG member – It seems that additional IFIT-specific information is required to make this useful and the IGPs are certainly not the case. Additionally, the point was made that an IFIT specific information channel would anyway be required to provision the telemetry generation.
Thanks,
Acee

From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> on behalf of Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>
Date: Monday, April 6, 2020 at 2:33 PM
To: "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org<mailto:ginsberg=40cisco.com@dmarc.ietf.org>>, Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>>
Cc: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>, "draft-song-opsawg-ifit-framework@ietf.org<mailto:draft-song-opsawg-ifit-framework@ietf.org>" <draft-song-opsawg-ifit-framework@ietf.org<mailto:draft-song-opsawg-ifit-framework@ietf.org>>, "lsr@ietf.org<mailto:lsr@ietf.org>" <lsr@ietf.org<mailto:lsr@ietf.org>>, "opsawg@ietf.org<mailto:opsawg@ietf.org>" <opsawg@ietf.org<mailto:opsawg@ietf.org>>, Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>, "draft-wang-lsr-ifit-node-capability-advertisement@ietf.org<mailto:draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>" <draft-wang-lsr-ifit-node-capability-advertisement@ietf.org<mailto:draft-wang-lsr-ifit-node-capability-advertisement@ietf.org>>
Subject: Re: [Lsr] I,Scope of FIT Capability: a node or a link?

+1
Please do not take my comments about link vs node capabilities, as support for the solution, they are semantical.

Cheers,
Jeff
On Apr 6, 2020, 8:58 AM -0700, Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>>, wrote:


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.


+1

IS-IS is not the correct place to implement Service Discovery mechanisms. The management plane already has ample mechanisms for service and capability discovery.

Tony


_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr