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

"Acee Lindem (acee)" <acee@cisco.com> Fri, 26 July 2019 12:54 UTC

Return-Path: <acee@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 B29F712021D; Fri, 26 Jul 2019 05:54:44 -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=RdAYWLr3; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=bI4YegfC
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 f0FG7nlYq1r9; Fri, 26 Jul 2019 05:54:43 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACB0B120236; Fri, 26 Jul 2019 05:54:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24977; q=dns/txt; s=iport; t=1564145682; x=1565355282; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=nNQsPIvm1DwCLz79/uAxCXCl0hj3suFGiTRdpLqkByU=; b=RdAYWLr3+9MMA25VZRJtfzZwOiLfXLfO7jeV3XPFQjPOFrRqU3w1gZHh jv4OBhPCkzyWAzaNkKltyP6MDe6lZ2xET/lw9XxfmZmHqEpwjghHSaZRS QfmJ6L6jTGvE4jYM88rcZfu1Iy3I5IpPt8K9A833k3dXMgTuxZb9LbZoX U=;
IronPort-PHdr: 9a23:sTjt9hbszhz+g4tE1dIkZAz/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20QKbRp3VvvRDjeee87vtX2AN+96giDgDa9QNHwQAld1QmgUhBMCfDkiuJfXnYgQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAACC9zpd/5tdJa1mGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwQBAQEBAQsBgRQvUANtVSAECyqEHoNHA4RSiC2CW36WVYEugSQDVAkBAQEMAQElCAIBAYRAAheCSyM0CQ4BAwEBBAEBAgEGbYUeDIVKAQEBAQMSCwYdAQE3AQ8CAQgOAwMBAQEoAwICAjAUCQgBAQQBDQUigwABgR1NAx0BDqENAoE4iGBxgTKCegEBBYEyAQMCAgxBgwAYghMDBoE0AYteF4F/gRABJx+CFwcuPoJhAQECAQGBfQYHCYJVMoImjn6Ef4htjg4JAoIahlmNNxuYDI06h0qQCwIEAgQFAg4BAQWBUDiBWHAVOyoBgkGCQoNxhRSFPgFyAQGBJ41VAQE
X-IronPort-AV: E=Sophos;i="5.64,310,1559520000"; d="scan'208,217";a="301588491"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Jul 2019 12:54:41 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x6QCsfmg017044 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 Jul 2019 12:54:41 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 07:54:41 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 07:54:40 -0500
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 26 Jul 2019 07:54:40 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gaO9sYdjPFJRRcGTG1r1anZmBcRqz4j8n5EV3/qS/ywJYelKQ2VvfN30KMX3feu8lJv9dBqrheEk7Wm0uAZ98fuX/UVWNS2l29GQrIntZKFSdQe9R4P3Jj4fuUll3R+ky32AU6mBePuf0W4A/XKbAzIOgYEd5RJ+2T2y6N4I8a9cndEp1mhTB34mpvPDipZSo7FLMwWE/sM+lHOIRahL3g8/SSAVKzw+m2j8pq9WWyWrl6038tO5Zs4uZLMjXuPXGpCtVEpnIbqQqzCVtvAzOb/F0eShU4vj/Deq+E/jg6kR/2aKPSj46NFhCdMmi314Aam2nvEqDGK2p960zL+A1Q==
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=nNQsPIvm1DwCLz79/uAxCXCl0hj3suFGiTRdpLqkByU=; b=bN517sP9T9xoS2ecaTYxWIFwr+tOwUhjmTvxhnW8myWqmo6ZhrcBdj59U1C/X9j1wqolgemZytCe1DFKr6R+LMJRkVWxA4J70XkQVUVU/djW8nwKmRLvsj06nGdZHJkxFCVo3Y8ArWuTEd8MpQuUN7PDHbzaYwv2xj/XBYlY19PTqUOhlJdzCkxO7KG3xnIMci4ZqKTVhiMoFQbcxlttS/65y3zUGA2DscuzFv28x6Jzb9Y+OXpXmqIaAVuwEgxGu8DOHOLLHbujv2rhBi+ho+9HSzvC4uZRnytK+UBYmjLLcpYdVRN3xdwOVezPEhkSFvPzYQ2RvBuheHg3095Vsw==
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=nNQsPIvm1DwCLz79/uAxCXCl0hj3suFGiTRdpLqkByU=; b=bI4YegfCCzksIzmjDqn08uuV+OYzU5/WkEK1DquZ4LIsNMb5LDCUX04uXNbJAAqgkqHb/3sBcoimD7byTTdLDfZZhfw8CSrj3A7RdjkKUtG20QYnMnMhYI5DQ56bOAM6kUXGrSLFxB2snrxw9jvphl5sffMrnvXRMiHtPN1kHq4=
Received: from MWHPR11MB1902.namprd11.prod.outlook.com (10.175.53.139) by MWHPR11MB2015.namprd11.prod.outlook.com (10.169.236.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.10; Fri, 26 Jul 2019 12:54:38 +0000
Received: from MWHPR11MB1902.namprd11.prod.outlook.com ([fe80::64fa:549d:e02a:a2b2]) by MWHPR11MB1902.namprd11.prod.outlook.com ([fe80::64fa:549d:e02a:a2b2%5]) with mapi id 15.20.2115.005; Fri, 26 Jul 2019 12:54:38 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Susan Hares <shares@ndzh.com>, "Ketan Talaulikar (ketant)" <ketant@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+sYO6Udv7qoQAI5siAAAx0jYA=
Date: Fri, 26 Jul 2019 12:54:37 +0000
Message-ID: <95B88C9A-79EE-4B1D-91D9-9EB7E38D1059@cisco.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=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1003::3d5]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7777f000-4b82-4f7e-90f4-08d711c86b04
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MWHPR11MB2015;
x-ms-traffictypediagnostic: MWHPR11MB2015:
x-ms-exchange-purlcount: 8
x-microsoft-antispam-prvs: <MWHPR11MB20152D0D739A1DA93DC9A752C2C00@MWHPR11MB2015.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01106E96F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(366004)(136003)(346002)(396003)(199004)(189003)(476003)(486006)(54906003)(6116002)(6512007)(53936002)(6246003)(236005)(5660300002)(99286004)(25786009)(966005)(76116006)(66446008)(14454004)(186003)(54896002)(2501003)(110136005)(7736002)(76176011)(102836004)(71190400001)(68736007)(6436002)(71200400001)(8676002)(4326008)(6506007)(53546011)(8936002)(478600001)(9326002)(86362001)(256004)(6306002)(229853002)(66476007)(446003)(66946007)(81166006)(2616005)(81156014)(33656002)(11346002)(66556008)(36756003)(2906002)(606006)(46003)(316002)(91956017)(6486002)(64756008); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB2015; H:MWHPR11MB1902.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-message-info: r8uxEoAXLn+b2q7QSbZePcT4tKdJ5Wf3CSThChT4hZ5KJue/w9s93OhWZCVjO45lVF6S8OY9JUbKqfBEX31hoQ7TS6hk6/2AIXojD3ZhOs7SiIOvJ9Txp7aFUZT+NYBvZDk3z1xGZvVYlFRw6Keao6vbldEOW3KTXUXvJHgatXRIAV0h2cJv/o+jB6Wd5IPXhUhx/RZASxjAjl2xA76x0Ac04J2GLAXhG9CaZdUncxGLpggSSZ+ftjm9dwfJUHX2QaujQYNqLdqzfUHUvkHyY3YkNkSO/u1/qX84AejHbU3cQSQno/jfuWzoNTaihugFGZgCntGQR4B9Je2FcUpueb/pB0Nzt+2SjSQILDLFv49+mMAhK/WW+NoXegHs940rDqNagtTffBUtloERIg/hIEjr6K+zhWTDWLG+3AAXdlY=
Content-Type: multipart/alternative; boundary="_000_95B88C9A79EE4B1D91D99EB7E38D1059ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7777f000-4b82-4f7e-90f4-08d711c86b04
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2019 12:54:38.0235 (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: acee@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB2015
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qvQyKKeZONp1YJmN431I0wYmYHI>
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 12:54:45 -0000

Hi Sue,

From: Susan Hares <shares@ndzh.com>
Date: Thursday, July 25, 2019 at 10:58 PM
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Acee Lindem <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Cc: IDR List <idr@ietf.org>, "draft-ietf-idr-bgp-ls-segment-routing-rld@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.

We will include the IDR list on the WG last call for drafts that specify BGP-LS.



Sue

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

Not yet.

Thanks,
Acee


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
Cc: idr@ietf.org; 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> On Behalf Of Acee Lindem (acee)
Sent: 25 July 2019 16:28
To: 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