[Idr] Update to RFC7752 to address comments/discussions in IDR WG
"Ketan Talaulikar (ketant)" <ketant@cisco.com> Mon, 25 March 2019 08:28 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 8E0AB120397 for <idr@ietfa.amsl.com>; Mon, 25 Mar 2019 01:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.944
X-Spam-Level:
X-Spam-Status: No, score=-11.944 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.157, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, 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=mVKnppmQ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=UU98Jbio
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 qLOGimJSZsTI for <idr@ietfa.amsl.com>; Mon, 25 Mar 2019 01:28:31 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8E81120370 for <idr@ietf.org>; Mon, 25 Mar 2019 01:28:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=779821; q=dns/txt; s=iport; t=1553502510; x=1554712110; h=from:to:subject:date:message-id:mime-version; bh=Y0s3+mF3/RQDbRuMIaU29FK5tOrnOAKlKx5Fls+r2Pc=; b=mVKnppmQBCrLUboV1GU7Kq0imLFuVzOCLLNqJcieYQgBRuqnLha8jsEq XbeP49Q6JvEtWhkhUqB01eZl2Bnn6Clxw/sLAYYvHZq6+oYutY0GO5tnM cLRS8PKbWEFezcDPQO5WHtEWaHLYiZYJINd8arpcw2fdGxAv2MNGsUG0z s=;
X-Files: Diff_ rfc7752.txt - draft-ketant-idr-rfc7752bis-00.txt.html : 565877
IronPort-PHdr: 9a23:KX1PXxLvsHyPfQcz4tmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeCtKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXE72MPfscwQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DOBACZkJhc/4cNJK2GZb81EwKBCguGETrABY5/
X-IronPort-AV: E=Sophos;i="5.60,256,1549929600"; d="html'217?scan'217,208,217";a="251237243"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Mar 2019 08:28:29 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x2P8STQa032641 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Mon, 25 Mar 2019 08:28:29 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Mar 2019 03:28:29 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 25 Mar 2019 03:28:27 -0500
Received: from NAM01-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; Mon, 25 Mar 2019 03:28:27 -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=2SdlDfbsoE0a0yrytXgd3PohoGw6hQiVvTiysbX5J4E=; b=UU98JbiouIFSAdRWDC6xmNGhmO6uRErMT5wgnoh8OJrLdN+NmaK5K2wb+2c+lAIESZOOAt3r6hI0fbK6p7rEVqHg+MSjNww2og/WhIGMs2PpBuSpXU2AdE5AnGkgBcAEseQHiSpU++145DXwu6QdUYplZHnxw30OO+sHbcw2vqY=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB3520.namprd11.prod.outlook.com (52.135.125.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.18; Mon, 25 Mar 2019 08:28:26 +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; Mon, 25 Mar 2019 08:28:26 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Update to RFC7752 to address comments/discussions in IDR WG
Thread-Index: AdTi5K7odOXiYDDxTACwQ3gZg1IpVQ==
Date: Mon, 25 Mar 2019 08:28:25 +0000
Message-ID: <SN6PR11MB28459A01D546890B0C14AC10C15E0@SN6PR11MB2845.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [2001:420:c0e0:1005::381]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 359da677-5e28-45b4-3211-08d6b0fbda05
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:SN6PR11MB3520;
x-ms-traffictypediagnostic: SN6PR11MB3520:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <SN6PR11MB3520085FD2BCCFC8838539E3C15E0@SN6PR11MB3520.namprd11.prod.outlook.com>
x-forefront-prvs: 0987ACA2E2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(346002)(396003)(136003)(376002)(53754006)(189003)(199004)(13464003)(966005)(478600001)(105586002)(106356001)(2351001)(99936001)(8676002)(8936002)(14454004)(81166006)(81156014)(1730700003)(66574012)(2501003)(33656002)(53546011)(6506007)(14444005)(102836004)(256004)(316002)(476003)(7696005)(486006)(6916009)(9686003)(6306002)(5024004)(55016002)(52536014)(5640700003)(15650500001)(305945005)(46003)(6116002)(5660300002)(2906002)(6346003)(99286004)(97736004)(68736007)(71190400001)(71200400001)(6436002)(186003)(74316002)(7736002)(86362001)(53936002)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3520; H:SN6PR11MB2845.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)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ketant@cisco.com;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5/J2ehwh441RmUcC0gewLKefnqW31OLNTeYdr+kduZ8DRgukrMsjfF82sdQrg3AGIhjZRovqDeHeIg/zc8T8Wb+k+sdnFMNz60KXmGe6flHzKX1o+WriRPmeFTudlSTWBdiKffDp7xvZnSky4pEc2JWswlLjoh8DVlafh7LF+gnVj+lUchvjzgZ9lBZ5j5B4XcMso1Ioi8uPmd7IPqb6xYcYRQxh/x8fipssBxbG8x3BjWat7qMK5CPXePj0L0OMo5Z1XGFrZ6X81c+G5WdK9UB4szpShc39gepPzSEbMZUcr4jWrBE+rnkAxoJDRGa8/Z+IkU47Oo8Eq8SGGNxE9XJXufG0ooU8lcQxRnSfWv6x318s4ICrrwLDDG30FpZe+vLQ8gZIB0vcuzEl7Wr9YW96XoKOoSPYUFxztAeDJnY=
Content-Type: multipart/mixed; boundary="_002_SN6PR11MB28459A01D546890B0C14AC10C15E0SN6PR11MB2845namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 359da677-5e28-45b4-3211-08d6b0fbda05
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2019 08:28:25.9386 (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: SN6PR11MB3520
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/5a3pT0zhC-s8Ls2-HNnpGg3wHY0>
Subject: [Idr] Update to RFC7752 to address comments/discussions in IDR WG
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: Mon, 25 Mar 2019 08:28:47 -0000
Hello All, There have been several discussions on the mailing list, in past WG meetings and in offline discussions about the need to clarify certain aspects of BGP-LS. Some of these feedback/issues have been about TLV handling, fault management, growing BGP-LS attribute, session isolation, etc. Some of the points that have come up for discussions during review of BGP-LS extension drafts seem not specific to those extensions but aspects that need addressing in the base BGP-LS specification itself. Based on the feedback received from the chairs and also Alvaro (RTG AD), we are proposing an update to RFC7752 to address some of these issues raised as also other aspects that we've learnt based on implementation and deployment. This topic would be likely presented in the IDR WG session later today. My apologies for the delay in sharing this draft for review with the WG before the cut-off. I hope it serves as a basis for us to discuss in the meeting, on the mailer as well as in person in Prague. The Appendix includes a high-level overview of the changes since RFC7752 and I am also attaching a diff of this draft from RFC7752. Thanks, Ketan -----Original Message----- From: internet-drafts@ietf.org <internet-drafts@ietf.org> Sent: 25 March 2019 09:13 To: Adrian Farrel <adrian@olddog.co.uk>; Jan Medved (jmedved) <jmedved@cisco.com>; Saikat Ray <raysaikat@gmail.com>; Ketan Talaulikar (ketant) <ketant@cisco.com>; Hannes Gredler <hannes@rtbrick.com>; Stefano Previdi <stefano@previdi.net> Subject: New Version Notification for draft-ketant-idr-rfc7752bis-00.txt A new version of I-D, draft-ketant-idr-rfc7752bis-00.txt has been successfully submitted by Ketan Talaulikar and posted to the IETF repository. Name: draft-ketant-idr-rfc7752bis Revision: 00 Title: Distribution of Link-State and Traffic Engineering Information Using BGP Document date: 2019-03-25 Group: Individual Submission Pages: 58 URL: https://www.ietf.org/internet-drafts/draft-ketant-idr-rfc7752bis-00.txt Status: https://datatracker.ietf.org/doc/draft-ketant-idr-rfc7752bis/ Htmlized: https://tools.ietf.org/html/draft-ketant-idr-rfc7752bis-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-ketant-idr-rfc7752bis Abstract: In a number of environments, a component external to a network is called upon to perform computations based on the network topology and current state of the connections within the network, including Traffic Engineering (TE) information. This is information typically distributed by IGP routing protocols within the network. This document describes a mechanism by which link-state and TE information can be collected from networks and shared with external components using the BGP routing protocol. This is achieved using a new BGP Network Layer Reachability Information (NLRI) encoding format. The mechanism is applicable to physical and virtual IGP links. The mechanism described is subject to policy control. Applications of this technique include Application-Layer Traffic Optimization (ALTO) servers and Path Computation Elements (PCEs). Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
- [Idr] Update to RFC7752 to address comments/discu… Ketan Talaulikar (ketant)