[Idr] Comments on draft-hegde-idr-bgp-ls-epe-inter-as-00
"Ketan Talaulikar (ketant)" <ketant@cisco.com> Tue, 26 March 2019 16:58 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 3D0841206BB; Tue, 26 Mar 2019 09:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=U2Nrg5Iy; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=EJkRwddY
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 lqSjBOoXhClY; Tue, 26 Mar 2019 09:58:05 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7390C1206C8; Tue, 26 Mar 2019 09:58:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1410; q=dns/txt; s=iport; t=1553619484; x=1554829084; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=mpkCpXAgn2iTeRH9Pen1rm5Hc3qP9VucTTZ9lwFMjXY=; b=U2Nrg5IyHG+W0tmbqKT8fMdplg5nHA4qf6Mg4sC+DBIUq5R/PAejxU1R pfL9HAEO4Y9PZGvVytjLz5BBTCuKkkvcBdJfzEP6VjRB/hJVO2R4f45pc EIvdGyvnC5xErRzCDhp8atg/qp7yGGJPu4vn8dfQV9cI2y6CGNPFTwbHj 0=;
IronPort-PHdr: 9a23:hDB1MRG6JpbPnPvL3b7TsZ1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4w3Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+ef3ncyU8AOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAADYWZpc/4QNJK1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgT0kLANodAQLJ4dVA4RSiluZZIEugSQDVA0BASMJhEAChSIiNAkNAQEDAQEJAQMCbRwBC4YLBgEBJRIBEQE+QiYBBA4NgxuBXQMVAQIMohsCihSCIIJ4AQEFgTUCg0wYggwDBYEvAYsxF4FAP4ERRoVrAQEDgRpGgzmCJootmm8JAoF/hWKLcZQCix2GBo0sAgQCBAUCDgEBBYFNOIFWcBWDJ4IKDBeDS4UUhT9ygSiPFAEB
X-IronPort-AV: E=Sophos;i="5.60,273,1549929600"; d="scan'208";a="529321636"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Mar 2019 16:57:59 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x2QGvv3h022788 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 26 Mar 2019 16:57:57 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 26 Mar 2019 11:57:56 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 26 Mar 2019 12:57:55 -0400
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 26 Mar 2019 11:57:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mpkCpXAgn2iTeRH9Pen1rm5Hc3qP9VucTTZ9lwFMjXY=; b=EJkRwddYa3dXRgiEmfM4+YTWF0IKn4yr02obpBFvE17+WJVDRufm+IcXGC3sVpJf/k6CcK5M93/2GgX8xHcpQeSa+IE9AEiTny3tlC7ISHd05SNEa9yZHFjmwXmRnCHZQavQPcQgdDgyM6u+FOW8MIb1DZxmOn7E7GGurduF3Ww=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB2813.namprd11.prod.outlook.com (52.135.93.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.15; Tue, 26 Mar 2019 16:57:53 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::ddd2:508a:e4e8:49b2]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::ddd2:508a:e4e8:49b2%3]) with mapi id 15.20.1730.019; Tue, 26 Mar 2019 16:57:53 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "draft-hegde-idr-bgp-ls-epe-inter-as@ietf.org" <draft-hegde-idr-bgp-ls-epe-inter-as@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Comments on draft-hegde-idr-bgp-ls-epe-inter-as-00
Thread-Index: AdTj8Oxb1mhZw8f0RP6O8MTUg8xH7g==
Date: Tue, 26 Mar 2019 16:57:53 +0000
Message-ID: <SN6PR11MB28459697EBF5E940AC496E1AC15F0@SN6PR11MB2845.namprd11.prod.outlook.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:c0e0:1005::381]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e86c5fee-021c-4703-3d74-08d6b20c301f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:SN6PR11MB2813;
x-ms-traffictypediagnostic: SN6PR11MB2813:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <SN6PR11MB2813497F9C673DF88CAE756DC15F0@SN6PR11MB2813.namprd11.prod.outlook.com>
x-forefront-prvs: 09888BC01D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(39860400002)(136003)(396003)(376002)(199004)(189003)(2501003)(6116002)(8676002)(186003)(4326008)(450100002)(6916009)(5660300002)(561944003)(7696005)(14454004)(33656002)(99286004)(2906002)(6506007)(71190400001)(25786009)(102836004)(81156014)(476003)(486006)(81166006)(71200400001)(53936002)(55016002)(6306002)(9686003)(52536014)(5640700003)(966005)(7736002)(14444005)(256004)(305945005)(8936002)(74316002)(6436002)(68736007)(106356001)(46003)(478600001)(97736004)(105586002)(86362001)(2351001)(316002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2813; H:SN6PR11MB2845.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: ipaqSk5RfVVNd5LPO517fDxMqRzCl4SoigdkdcjWEUNDVBbeqZFaDrQgWXRvPoaiCbBEfNWGxl4UI9Q3T10cZ92eN8RdcOYzIX8u/6X5UgNqTaaM/BtewPRiZZAeDnQkQG22iaP2g+r2tl/mlhrZNmMSesQf00MPo0dq7necSt694sUn6JsQ0jL20r9+ycJeXfZL2xFs0fk45jf8fWn9wEvBT9a7DI3pgrs9xsiqnxU5sfppaoR6gmZV2jKJnBKM5p62DkBNHhHEtWxvf1ukuJ7IkyvPVzMBfu2EgvfBFECHdQkwwtngpMuuTezWhv77CmPHjxyztzwYOIFr9B56jP2QcjlfbL3f4nrJfQbtX8TYtuO+6hl9LjtraLpeTubHmZErbSH4+D573R3m9SvbXpuJFClRDJoJJguNmDpmnJo=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e86c5fee-021c-4703-3d74-08d6b20c301f
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Mar 2019 16:57:53.5078 (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-Transport-CrossTenantHeadersStamped: SN6PR11MB2813
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/EHbhgH9af2fj3-51JXignv-UKY4>
Subject: [Idr] Comments on draft-hegde-idr-bgp-ls-epe-inter-as-00
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: Tue, 26 Mar 2019 16:58:16 -0000
Hi Shraddha/Srihari, Some comments on this draft that was presented at IDR session on Monday. Sec 3 talks about the F flag and that it is set on the "FRR SID". I get the impression that this introduces new/additional BGP Peering SIDs called "FRR SID" to provide backup for some "normal" BGP Peering SIDs. It would help if additional text and clarification with examples were provided to indicate how this is all achieved and the proposal to advertise all these "FRR SID" and their association with the "normal" BGP Peering SIDs. The new thing being proposed in this draft in Sec 4 is about including the Local Address TLVs along with the Link NLRI that represents the BGP Peering session and carries the BGP Peer Node SID TLV so that it may be possible to map the underlying Link NLRIs that are associated with the BGP Peer Adjacency SID TLVs. I believe this aspect is useful. I would suggest to reuse TLV 259 and 261 instead of having to define new TLVs and codepoints - you would find they are exactly what you are proposing to introduce. Regarding advertisement of other details and TE attributes for Inter-AS links, I would request you to check/review https://tools.ietf.org/html/draft-ketant-idr-bgp-ls-bgp-only-fabric-02 which covers this topic. It is applicable to any BGP-only network or part of it including the Inter-AS links. Thanks, Ketan
- [Idr] Comments on draft-hegde-idr-bgp-ls-epe-inte… Ketan Talaulikar (ketant)
- Re: [Idr] Comments on draft-hegde-idr-bgp-ls-epe-… Srihari Sangli