Re: [Idr] [Lsr] Regd covering BGP-LS extensions for IGP ELC drafts

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Fri, 26 July 2019 15:54 UTC

Return-Path: <ketant@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24D8B120048; Fri, 26 Jul 2019 08:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=hE1iF+tP; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=QdNWFSyA
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 OcCJkqz_NBaZ; Fri, 26 Jul 2019 08:54:38 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 097D4120041; Fri, 26 Jul 2019 08:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25276; q=dns/txt; s=iport; t=1564156478; x=1565366078; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ZV03f/wrfkp1pntRnnBBIvGwCEVXY1p1M65bwmo1Kh8=; b=hE1iF+tPAa5YIZEhpdrwK/6dYBlX6VH0y3RfbbuUOn1qooheZMdhFMi+ 36h7BAl65M+coZnvdY+RTaMCPDQvpAVXYQR1O8kNqujGJ1oAY7TCyR9qG MKxTZbGj8GsUUkqJ4Le5uyJIMb+z4WQgOr3mmiFUKPcCPswr7N5R/Pv+V k=;
IronPort-PHdr: =?us-ascii?q?9a23=3AwRiH9BKfMOtEWan3p9mcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeCtKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXE72MPfscwQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAABpITtd/49dJa1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUwQBAQEBAQsBgRQvUANtVSAECyqEHoNHA4RSiC6CW36?= =?us-ascii?q?WVYEugSQDVAkBAQEMAQElCAIBAYRAAheCSyM0CQ4BAwEBBAEBAgEGbYUeDIV?= =?us-ascii?q?KAQEBAQMSEQoTAQE3AQ8CAQgOAwQBASgDAgICMBQJCAEBBAENBQgagwGBHU0?= =?us-ascii?q?DHQEOoFMCgTiIYHGBMoJ6AQEFgTIBAwICDEGDABiCEwMGgTQBi14XgUA/gRA?= =?us-ascii?q?BRoIXBy4+gmEBAQIBAYFfJAcJglUygiaOfoR/lnwJAoIahlmNUpgNjTuHSpA?= =?us-ascii?q?LAgQCBAUCDgEBBYFQOIFYcBWDJ4JCg3GFFIU+AXIBAYEnjVYBAQ?=
X-IronPort-AV: E=Sophos;i="5.64,311,1559520000"; d="scan'208,217";a="385037377"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Jul 2019 15:54:36 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x6QFsaxL026455 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 Jul 2019 15:54:36 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 10:54:36 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 10:54:35 -0500
Received: from NAM02-CY1-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; Fri, 26 Jul 2019 10:54:35 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ISi2Hpiw+KHDD8qVa8Y1yLwF9rtOfUmZv/PUilSrvUO7ig2oRyWdnagXeTwMSC/4r6Ikb8jK9ntgxwqEtCBe/0k+VlZIUij7TuTSZQ47kbqL7OAFHjyPLWLK8h++O+lzyU0sJi5HsYmvlIsMv+wHO2ItFY5UCJahfLfUTtUouiFLc0dQW+GZAomTM8E0hDdgb656a9UBhID8/5+nP6uWGjgYYyBfcVo8lU27tg8me6bkfLTPOjmap8LPDgvJrwrqOLIMr0dNuBy1SaszSDHGZlCnQKunFRa34OIWZYJtZiJntNc41dwFElYCynxiSE9AuL/Kypg75hXeR2Vhbn6ZIA==
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=ZV03f/wrfkp1pntRnnBBIvGwCEVXY1p1M65bwmo1Kh8=; b=RXckKX/VcxAkHB4kIib7/wnf7Ah21p7i20Uh5l1nSC5naZfI14RCShs2NkDmtUfp8v9wUz+99fomYVM/n8nL55uUVVm8x+KJoT6NCLgWmo2hGQ13sQDQEPamgv/0uahxjur/B7jUG0CcgNFemHWVyEnuw71brViebd6nR2iWlFTZ9LXO3bCG3rDgNAEmLLw642s9LEiO81zBWFaYUwHDKld+/IApkKocINiwd809/42K2nZRnMo08EtNZ2ARed+LiBdtM8l8dlsm2wXtJk3+UcdtN5HeCLFUujyFcxUbgrGgn1NUXcVR6KCKhol6Gqk+LAhBpGoBiZ++g3BFT07u6Q==
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=ZV03f/wrfkp1pntRnnBBIvGwCEVXY1p1M65bwmo1Kh8=; b=QdNWFSyAHlxRokXhlB4KeSRmQZ6U/5Dfub+M0tVRwwnf2AgBczkbZsf0jEg5Qn9vzIIxclDC1NdhWLjHQBwEwrCfVgHIlAdbuvkIqga8G8QXrMhq8+LMzLGlJ15Qw1Lg0AFmHVlFnZGSMZuxwT1tSnvnbZmP/CVXTm3qLciDN7g=
Received: from DM5PR11MB2027.namprd11.prod.outlook.com (10.168.103.22) by DM5PR11MB1468.namprd11.prod.outlook.com (10.172.34.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.17; Fri, 26 Jul 2019 15:54:34 +0000
Received: from DM5PR11MB2027.namprd11.prod.outlook.com ([fe80::2ce9:4479:69b6:d12c]) by DM5PR11MB2027.namprd11.prod.outlook.com ([fe80::2ce9:4479:69b6:d12c%4]) with mapi id 15.20.2094.013; Fri, 26 Jul 2019 15:54:34 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Susan Hares <shares@ndzh.com>, "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-bgp-ls-segment-routing-rld@ietf.org" <draft-ietf-idr-bgp-ls-segment-routing-rld@ietf.org>
Thread-Topic: [Lsr] Regd covering BGP-LS extensions for IGP ELC drafts
Thread-Index: AdVDOlNklon4K6l2RS+sYO6Udv7qoQAI5siAABsB0eA=
Date: Fri, 26 Jul 2019 15:54:34 +0000
Message-ID: <DM5PR11MB202734047D3C9F4B8E04C4DFC1C00@DM5PR11MB2027.namprd11.prod.outlook.com>
References: <DM5PR11MB20275193C3594D11F683734AC1C10@DM5PR11MB2027.namprd11.prod.outlook.com> <008401d5435d$ef56a470$ce03ed50$@ndzh.com>
In-Reply-To: <008401d5435d$ef56a470$ce03ed50$@ndzh.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=ketant@cisco.com;
x-originating-ip: [2001:420:c0c8:1002::bb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ce685ca6-865c-445b-be8c-08d711e18e49
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5PR11MB1468;
x-ms-traffictypediagnostic: DM5PR11MB1468:
x-ms-exchange-purlcount: 8
x-microsoft-antispam-prvs: <DM5PR11MB14681C217D8D3D5121E2349CC1C00@DM5PR11MB1468.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01106E96F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(396003)(346002)(136003)(366004)(39860400002)(189003)(199004)(6116002)(14454004)(55016002)(7696005)(52536014)(71190400001)(6246003)(53546011)(81166006)(316002)(81156014)(9686003)(76176011)(7736002)(54896002)(2501003)(64756008)(71200400001)(186003)(790700001)(446003)(606006)(74316002)(66946007)(76116006)(66476007)(9326002)(11346002)(6506007)(4326008)(66446008)(6436002)(8676002)(54906003)(229853002)(110136005)(6306002)(86362001)(8936002)(966005)(486006)(256004)(476003)(25786009)(478600001)(46003)(33656002)(5660300002)(66556008)(53936002)(99286004)(2906002)(102836004)(68736007)(236005); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1468; H:DM5PR11MB2027.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: V4ySkmN7eDlDtrbmhLRlTR3e4xkqhDYX5v0mVosM2w+JzJcEbkmr9zUupd1XDaO3UtzBSyWikWP0PpP/6jp2YtQ31tpEYlT6AoHtrataLoZO+WMEV5MtzJEYjgkwgXVMkakbU0Rm+8efRrhesIMhZuObgx03+rjQJXc7VHQ/R2xo7Ae6MA3breudvlliCo4noHxykkSKk76uSi+VaYSPCs577EyDdx0i5z6XExnABepyZ1QUy55cOQGGuwIgCIgWj0d15BUYzniWIMiGLcvqoavLQZ8Q4GE1C136K9JD2bAHDuwHFLC05MyF2V6qqoas+6b6eTYnyOV9NACiJcRF79L0czMoSlWzcPT+O9nPW45bP68NiTMmVy55iPWnwz88+xUDLjhC5ZxQUEUtn6s/WpM0O7gYNTgyWPYaHddDJ8w=
Content-Type: multipart/alternative; boundary="_000_DM5PR11MB202734047D3C9F4B8E04C4DFC1C00DM5PR11MB2027namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ce685ca6-865c-445b-be8c-08d711e18e49
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2019 15:54:34.7394 (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: ketant@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1468
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GnrI966zaOmEKRUVWy-u9suzo7o>
Subject: Re: [Idr] [Lsr] Regd covering BGP-LS extensions for IGP ELC drafts
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jul 2019 15:54:41 -0000

Hi Sue,

In this specific case, I would like to point that we would be marking an IDR WG document (https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-rld/) as being “replaced” by the 2 LSR documents below.

https://datatracker.ietf.org/doc/draft-ietf-isis-mpls-elc/
https://datatracker.ietf.org/doc/draft-ietf-ospf-mpls-elc/

Thanks,
Ketan

From: Susan Hares <shares@ndzh.com>
Sent: 25 July 2019 22:58
To: Ketan Talaulikar (ketant) <ketant@cisco.com>om>; Acee Lindem (acee) <acee@cisco.com>om>; lsr@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-bgp-ls-segment-routing-rld@ietf.org
Subject: RE: [Lsr] Regd covering BGP-LS extensions for IGP ELC drafts

Ketan and Acee:

The IDR co-chairs (John and I) wish to reduce the number of trivial drafts for BGP-LS allocations that could be done with 1 sentence.   We discussed with the LSR chairs (Acee and Chris) that it would be reasonable for LSR to do what Ketan has requested.

We suggest that the WG LC is sent to IDR and LSR in case someone wants to discuss a concern.   The LSR chairs are capable and smart.   Acee and Chris can help shepherd these LSR drafts with BGP TLV language.

Sue

PS – has anyone heard if Chris Hopps is a father yet?


From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Ketan Talaulikar (ketant)
Sent: Thursday, July 25, 2019 6:43 PM
To: Acee Lindem (acee); lsr@ietf.org<mailto:lsr@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-bgp-ls-segment-routing-rld@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-rld@ietf.org>
Subject: [Lsr] Regd covering BGP-LS extensions for IGP ELC drafts

Hi Acee/All,

During the LSR WG meeting on Monday, we talked about covering the BGP-LS aspects of the following two IGP drafts in those drafts instead of requiring a separate document:

https://datatracker.ietf.org/doc/draft-ietf-isis-mpls-elc/
https://datatracker.ietf.org/doc/draft-ietf-ospf-mpls-elc/

Originally, these IGP drafts introduced a new node capability that required a new BGP-LS TLV and this was captured in the IDR WG document https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-rld/

However after the discussion in the LSR WG over the last few months, the approach has changed such that the IGP signalling is being done by introduction of new flags and MSD-type. This makes the corresponding BGP-LS updates quite trivial and as discussed in the LSR WG, I would recommend to add some text (proposed below) to the two IGP documents.

OSPF:

The OSPF extensions defined in this document can be advertised via BGP-LS [RFC7752] using existing BGP-LS TLVs. The flags field of the OSPFv2 Extended Prefix TLV and the OSPFv3 PrefixOptions where the ELC Flag introduced in this document is advertised using the Prefix Attribute Flags TLV (TLV 1170) of the BGP-LS IPv4/IPv6 Prefix NLRI Attribute [https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-ext-16#section-2.3.2]. The new ERLD MSD-type introduced for OSPF by this document is advertised using the Node MSD TLV (TLV 266) of BGP-LS Node NLRI Attribute [https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-msd-05#section-3].

ISIS:

The IS-IS extensions defined in this document can be advertised via BGP-LS [RFC7752] using existing BGP-LS TLVs. The Prefix Attribute Flags sub-TLV where the ELC Flag is introduced in this document is advertised using the Prefix Attribute Flags TLV (TLV 1170) of the BGP-LS IPv4/IPv6 Prefix NLRI Attribute [https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-ext-16#section-2.3.2]. The new ERLD MSD-type introduced for IS-IS by this document is advertised using the Node MSD TLV (TLV 266) of BGP-LS Node NLRI Attribute [https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-msd-05#section-3].



I am copying the IDR WG and authors of the BGP-LS ERLD draft as well for their inputs/feedback.

Thanks,
Ketan

From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of Acee Lindem (acee)
Sent: 25 July 2019 16:28
To: lsr@ietf.org<mailto:lsr@ietf.org>
Subject: [Lsr] IETF 105 LSR Working Group Meeting Minutes

I think we had some very good discussions in our sessions this week. I’ve uploaded the minutes for the both LSR sessions on Monday. Thanks much to Yingzhen Qu for taking them.

https://datatracker.ietf.org/meeting/105/materials/minutes-105-lsr-00

Thanks,
Acee