Return-Path: 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 0A99EC14F61D for ; Fri, 6 Sep 2024 13:03:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kl_ASIpGIW2I for ; Fri, 6 Sep 2024 13:03:50 -0700 (PDT) Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2130.outbound.protection.outlook.com [40.107.94.130]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC82EC14F61C for ; Fri, 6 Sep 2024 13:03:49 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=pass; b=VQCAHxU91YAIugQ7F3lwsILZB81maraYagkbYYmMGKD3SlZbPKExNs7wdcVwwNYl0sUK6tDA9sHrTCCH7qXpYyr2ekshZDTEbuUeC1seARyqdS2d1M3iMAyAySe5Xxar+w5SAE/DIBUQJGB6wCCiK5Je8wqXytVEiECVROdq06yB1RsBYDjrx1d5ddTgsV8WdYbT+fhtEjvNkkFFC463Inh23vS9y67mv0F9Zyd1BM9CkiWFAHhAKx7tusO+YJzv84d5zOKRYKkkG+1kJUBKTqMLDRHyz4PEsOpU3iHBDP0qzTa8yuiFogptFsALae1B4K1TWGcuV3bB0EjqHrQ7qw== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=XEImUh63z79/+EOUhFjXDN3ETgB2PMxUiOdzGy7egGE=; b=t/An9JIH8WDxl4yPNUXw3dhtM63uFmU6TgSug4SVuJZZpJU84BJlxOgeVU0MjIrNT9t15+4cGtj+zUhDEnBnqID3xyI3RI8qJtVTX/bShcm3kIBDGnZ7LxtuEDEh9guqKVLiLjqXIcwaYjPJG3WX6iiYkOi/9kcjeaCYhoNlAUCQRRVn3NmGacIyjqxKDX6j3jfAwYNuqjR6xTKlJZ5eRajpyS7KIK7Ooycq6Rrjg9dii9PA6yUSl+7uaElnbx+O8kW4kLP4ZjH3EQb8p6mvvQoIX5M0J+fZJGD425Az/jLj7D3SpBb9WDSuOv0xETVhpeYzPKvi4PCu2FovNE8Qlg== ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 104.47.55.45) smtp.rcpttodomain=ietf.org smtp.mailfrom=ndzh.com; dmarc=bestguesspass action=none header.from=ndzh.com; dkim=none (message not signed); arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=ndzh.com] dkim=[1,1,header.d=ndzh.com] dmarc=[1,1,header.from=ndzh.com]) Received: from CH5P223CA0012.NAMP223.PROD.OUTLOOK.COM (2603:10b6:610:1f3::26) by CH0PR08MB7338.namprd08.prod.outlook.com (2603:10b6:610:113::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7918.28; Fri, 6 Sep 2024 20:03:46 +0000 Received: from CH1PEPF0000AD81.namprd04.prod.outlook.com (2603:10b6:610:1f3:cafe::b4) by CH5P223CA0012.outlook.office365.com (2603:10b6:610:1f3::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7939.17 via Frontend Transport; Fri, 6 Sep 2024 20:03:46 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 104.47.55.45) smtp.mailfrom=ndzh.com; dkim=none (message not signed) header.d=none;dmarc=bestguesspass action=none header.from=ndzh.com; Received-SPF: Pass (protection.outlook.com: domain of ndzh.com designates 104.47.55.45 as permitted sender) receiver=protection.outlook.com; client-ip=104.47.55.45; helo=NAM10-MW2-obe.outbound.protection.outlook.com; pr=C Received: from obx-outbound.inkyphishfence.com (52.4.92.69) by CH1PEPF0000AD81.mail.protection.outlook.com (10.167.244.89) with Microsoft SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.7918.13 via Frontend Transport; Fri, 6 Sep 2024 20:03:46 +0000 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10lp2045.outbound.protection.outlook.com [104.47.55.45]) by obx-inbound.inkyphishfence.com (Postfix) with ESMTPS id 03930102DFA for ; Fri, 6 Sep 2024 20:03:45 +0000 (UTC) ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=W4DdygKvs2EKcOjEO2xRvvK4jITzeRfbAa+4R6hMtW7WofNBJtJ/VYqA76ipWnHZSYHqAgUDl0Nh9Qw1rYXXxZ/EtSs2nr7pR81XKUdOhm1lURr59ob5WKpjVWVTLArV2S2HixIsDRbcjv4mVVjCOSQQCPq665M48RNGXEeRanowcETdyWCH+jcB0vBuHwQBMGkSdugVgbmkCWJmxXjIZRn2gNDa5eEXeu0bPSqmYOsSUE+kT5HDeKs5gtSPbgc686HgtZ0uqf0obLiSnDJQzevw1MCDLE7viPTIHGUV/QrIYfpGok08GSlPQV1233h3EMJqRiwfQDEiRV7uPcRe9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=XEImUh63z79/+EOUhFjXDN3ETgB2PMxUiOdzGy7egGE=; b=mRfIlCiYO0UUEsdcNN+Go0hWHEkKzVykjgDKd1/0gPaM9NtlDkSEXfGVLERecJwVn5FP1gnTQX7pkWufqneY1G/TOCIRmN9ZP0IfXcr43Lk51awKjkcOWEI4+CP4c+UY2TLNGudIKtrVedVsM9/l5niG3aCVXkxbQyiKdjmWMWYoYQWAbXeEKSqdPqDUMtO5TWb6QNwq/7K6oPXQO0ToAS8j756lwVoyrPCFvyjNU87/QTeP062AM/vt3LWdtwnYji/t4ZHkj5twnACuQ9AifiE+/epFC3UoXDNUa+b8Fu6VtcUffXlTFgLjHFxka1KwzH9H8jYU/ZoSE5xwb6TWSA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ndzh.com; dmarc=pass action=none header.from=ndzh.com; dkim=pass header.d=ndzh.com; arc=none Received: from CO1PR08MB6611.namprd08.prod.outlook.com (2603:10b6:303:98::12) by BL3PR08MB7481.namprd08.prod.outlook.com (2603:10b6:208:340::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7918.27; Fri, 6 Sep 2024 20:03:42 +0000 Received: from CO1PR08MB6611.namprd08.prod.outlook.com ([fe80::7744:8abd:9769:c2bf]) by CO1PR08MB6611.namprd08.prod.outlook.com ([fe80::7744:8abd:9769:c2bf%5]) with mapi id 15.20.7918.024; Fri, 6 Sep 2024 20:03:41 +0000 From: Susan Hares To: "idr@ietf.org" Thread-Topic: Brief Shepherd Reports on 10 BGP-LS Individual drafts proposed to IDR Thread-Index: AdsAlkL1BCJARz4ORziY3DnAFHdVZg== Date: Fri, 6 Sep 2024 20:03:41 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Authentication-Results-Original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ndzh.com; x-ms-traffictypediagnostic: CO1PR08MB6611:EE_|BL3PR08MB7481:EE_|CH1PEPF0000AD81:EE_|CH0PR08MB7338:EE_ X-MS-Office365-Filtering-Correlation-Id: b5248c68-de27-497e-f925-08dcceaf03f9 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam-Untrusted: BCL:0;ARA:13230040|366016|376014|1800799024|38070700018; X-Microsoft-Antispam-Message-Info-Original: =?us-ascii?Q?ymkSHNDRNWfl8J5fRqvOlSxx0cCnjszv51+Rd8YC64IT45F2/chZjUZhVXxb?= =?us-ascii?Q?rdpb4Rw+FcZK45/uHGHt4OqKr6NH16mg9JJ/voCcDabEeq9qc2f/GyTsplS0?= =?us-ascii?Q?Gvxp+G+QTqmgwSlp5IRM2Ne1BOiwZaBVBzg8LcLNl49cgJGijEhqDtt/Jj6o?= =?us-ascii?Q?VgfgONwoqNEU0ktrpJskeErjTI+SlGrvDWTh4lyaV42dZNI/BYSJWrL5KRuA?= =?us-ascii?Q?QOnfh1s+xGAM+VwQuVYFbJdZymqvPQotIIdNGZ8Mc25D7h1bDQbJC/KmEYJC?= =?us-ascii?Q?y0S6ZkLIuqq3UMW3KRh/aG7K2WTdEYnsNmxH16l4McfJymNBjBXQwa6JcsV1?= =?us-ascii?Q?6mtq8KHrGBjxSIY3d51JVOaluVCtETCV/ndQdjCrvZFaJilBt9Nk6iqItWsV?= =?us-ascii?Q?W6RuAKEwD4cTvLLtWQ9969HRSLn2Sqy9RRRqKsu7dTu5YzHkkEflTG9hRZUF?= =?us-ascii?Q?OUloRh+fBE+WGf2PmCeVAeyszlVyci5Ub3E69Ve1fTSQnTV1ax0JcaABRoqr?= =?us-ascii?Q?W7UI23JUPW3KWKsQxJghvzKtlC9BNRLJsix6/pmNO+kuGNJvLrT35sxtlNZ5?= =?us-ascii?Q?RAwupNfAVggfPQV4oxNIcwF7NQXb8Cdczej32ek/nfuGiAdxSACUsxw0+OO+?= =?us-ascii?Q?jV27hrk7qBMQbPPLPs2pvS8uN5g5ZLmFx18Udfj2n0OhiYfDYSIEq6JZVLXH?= =?us-ascii?Q?aMlZLbVcXrOiVp8Ty6OkZtygZQ7fhvT1OxsmCXtXypsXr4aOzC/lVXxRIF/k?= =?us-ascii?Q?E1PmSCsAWuIm6CXFIssF2DHMhWhYe3AHrvVD09Asrb73VAbxa+dfiOE9tJT1?= =?us-ascii?Q?tu826nEQEGvDlV2/68r0EnEX8gOR68CfZMNEyWb/GvVQ1d8H/NNcIXgU3MO/?= =?us-ascii?Q?iVyx5onHDTPNpaYS59iSzcF4KP+C/ClTvMW5O6FPiC6baQpDqP/5yYKkIEjH?= =?us-ascii?Q?coZXjyfyVXABgCOi8zXP6YA/T//ovuvA18BU8YlM+NUQovt4g7RAYRHmlVqI?= =?us-ascii?Q?yiASCMAViwh8DmMyrP20w6OWufFcTjYyLkHmnclXJjkLOHvSkG19sOH7/Oz8?= =?us-ascii?Q?ExiiLBEJlbsNyevkV4z77x0M+lYxSwpSUb4Xp3Lb+QlmnyoIkqlYHv8dVyno?= =?us-ascii?Q?j5i0UfmHWNxiuZ5Va4+IX0HeysSY8ce9s4LZV6aBq+/aJ4AiXINegHPh73ll?= =?us-ascii?Q?8vnFwdKoIN9EimSJq8FQB1OJ9vaimcIYQM8gRftCOMdXwSr+7kFE08E7J1/r?= =?us-ascii?Q?4nuBKblBz6OMcBU0cb075SBoROQQnnDcEfOAJgOKDZudyPuXYLcHIMRxZPgo?= =?us-ascii?Q?Rj+r/xk2AyKizxnDQ+UZxLsHUR4oz5Doq1rGF1mev454gqrXm6HNFc/mQLFV?= =?us-ascii?Q?yv8cAe7mCpwVYF67kqnJJ4S3PLiEBw2TyqQl1adyuwS0/kgSCg=3D=3D?= X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:CO1PR08MB6611.namprd08.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(376014)(1800799024)(38070700018);DIR:OUT;SFP:1102; Content-Type: multipart/alternative; boundary="_000_CO1PR08MB66111C34F7526B38CF604684B39E2CO1PR08MB6611namp_" MIME-Version: 1.0 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL3PR08MB7481 X-Inky-Outbound-Processed: True X-EOPAttributedMessage: 0 X-MS-Exchange-SkipListedInternetSender: ip=[104.47.55.45];domain=NAM10-MW2-obe.outbound.protection.outlook.com X-MS-Exchange-ExternalOriginalInternetSender: ip=[104.47.55.45];domain=NAM10-MW2-obe.outbound.protection.outlook.com X-MS-Exchange-Transport-CrossTenantHeadersStripped: CH1PEPF0000AD81.namprd04.prod.outlook.com X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id-Prvs: 9043c4c3-5325-4bc0-59f4-08dcceaf0130 X-IPW-GroupMember: False X-Microsoft-Antispam: BCL:0;ARA:13230040|36860700013|35042699022|82310400026|376014|1800799024; X-Microsoft-Antispam-Message-Info: vL9+Tfb69f6bWWz8qb/z5nN9p8tyvmxX9jhp4oSZBvJtL8sFwV6EryWvXHPnW6GJGr/osBjIWErHRTW3iLWt0o0Hxdy4e+ZzkZZnFY6+YNinMGd/ACSWM4+yOr76rjQtAJlBc0l+KmkltGRmPUonfdc1Pwu/DoQbZP/68m6DtEIk0Vpq8bAlOR7g4sWb9625RaVqC5JYa4oANkGYU/banjOwfKgB8d603cJQw+QJLWT8QrSx3v9VqWqDIlrMKWMEXXSxHz8IubV0h5ZPaHweJeY0faB4jMqJcceaLE53hei648VS76HQ/edjcxUGxs2fNvzbg1NlCCGkWHBeOiKAtWv+OuWQFNuOEeMgpctS9uVtFqN0r3ppa6w9TKc0GMntaBOiAotitbxZng6yPm/wWgVM7rflBq/TQ/OrxrEeF1zBqgR42WZu+lykLr5Z5hmXUQ3DnW6FRleVtXAYAbam9W0RNN2eoGUsKuCDweIpVnIaZE3wTLgSCJXcx5TVVDA7jcBQtjKcU3JxiagmOiVN8bLDMTxr/s5tDfQBu1G7qQM0Z9dEnckLADMmKpHhAZoUTDeqq1UdU56Anh2uq51e5+vGzfOvxOdNWfuSr/dckchjLbLca1ibQeHGaL1tOVUvU3mCXlsZ9oJy7zOCIHYzpY49uclby5UzVf8DQKk+AvtSA1K/7w0FWDPPuYymmhCsoNLQhunx+BxIq3qjRYyqcTJ1egUXgnRKACk0tVKZyZ7uOT3xMWi6bA7/THeSlH38CJLJ5pyK7TeuThmlGYZuMgXNY8tARRYMUy8M4B51/U/EKw/p7W63vmCCnZpxTvk7JYXPM8gKBQ1ZW0H8etEmVQ== X-Forefront-Antispam-Report: CIP:52.4.92.69;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:NAM10-MW2-obe.outbound.protection.outlook.com;PTR:mail-mw2nam10lp2045.outbound.protection.outlook.com;CAT:NONE;SFS:(13230040)(36860700013)(35042699022)(82310400026)(376014)(1800799024);DIR:OUT;SFP:1102; X-OriginatorOrg: ndzh.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Sep 2024 20:03:46.0299 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: b5248c68-de27-497e-f925-08dcceaf03f9 X-MS-Exchange-CrossTenant-Id: d6c573f1-34ce-4e5a-8411-94cc752db3e5 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=d6c573f1-34ce-4e5a-8411-94cc752db3e5;Ip=[52.4.92.69];Helo=[obx-outbound.inkyphishfence.com] X-MS-Exchange-CrossTenant-AuthSource: CH1PEPF0000AD81.namprd04.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH0PR08MB7338 Message-ID-Hash: Y5VUTPZYOGS3RTWIHLLBJNGIGX4O2RGY X-Message-ID-Hash: Y5VUTPZYOGS3RTWIHLLBJNGIGX4O2RGY X-MailFrom: shares@ndzh.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BIdr=5D_Brief_Shepherd_Reports_on_10_BGP-LS_Individual_drafts_pr?= =?utf-8?q?oposed_to_IDR_?= List-Id: Inter-Domain Routing Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --_000_CO1PR08MB66111C34F7526B38CF604684B39E2CO1PR08MB6611namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable IDR WG: Due to feedback from the IDR WG regarding IETF meeting time, the IDR chairs have started to hold an interim for BGP-LS and SR drafts before each IETF meeting. September 9 at 10:00-12:00 EDT is the BGP-LS and SR Interim before IETF-121. If you want to request WG adoption of your draft during September, October, or November, you must request to present your draft at this Interim meeting. Just a reminder, before an adoption call you need to have an IDR WG shepherd (usually an IDR co-chair) review your draft. Below is information on Allocation of SR Sub-TLVs and a brief Review of 10 individual drafts related to BGP-LS proposed for IDR. Cheerily, Sue Hares =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Allocation Information Segment Routing Sub-TLVs are still under early Allocation. This meeting will propose an allocation method for Segment routing Sub-TLVs. For the BGP-LS individual drafts, most BGP-LS parameter assignments are already under expert review. Therefore, allocation is not covered at this meeting. Reviews of 10 BGP-LS drafts 1. draft-chen-idr-bgp-ls-algo-related-adjacency-sid-04 Please do the following things prior to requesting pre-adoption shepherd's review of your draft: 1. Please update this draft to the latest version of the document. Please note that draft-peng-idr-segment-routing-te-policy-attr has been adopted as draft-ietf-idr-sr-te-policy-attr. 1. Please verify that the lsr WG reference are correct, and the these documents have been adopted by lsr. 1. Please carefully define all parameters to specific lengths. 2. If You have a reserved flag, please indicate set to zero and ignored = upon reception. 3. Please check your efforts align with [RFC9552], Draft-ietf-idr-bgp-ls-sr-policy. 1. draft-chen-idr-bgp-ls-security-capability-03 Please do the following things prior to requesting pre-adoption shepherd's review of your draft: 1. Please reduce your abstract to 2 paragraphs. 2. Please reduce your introduction to new points about BGP-LS not found in [RFC9552] 1. Section 2.2 - please explain what adding the Security capability attribute does for these features. BGP-LS is reading the security attribute. 1. Once you explain the mechanisms, then you must explain why it is needed for each place you want to add it. Please note, this must be proven from a security perspective. 1. draft-chen-idr-bgp-ls-sr-policy-cp-validity-01 Please do the following things prior to requesting pre-adoption shepherd's review of your draft: 1. Please update your drafts to the latest revision. [draft-ietf-idr-te-lsp-distribution] is replaced by [draft-ietf-idr-bgp-ls-te-path] and [draft-ietf-idr-bgp-ls-sr-policy] Please update [RFC7752] to [RFC9552] 1. Please indicate why the CP Validity Sub-TLV adds value to the BGP-LS stream by giving the count of segments in a segment list. Please adjust your text to indicate BGP-LS is read-only. 1. Please augment your procedures to indicate what happens If the information is not available. 1. Please add a security section. 1. draft-chen-idr-bgp-ls-transport-slide-06 This draft overlaps with the adopted IDR draft: draft-ietf-idr-bgp-ls-sr-policy-nrp-00. What is different with this draft? 1. draft-dong-idr-bgp-ls-scalable-nrp-01 This extension describes hierarchy in the NRP. This is a valuable addition to the NRP Mechanisms. Should this material be added to the draft-ietf-idr-bgp-ls-sr-policy-nrp? 1. draft-li-idr-bgpls-sr-policy-composite-path-06 This draft deals with the composite candidate path. Please do the following things prior to requesting pre-adoption shepherd's review of your draft: 1. update references to the appropriate latest drafts or RFCs, 2. Indicate how the Constituents SR Policy TLV is stored and used in ope= rational BGP. 3. Add substantial text about the security considerations of a composite= SR Policy. Please note that composite SR Policy have a different attack vector than the explicit segment lists. 1. draft-lin-idr-bgp-ls-te-policy-pm Please do the following things prior to requesting pre-adoption shepherd's review of your draft: 1. Upgrade your references to BGP-LS to [RFC9552] 2. Provide an introduction and 3. Provide a Security section that deals with the BGP-LS distributing the critical information about a network's performance. 1. Draft-liu-idr-bgpls-sr-p2mp-policy-distribution Please plan to talk to the authors of draft-ietf-idr-sr-p2mp-policy. I noticed that the authors for this draft are Yisong Liu, Changwang Lin, Hooman Bidgoli, and Sandy Zhang, I noticed that the authors for draft-ietf-idr-sr-p2mp-policy are Hooman Bidgoli, Daniel Voyer, Andrew Stone, Rishabh Parekh, Serge Krier, an= d Swadesh Agrawal. This draft should align with the mechanism and Information in draft-ietf-idr-sr-p2mp-policy. 1. Draft-liu-idr-bgp-ls-srp-flexible-path-selection-00 I notice that the draft-liu-spring-sr-policy-flexible-path-selection Adds parameters for the dynamic path switching. Is this dynamic path switching between existing explicit Candidate paths or Composite Candidate paths? Or are these parameters of dynamic Candidate Pa= ths? This concept needs to be further defined in Spring WG. After getting the Spring work completed, this draft should have the following changes: 1. Give [RFC9256] reference for type of Candidate paths 2. Add [RFC9552] reference 3. Explain carefully what type of Candidate Paths (explicit, dynamic, or= composite) This applies to 1. Explain the mechanism careful, 2. Give the SubTLVs 1. Draft-tong-idr-bgp-ls-savenet-00 The IDR chairs are discussing SAVNET with SAVNET authors. The authors should contact the IDR Co-chairs to discuss Why a Subnet identifier is being queried with BGP-LS. We are examining all BGP related SAVNET drafts prior to IETF-121/ --_000_CO1PR08MB66111C34F7526B38CF604684B39E2CO1PR08MB6611namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

= IDR WG:

=  

= Due to feedback from the IDR WG regarding IETF meeting time,

= the IDR chairs have started to hold an interim for

= BGP-LS and SR drafts before each IETF meeting.

=  

= September 9 at 10:00-12:00 EDT is the BGP-LS and SR

= Interim before IETF-121.  If you want to request WG adoption

= of your draft during September, October, or November,

= you must request to present your draft at this Interim meeting.  =

=  

= Just a reminder, before an adoption call you need to have

= an IDR WG shepherd (usually an IDR co-chair) review your draft.

=  

= Below is information on Allocation of SR Sub-TLVs and a brief

= Review of 10 individual drafts related to BGP-LS proposed for IDR.

=  

= Cheerily, Sue Hares

=  

= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=  

=  

Allocation Information

= Segment Routing Sub-TLVs are still under early Allocation.

= This meeting will propose an allocation method for

= Segment routing Sub-TLVs. 

=  

= For the BGP-LS individual drafts, most BGP-LS parameter

= assignments are already under expert review. Therefore,

= allocation is not covered at this meeting.

=  

Reviews of 10 BGP-LS drafts

=  

  1. draft-chen-idr-bgp-ls-a= lgo-related-adjacency-sid-04

=  

= Please do the following things prior to requesting

= pre-adoption shepherd’s review of your draft:

=  

  1. Please update = this draft to the latest version of the document.

=    Please note that draft-peng-idr-segment-routing-te-policy= -attr

=    has been adopted as draft-ietf-idr-sr-te-policy-attr.

=  

  1. Please verify = that the lsr WG reference are correct, and the

these documents have been adopted by lsr= .

=  

  1. Please careful= ly define all parameters to specific lengths.
  2. If You have a reserve= d flag, please indicate set to zero and ignored upon reception.  =
  3. Please check your efforts align with [RFC9552],
    4. <= /ol>

    Draft-ietf-idr-bgp-ls-sr-policy.

    =  

    1. draft-chen-idr-bgp-ls-s= ecurity-capability-03

    =  

    = Please do the following things prior to requesting

    = pre-adoption shepherd’s review of your draft:

    =  

    1. Please reduce you= r abstract to 2 paragraphs. 
    2. Please reduce your introduction to new points about

    BGP-LS not found in [RFC9552]

    1. Section 2.2 ̵= 1; please explain what adding the

    Security capability attribute does for these features.   <= o:p>

    BGP-LS is reading the security attribute.

    1. Once you explain = the mechanisms, then you must explain why it

    is needed for each place you want to add it.

    =  

    = Please note, this must be proven from a security perspective.

    =  

    1. draft-chen-idr-bgp-ls-s= r-policy-cp-validity-01

    =  

    = Please do the following things prior to requesting

    = pre-adoption shepherd’s review of your draft:

    =  

    1. Please update you= r drafts to the latest revision.

    [draft-ietf-idr-te-lsp-distribution] is replaced by

    [draft-ietf-idr-bgp-ls-te-path] and

    [draft-ietf-idr-bgp-ls-sr-policy]

     

    =      Please update [RFC7752] to [RFC9552]  

    =     

    1. Please indicate w= hy the CP Validity Sub-TLV

    adds value to the BGP-LS stream by giving the

    count of segments in a segment list.

    Please adjust your text to indicate BGP-LS is read-only.

     

    1. Please augment yo= ur procedures to indicate what happens

    If the information is not available.

     

    1. Please add a secu= rity section.

    =  

    1. draft-chen-idr-bgp-ls-t= ransport-slide-06

    =  

    This draft overlaps with the adopted IDR draft:

    draft-ietf-idr-bgp-ls-sr-policy-nrp-00.

     

    What is different with this draft?

     

    1. draft-dong-idr-bgp-ls-s= calable-nrp-01

    =  

    This extension describes hierarchy in the

    NRP.  This is a valuable addition to the N= RP

    Mechanisms.

     

    Should this material be added to the draft-ietf= -idr-bgp-ls-sr-policy-nrp?  

    =  

    1. draft-li-idr-bgpls-sr-p= olicy-composite-path-06

     

    This draft deals with the composite candidate p= ath.

     

    = Please do the following things prior to requesting

    = pre-adoption shepherd’s review of your draft:

     

    1. update references= to the appropriate latest drafts or RFCs,
    2. Indicate how the Constituents SR Policy TLV is stored and used in ope= rational BGP.
    3. Add substantial text about the security considerations o= f a composite SR Policy.

     

    Please note that composite SR Policy have a dif= ferent attack vector than

    the explicit segment lists.

     

     

    1. draft-lin-idr-bgp-ls-te= -policy-pm

    =  

    = Please do the following things prior to requesting

    = pre-adoption shepherd’s review of your draft:

    =  

    1. Upgrade your ref= erences to BGP-LS to [RFC9552]
    2. Provide an introduction and
    3. Provide a Security section that deals with the

    BGP-LS distributing the critical information

    about a network’s performance.

    =  

    1. Draft-liu-idr-bgpls-sr-= p2mp-policy-distribution

    =  

    Please plan to talk to the authors of

    draft-ietf-idr-sr-p2mp-policy.

     

    I noticed that the authors for this draft are

    Yisong Liu, Changwang Lin, Hooman Bidgoli, and = Sandy Zhang,

     

    I noticed that the authors for

    draft-ietf-idr-sr-p2mp-policy are

    Hooman Bidgoli, Daniel Voyer, Andrew Stone, Ris= habh Parekh, Serge Krier, and Swadesh Agrawal.

     

    This draft should align with the mechanism and

    Information in draft-ietf-idr-sr-p2mp-policy.

    =  

    1. Draft-liu-idr-bgp-ls-sr= p-flexible-path-selection-00

    =  

    I notice that the draft-liu-spring-sr-policy-fl= exible-path-selection

    Adds parameters for the dynamic path switching.

     

    Is this dynamic path switching between existing= explicit Candidate paths or

    Composite Candidate paths?  Or are these p= arameters of dynamic Candidate Paths?   

     

    This concept needs to be further defined in Spr= ing WG. After getting the

    Spring work completed, this draft should have t= he following changes:

     

    1. Give [RFC9256] r= eference for type of Candidate paths
    2. Add [RFC9552] reference
    3. Ex= plain carefully what type of Candidate Paths (explicit, dynamic, or composi= te)

    This applies to

    1. Explain the mech= anism careful,
    2. Give the SubTLVs

    =  

    1. Draft-tong-idr-bgp-ls-s= avenet-00

    =  

    The IDR chairs are discussing SAVNET with SAVNE= T authors.

    The authors should contact the IDR Co-chairs to= discuss

    Why a Subnet identifier is being queried with B= GP-LS.

     

    We are examining all BGP related SAVNET drafts = prior to IETF-121/

    =

--_000_CO1PR08MB66111C34F7526B38CF604684B39E2CO1PR08MB6611namp_--