Re: [Lsvr] WGLC for draft-ietf-lsvr-applicability-04 (to end January 21, 2020)

Keyur Patel <keyur@arrcus.com> Wed, 22 January 2020 03:45 UTC

Return-Path: <keyur@arrcus.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2A2D120013 for <lsvr@ietfa.amsl.com>; Tue, 21 Jan 2020 19:45:43 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netorgft1331857.onmicrosoft.com
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 QjqutWqoIZXd for <lsvr@ietfa.amsl.com>; Tue, 21 Jan 2020 19:45:40 -0800 (PST)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2073.outbound.protection.outlook.com [40.107.236.73]) (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 C8B53120044 for <lsvr@ietf.org>; Tue, 21 Jan 2020 19:45:39 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Lf/Hf76pWeF7dBMRx5Q7Fafd+/3trwEFVcjJuTX/R5JQP3Q/DR5GdDYF16yizOobaJUTBckeu/Gksv7qXD5yFp8oAobHmGoPPJMqOioyFJWGZaxZapzoWn5uZmyUkmRSlz8UhLrV0cMCsufKOMvr/hxo4RGz4Majp+HrY+q//gP8v+W+rsEgeaNSvw8oCpQI7rrWJHna5tfhiPOcjdUdq5QMYFcRrBupMp7XWHyZwR7K1rjxfdpUKc53aIlp96xOVR5K/YCAdbulnTFt6+YYHHcvG68n1/gf0EwicraKrKefZZLLk3A7VciUFtTvpLipOZOtOHAA0NFeouhG2uxlKg==
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=Y+x7MYiSWNwSOpCGZ2fxRflrTb3ONdLZtAdZqTCI/gQ=; b=FIh71rzB2KkIJHz+9zslVFCmLcucq6XsOxYm++ULRX8P74ZMgSHI4oGS7hx0K8Bp6tzqhCs4mOvSZNRjG8R0i6MHrqGZUrgoHdHfvmUUnunob+ppaFr3kCvvlWFIxi9Cop/ptF0xIRF6ben9ibE188youemh6d+FSI7doAEDmKdln1dfWELngCs64bDDMNyubWBSHPTFt5agOftm5YVB+oOOfZBGMy+GGxee+0pIJWXy+2EaUztWOD2n4kqsJ6E0U8BQdvyQXxTyhxKJu6yqY6mcb4f5lSBNYZhu6f0BQtPUcMeBe+45pbBc42CxdCf3kC9wfzJGtCYpIL/TnnKfeg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arrcus.com; dmarc=pass action=none header.from=arrcus.com; dkim=pass header.d=arrcus.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT1331857.onmicrosoft.com; s=selector2-NETORGFT1331857-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Y+x7MYiSWNwSOpCGZ2fxRflrTb3ONdLZtAdZqTCI/gQ=; b=e7gPGPEV1VwdLz63MjT3GR2EMk+H4qmmaH9XMX5Q4+WU2eWDXeZQDrQLCevvF5jdMD2ULCpiZakO14rDjVGWnDCHWKbuGid7P4rn9XT/9F2Gbgpd0fzdBrdw3XrNQiGnLbU87gnqVk6+EtLmmGZnOI4TjW9RNoo7lTi02sc953g=
Received: from BYAPR18MB2856.namprd18.prod.outlook.com (20.179.59.30) by BYAPR18MB2695.namprd18.prod.outlook.com (20.179.58.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.23; Wed, 22 Jan 2020 03:45:37 +0000
Received: from BYAPR18MB2856.namprd18.prod.outlook.com ([fe80::d8cc:de80:2181:6c27]) by BYAPR18MB2856.namprd18.prod.outlook.com ([fe80::d8cc:de80:2181:6c27%7]) with mapi id 15.20.2644.027; Wed, 22 Jan 2020 03:45:37 +0000
From: Keyur Patel <keyur@arrcus.com>
To: Boris Hassanov <bhassanov=40yahoo.com@dmarc.ietf.org>, "lsvr@ietf.org" <lsvr@ietf.org>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>
Thread-Topic: [Lsvr] WGLC for draft-ietf-lsvr-applicability-04 (to end January 21, 2020)
Thread-Index: AdXFPESJQqXWSN51Tqy1DO85V6W27gG/Ap5wAQ4F/gAACLzQgA==
Date: Wed, 22 Jan 2020 03:45:37 +0000
Message-ID: <077EC01A-0CE6-411D-98D2-B7689D11B071@arrcus.com>
References: <AM6PR07MB482349E2CC33B30A35F7D0A9E03F0@AM6PR07MB4823.eurprd07.prod.outlook.com> <AM6PR07MB482383564D43B71545F8F411E0360@AM6PR07MB4823.eurprd07.prod.outlook.com> <513025242.9878512.1579620926598@mail.yahoo.com>
In-Reply-To: <513025242.9878512.1579620926598@mail.yahoo.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=keyur@arrcus.com;
x-originating-ip: [70.234.233.187]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4de8e842-3f96-4d0a-0772-08d79eed8b50
x-ms-traffictypediagnostic: BYAPR18MB2695:
x-microsoft-antispam-prvs: <BYAPR18MB26956C5ADCC4F82B8891967BC10C0@BYAPR18MB2695.namprd18.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 029097202E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39830400003)(136003)(366004)(396003)(346002)(199004)(189003)(33656002)(6506007)(966005)(508600001)(2616005)(8936002)(26005)(8676002)(9326002)(86362001)(81156014)(81166006)(2906002)(186003)(5660300002)(36756003)(76116006)(316002)(71200400001)(66556008)(110136005)(66946007)(64756008)(66476007)(66446008)(6512007)(6486002)(53546011); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB2695; H:BYAPR18MB2856.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: arrcus.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: rT7wKaoj2XTw1J+Y63c4sttYYPe45SICIdRVCrMgKK2MnsdG1yMgqVxiaKtOTv50C6nF76ck+uIid9zL8uh76Os/kT1VSwf2MYQr1+GWBHhi4vZP91DBre3v0neOs4HPuoNt0dLzIog/Djhd1Yl2WbYtaRFZi1+YT+rhvlI7pYg3l8pDL3imhCpVZg1fZHPd6V3ngDH1QTj6Ta3vzudbaBSWB39JfF0dWzSAHq4qcdtpXqmvJXsaWIox0LyuBHuiaS2LfjsOCDmbNDCvPOnWoM21Gqgd/FVWFZknL02C2mysEkQnb88szStRAY0m7Fu+G1kdFTFHyP+G7v3zCZX0Cgc3JfcW+FM8SH3d9ito1KCGWk1sJQ4+M0tyx6GnAU8sHtdRlC1GWDgKAuOXKtHnSdW0rUi17X0DROOLUPFF+yMCRNos6dtjleJl2cJhvp0AErwIJNJzulgRYfZnj0n4D+AGSTKMPoC1EJ4eqUzr/ZI=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_077EC01A0CE6411D98D2B7689D11B071arrcuscom_"
MIME-Version: 1.0
X-OriginatorOrg: arrcus.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4de8e842-3f96-4d0a-0772-08d79eed8b50
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2020 03:45:37.6301 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 697b3529-5c2b-40cf-a019-193eb78f6820
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: YvV0C9qC3abGCz6HzqnSkM9ui2/eAoeegnbll1++f3nJwRegoZjhqLyr/riLIQWECJlg3tnyM0lWvXWfqiKVZA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR18MB2695
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/cuvCMgXCBS5RTx8fXHoJo_XIEIw>
Subject: Re: [Lsvr] WGLC for draft-ietf-lsvr-applicability-04 (to end January 21, 2020)
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2020 03:45:44 -0000

Hi Boris,

Thanks for your comments and detail review. 😊

Ack on all three. We will cover it in next revision.

Regards,
Keyur

From: Lsvr <lsvr-bounces@ietf.org> on behalf of Boris Hassanov <bhassanov=40yahoo.com@dmarc.ietf.org>
Date: Tuesday, January 21, 2020 at 7:35 AM
To: "lsvr@ietf.org" <lsvr@ietf.org>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>
Subject: Re: [Lsvr] WGLC for draft-ietf-lsvr-applicability-04 (to end January 21, 2020)

Hi Gunter and all,

Sorry for the late reply.
I read the draft and personally support its publication.

Few comments for the next updated version:
1) The References part needs to be updated since there are newer versions of those drafts are available.
2)  Can RFC 5549 approach be incorporated for simplification of BGP connected graph configuration and creation? There is example of such implementation  for kind of BGP unnumbered peering configuration so it could be useful here too, IMO.
3) I think that LSVR/BGP-LS SPF has another very important use case: using of  of real topology information of CLOS network for monitoring and troubleshooting instead of using home-made tools for topology verification... Can we extend the draft for such case in the the next version?

Thanks.

SY,
Boris




On Thursday, January 16, 2020, 9:45:40 AM GMT+3, Van De Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.com> wrote:



Tuesday 21 January is approaching soon.

If you read the draft, please post your comments on document readiness and completeness.



Be well,

G/



From: Lsvr <lsvr-bounces@ietf.org> On Behalf Of Van De Velde, Gunter (Nokia - BE/Antwerp)
Sent: Tuesday, January 7, 2020 16:39
To: lsvr@ietf.org
Subject: [Lsvr] WGLC for draft-ietf-lsvr-applicability-04 (to end January 21, 2020)



Hi All,





The LSVR WG initiates a working group last call for "draft-ietf-lsvr-applicability-04". Please send your comments to the list before Tuesday January 21.



https://datatracker.ietf.org/doc/draft-ietf-lsvr-applicability/



All, please reply on-list indicating if you're aware of an implementation.

If not already completed, please reply on-list indicating if you're aware of any relevant IPR.



Brgds,

Gunter & Victor

LSVR WG co-chairs


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