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 AD6F7C14F700 for ; Thu, 5 Sep 2024 22:05:59 -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 el30XrpDoTMy for ; Thu, 5 Sep 2024 22:05:58 -0700 (PDT) Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2109.outbound.protection.outlook.com [40.107.244.109]) (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 A9A42C14F6FD for ; Thu, 5 Sep 2024 22:05:58 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=pass; b=nRX6tjYHmpg1CZP3H883AIQmiyRnreEM8P5gSrGOSrmzOk7dCurnSFyA+T8OJaKZfAtRXPOx42yCFTEnflSLV6hLBUywmdvLTrLo1jLm+mmESwEX7azsaXaYrPAAda1muWo3+Mi2yOQWGMA7RUxaGfXkyJDHfuw5699qMBjhGgjuC8lqAK4kS4eHObv94Qkf4RT/HtIurk6bHh3zH1NtvfbOvm2GwkMNyjRABqwdqH6nywi13kP4Sp0QAd0KetGIyTItHVHj6/JlVqFOurlAjcYLuXSWEehqNFO7GhbcRTIWn9qyAFToAN+nWh/9S+N1OCLzULTJVhEFiN8lOdUxEw== 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=4WsybPgisnXWrpJbjWHvN/kvyhIIG3bft9rXuw0Se3U=; b=TUU/wO3nvL2/UxG5aNa4WzKqo+y2T5TF0mEoTlo9evejZvFHppLKBm/13JK125pvGsXc5b9FcGC9xYDxcFFpruBTrzRBACNgP866O80RQESbt9U1bHBzCfbKNe0qs6zhmEQ5ASh/oHktCHLaHe0tR1oYgMw+dubyDEgJk0ZwVP8qPVKwZJF7uv3Fazx/HyOj6QMW+J0MoN14TK+wr3bqCVscUqAY+N4FHUffDLteXjyFboryk4kzUo0Ix/9xsvKXpK7jA4G9Mlks9gKl/85a+aquyxSdSP2BblQz2kyfLQix5GDvcWz4E0kceXuew7HLAbM6hWf+eQT+7bTGSDrk9A== ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 104.47.66.43) smtp.rcpttodomain=chinamobile.com 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 DS7PR05CA0026.namprd05.prod.outlook.com (2603:10b6:5:3b9::31) by CH3PR08MB9878.namprd08.prod.outlook.com (2603:10b6:610:21d::6) 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 05:05:54 +0000 Received: from DS1PEPF00017099.namprd05.prod.outlook.com (2603:10b6:5:3b9:cafe::dc) by DS7PR05CA0026.outlook.office365.com (2603:10b6:5:3b9::31) 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 05:05:54 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 104.47.66.43) 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.66.43 as permitted sender) receiver=protection.outlook.com; client-ip=104.47.66.43; helo=NAM12-MW2-obe.outbound.protection.outlook.com; pr=C Received: from obx-outbound.inkyphishfence.com (50.17.62.222) by DS1PEPF00017099.mail.protection.outlook.com (10.167.18.103) 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 05:05:53 +0000 Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12lp2043.outbound.protection.outlook.com [104.47.66.43]) by obx-inbound.inkyphishfence.com (Postfix) with ESMTPS id 9A85F102C1F; Fri, 6 Sep 2024 05:05:52 +0000 (UTC) ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=WHGVSl82UjUF7Fk59L9SK0jAnAHEdlWp4esDLeefUv9GWhChSA/cUk2+XiZITMQ3H3UG0tWL8PDv7WAQj9HVzN57cZKrlW+nUp4UwOwob/m6ZXSauYafdqTc0BgwKOITZ8w4zaWX6SwNgjcy74562yS+p/NsoHSAn5TUzDpv45+KWKrzMWaWLDSSwXUd9Q1gs6BeT5wy0XGrXyMXufOdRCOyog7G1iSxVKH1TgGQNMbthg2qRuaKYYm55OFLJq3nbC1mutJW6l+rSN3HdFNdDV52awjKQjVtr4t8otejLjDCgCPV2L85ghXq3zArVu8Mlh/RUXfQUyazPh59pkF/EQ== 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=4WsybPgisnXWrpJbjWHvN/kvyhIIG3bft9rXuw0Se3U=; b=D/lCSKk1GutkdUaZgdhMxArMNoFSd3w7uy3IRefx56xmta7T0vJ8ZTLMzmmoopRS/aNseT98xTF/yUnbkHyjS8Oop8yUfEa5/35CZDdHx6njljjDGj2D7sVyQt31+LU/Dr2GfWe3DhaJfukpO9EToOjpXTZIxi3tkR5A+Z68gzhHkGaOJN+IJE0FXxFggDc7yrs/9Sr/P1wZ1cZw4CQjUTb/B3LgTUYKcKvEiTMcGC4g76Cgzl8yLuBxuOC0DrwNUHOTXwrbf6G5EUACaL7dLHDSfQciHmULH5XTLmSAH/P/0iTQ8y60tPuyRS/ZCEDa/Xny4KCpaQG6ELOlQO2RIg== 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 CH0PR08MB8707.namprd08.prod.outlook.com (2603:10b6:610:182::15) 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 05:05:50 +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 05:05:50 +0000 From: Susan Hares To: "idr@ietf.org" Thread-Topic: Shepherd draft-zzd-idr-sr-policy-scheduling-04 - I actually reviewed-05 Thread-Index: AQHbABpxN4owSfcjX0WxfqD3Hxyrug== Date: Fri, 6 Sep 2024 05:05:50 +0000 Message-ID: References: In-Reply-To: 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_|CH0PR08MB8707:EE_|DS1PEPF00017099:EE_|CH3PR08MB9878:EE_ X-MS-Office365-Filtering-Correlation-Id: 1a107e49-53b9-4cb0-f26b-08dcce319592 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam-Untrusted: BCL:0;ARA:13230040|366016|1800799024|376014|38070700018; X-Microsoft-Antispam-Message-Info-Original: =?us-ascii?Q?JMqbK5CEQ6Q0MLUgOUiU/NTfHHFCgCBHlN8vmcx4nsh/RKDLYxsCsaegU54N?= =?us-ascii?Q?s80hTK2SZ/ThwLbkaf30QL30htTGiylXIOVzwnHm4vMW/QkaHG2RE/MAxwXD?= =?us-ascii?Q?QUt9RQ6V6yciC9b4EDczs31WxHC7FNUwojg8t6Aky+TxVN79yvlsi2ISltOl?= =?us-ascii?Q?8FWghSDvflrdxY276Ow/23T8Ruu+BEVKCny1n7QazHPLMjpFD90Kx5oH+7m/?= =?us-ascii?Q?COGCMgucGkIwogwgDWoFBF6/MGNuHdLi87Glyd7R9dIHWmB3oM6BJ4wiqGMD?= =?us-ascii?Q?iYY54iZp6w/iB0Lv9Wjk4UxxKc3ZgLEBLl6Bg+CSyfgYBMM+ffT4sJwK2z6i?= =?us-ascii?Q?6JJN1lbyfkoHlWfFk/Tqjm23m8s05YCljx3OmuOSwU149q8vOLqYj19KDOAN?= =?us-ascii?Q?wdfg2vq1FDQ378AmLE3Fi81N+mJOoNe1JNMcgW+R3c8MZSrdRJDQoSe0nu0L?= =?us-ascii?Q?AdtBIXVdXAwIco7dSkh/6bJWQvQaHdKsc6D9VXtMllKP1tygycCMs5jPA06P?= =?us-ascii?Q?jGAMNavg1fjNnD2udbYSTJEXcU6c4As6H9btxG/63YfVu+uSD/G40nkVlAIa?= =?us-ascii?Q?RGMnGZBP+vWRdlvL9Phuiphq13GyuwDiWTc3noiO8G1URJo/wiyUmVS8lEi7?= =?us-ascii?Q?LVIutDvsLVUSMs8CxsWpnSYQoNB5nq7AfHRblGTfa27fShnrCUKdhRaa3R2E?= =?us-ascii?Q?p3/DDx/78Ssxa+jLjlbLI7QCXSQhauen3/8x2gBPsrsniYlkiZbyPzpRK4dL?= =?us-ascii?Q?up0E1y63kq+aV482W2hnV77uffTYN/rWcW2OiqB1MYO/A2lP9Q+fhi5uqrkH?= =?us-ascii?Q?rku5ynMAOugclrB/87ylQeUxrMVjMsgusrRdJZv11Onte5sr82YB6W22E74v?= =?us-ascii?Q?ZVyiaCudLKrrzu80XH/mPxyO6uBqdokvqBxJ/j8MivwGSmYFQ7N+J8V/96yO?= =?us-ascii?Q?+/0OxNnbLRCYHjvY9/Lzme9OSbAItjcWninXXf/LUKJAT7fWgVKxyRDf6hfT?= =?us-ascii?Q?8Sni+ifDXEA99Zz8+vRURvF6kHR7OnAYTCs95UWonG4vxqvOxYWWyPvcRYkm?= =?us-ascii?Q?Ld/2nqauqTtB1EjUzY2uvDclVdkA16kJ9QP/0Vjj/PV5zIueMP88ZgEpLfO7?= =?us-ascii?Q?yFgnmHscQl4uZ1KJkLEEtxgEVz/3YEcwwtQNNPIZRSJFbQKaLdRv5ATXg83+?= =?us-ascii?Q?GVDzKDXyO+jAx7biU+Bi8WE0zDwnLjD0NJvBpP4J5Sv94iVNoyDJgW6eaYTB?= =?us-ascii?Q?LwMEv8tSU6oPH7Y8EbbPfI2qbWG42/nu3mTp3W7GQIpdyeUBlZrF9WB6PMxB?= =?us-ascii?Q?oC3RwlBtCsyLk1wqbAiBtFwd8GvdyznmOy9CTh7Y15F1nY2gTyouwfemKyMy?= =?us-ascii?Q?o3nznYbMM/j0ci2I7erukTjMLVCQFjemhDjbae3KIXASAT/K0g=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)(1800799024)(376014)(38070700018);DIR:OUT;SFP:1102; Content-Type: multipart/alternative; boundary="_000_CO1PR08MB66118ADC323FC9262ACF2216B39E2CO1PR08MB6611namp_" MIME-Version: 1.0 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH0PR08MB8707 X-Inky-Outbound-Processed: True X-EOPAttributedMessage: 0 X-MS-Exchange-SkipListedInternetSender: ip=[104.47.66.43];domain=NAM12-MW2-obe.outbound.protection.outlook.com X-MS-Exchange-ExternalOriginalInternetSender: ip=[104.47.66.43];domain=NAM12-MW2-obe.outbound.protection.outlook.com X-MS-Exchange-Transport-CrossTenantHeadersStripped: DS1PEPF00017099.namprd05.prod.outlook.com X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id-Prvs: 541c58f3-a8a0-44a2-e9ad-08dcce31938d X-IPW-GroupMember: False X-Microsoft-Antispam: BCL:0;ARA:13230040|1800799024|35042699022|376014|82310400026|36860700013; X-Microsoft-Antispam-Message-Info: R0uR1m/Rr86GteYuHNoiQjHzmpSXT3YIB6ZjXGMCbUz0SnLTdej2Luqh1xXzZNBFCCrbfq9Npu3+1ZDdiJ18HQKZ3GhxOkL1oHwUH264E75xP3LPbqAoeJ+B3o30rAKMS6ZieUQ1pbEOJQooLSRhQXgfYipALKkfX9MCxtK9kZetTbY/enQ3JrU+1HRefkyxJsr3D5t1JFleiaD7CaShNnR69B+5dRMWcogwfd2xwrpJ5aJtVUAwENe+drWixcNlYXgp+hPu1uoyz1bE8ljthyeV2ZGFB3o7fkZb7ay9b1gHy3we3L3tAKmcDqfhFmAUTde8ApBGRzUB42jB8HRnft9shx2o9HW4zZ8J5nULR59h/8+qYe8RudpzLBx+/hH5ui1SXdmUmNHxvO66D5z7Uo5iPJtyvi4KiMv+1wqLwT2kl1XENRLjEof+Xwat10eegry2iYrpVHWem6URQF4o2GzkhzH0kd0Sv1Zl7dDGntxJvJKK2rIQor+Nno7n6oPfdbmsTKEgbf+BXla5UhbOLqm1iHEtDzkHGg+YG2kG8aN+Tzhb1m2+CizqbYaKnePpjoqnqxJclNIPvx0CTafOhj9kCNM8EjTGrAoLQ5z0H8HU8yF1pC63GDXpjrZxkJcF4C0vRkUrwUnJHpzoqU4UFAp4EpsSHrdBdRwHjtq5AuZHCFxBbER9FERjJCQxm55vb11dZNeZA8QkXCPLGfC6lHGuw/TELK/aCEg+D3jSA/zDRaU0Fbp8cwjRN0b72nHvTBajGWk6XcfcItK+CCGI3jfiUf1F466OhoOgJc0vbbTEGD5oT7hql39DjE34CYu7ambOAbGCLp9l/ejcgpFz9A== X-Forefront-Antispam-Report: CIP:50.17.62.222;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:NAM12-MW2-obe.outbound.protection.outlook.com;PTR:mail-mw2nam12lp2043.outbound.protection.outlook.com;CAT:NONE;SFS:(13230040)(1800799024)(35042699022)(376014)(82310400026)(36860700013);DIR:OUT;SFP:1102; X-OriginatorOrg: ndzh.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Sep 2024 05:05:53.6828 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 1a107e49-53b9-4cb0-f26b-08dcce319592 X-MS-Exchange-CrossTenant-Id: d6c573f1-34ce-4e5a-8411-94cc752db3e5 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=d6c573f1-34ce-4e5a-8411-94cc752db3e5;Ip=[50.17.62.222];Helo=[obx-outbound.inkyphishfence.com] X-MS-Exchange-CrossTenant-AuthSource: DS1PEPF00017099.namprd05.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH3PR08MB9878 Message-ID-Hash: ZU6T42QW6HHMDXD54XFOKWVNTXJ7RJQS X-Message-ID-Hash: ZU6T42QW6HHMDXD54XFOKWVNTXJ7RJQS 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 CC: "wangminxue@chinamobile.com" , "Nkosinathi.Nzima@mtn.com" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BIdr=5D_Re=3A_Shepherd_draft-zzd-idr-sr-policy-scheduling-04_-_I?= =?utf-8?q?_actually_reviewed-05?= List-Id: Inter-Domain Routing Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --_000_CO1PR08MB66118ADC323FC9262ACF2216B39E2CO1PR08MB6611namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please note that I actually reviewed draft-zzd-idr-sr-policy-scheduling-05.= txt Sue . From: Susan Hares Sent: Friday, September 6, 2024 1:04 AM To: idr@ietf.org Cc: Dongjie (Jimmy) ; Tianran Zhou ; wangminxue@chinamobile.com; Nkosinathi.Nzima@mtn.com Subject: Shepherd draft-zzd-idr-sr-policy-scheduling-04 Li, Tianran, Jie, Minxue, and Nkosinathi: Thank you for the interesting work in draft-zz-idr-sr-policy-scheduling-05 Below I've provided you a short shepherd's review. Please let me know if you have any questions regarding this draft? Would you mind answering some questions about this draft: 1. Are you planning any technical additions to this draft prior an IDR W= G adoption? 1. Will you request WG Adoption in the next 3 months? If you make the changes listed below, this draft appears to be ready for a WG adoption call. If you are close to a WG adoption, it might be nice to review this draft at the September 9, 2024 IDR interim. 1. Does this addition apply to all segment types? 1. Are you working on an implementation? Cheerily, Sue =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Shepherd Review for: draft-zzd-idr-sr-policy-scheduling-04 status: individual draft draft-status: Proposed Standard, version: revision needed (-05) implementations: unknown Authors: 5 authors Summary: Almost ready for WG adoption call Detailed Shepherd's review, Issue-1. Abstract, specify SR Policy Candidate Path distribution Old text:/ This document proposes extensions to BGP SR Policy to indicate the scheduling time of each candidate path(segment list) and its associated attributes./ Old text:/ This document proposes extensions to BGP mechanism to pass explicit SR Policy Candidate Paths in order to indicate the scheduling time of each candidate path(segment list) and its associated attributes./ Issue-2. Section 1, Update to [draft-ietf-idr-sr-policy-safi] Old text:/ [I-D.ietf-idr-segment-routing-te-policy] specifies how BGP may be used to distribute SR Policy candidate paths. It introduces a BGP SAFI with new NLRI to advertise a candidate path of a Segment Routing (SR) Policy./ new text:/ [I-D.ietf-idr-sr-policy-safi] specifies how BGP may be used to distribute explicit SR Policy candidate paths. It introduces a = BGP SAFI with new NLRI (SR Policy) and a new tunnel type for the BGP Tunnel Encapsulation Attribute (SR Policy) to advertise a candidate path of a Segment Routing (SR) Policy./ Old text:/ In order to solve these problems, this document proposes extensions to BGP SR Policy to indicate the scheduling time of each candidate path(segment list) and its associated attributes. / new text:/ In order to solve these problems, this document proposes extensions to BGP SR Policy as defined in [draft-ietf-idr-sr-policy-safi] to indicate the scheduling time of each explicit candidate path (segment list). / Issue-3: Section 3, update to latest drafts replace [draft-ietf-idr-segment-routing-te-policy] to [draft-ietf-idr-sr-policy-safi]. old text:/ The NLRI defined in [I-D.ietf-idr-segment-routing-te-policy] contains the SR Policy candidate path. The content of the SR Policy Candidate Path is encoded in the Tunnel Encapsulation Attribute defined in [RFC9012] using a new Tunnel-Type called SR Policy Type with codepoint 15. / new text:/ The NLRI defined in [I-D.ietf-idr-sr-policy-safi] contains the SR Policy candidate for an explicit policy. The content of the SR P= olicy Candidate Path is encoded in the Tunnel Encapsulation Attribute defined in [RFC9012] using a new Tunnel-Type called SR Policy (code point 15)./ Issue-4: Section 3, English text old text:/ The new SR Policy encoding structure is expressed as below:/ new text:/ The new SR Policy TLV structure is listed below:/ Issue-5: Section 4.1 and 4.2 Please Give ranges on the definitions. Here are a few questions that your text should answer: 1) Is group number zero valid? Are there any invalid group numbers? 2) Is index of zero valid? 3) Provide clearer diagram on time block. [index, reserved] [enable time] [disable time] are 12 octets of repeating information. Issue-6: Add information to security section See [draft-ietf-idr-sr-policy-safi] security section. What you need to update here is the protection of the critical information for the Scheduled Time Information Sub-TLVs you have added. Issue-7: Please add a manageability section The movement of traffic between SR Candidate paths based on time may take different skills to debug problems in code or configuration. Please provide a short manageability section. --_000_CO1PR08MB66118ADC323FC9262ACF2216B39E2CO1PR08MB6611namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Please note that I actually reviewed draft-zzd-idr-s= r-policy-scheduling-05.txt

 

Sue .

 

 

From: Susan Hares
Sent: Friday, September 6, 2024 1:04 AM
To: idr@ietf.org
Cc: Dongjie (Jimmy) <jie.dong@huawei.com>; Tianran Zhou <zh= outianran@huawei.com>; wangminxue@chinamobile.com; Nkosinathi.Nzima@mtn.= com
Subject: Shepherd draft-zzd-idr-sr-policy-scheduling-04 <= /span>

 

= Li, Tianran, Jie, Minxue, and Nkosinathi:

=  

= Thank you for the interesting work in

= draft-zz-idr-sr-policy-scheduling-05

=  

= Below I’ve provided you a short shepherd’s review.

= Please let me know if you have any questions regarding this draft?

=  

= Would you mind answering some questions about this draft:=

=  

  1. Are you planning = any technical additions to this draft prior an IDR WG adoption?

 

  1. Will you request = WG Adoption in the next 3 months?

 

If you make the changes listed below, this draft

appears to be ready for a WG adoption call.

 

If you are close to a WG adoption, it might be nice

to review this draft at the September 9, 2024 IDR interim.

=  

  1. Does this additio= n apply to all segment types?

 

  1. Are you working o= n an implementation?

=  

=  

= Cheerily, Sue

=  

=  

=  

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

= Shepherd Review for:

= draft-zzd-idr-sr-policy-scheduling-04

=  

=  

= status: individual draft

= draft-status: Proposed Standard,

= version: revision needed (-05) 

= implementations: unknown

= Authors: 5 authors

= Summary: Almost ready for WG adoption call

=  

=  

= Detailed Shepherd’s review,

=  

= Issue-1. Abstract, specify SR Policy Candidate Path distribution 

=  

= Old text:/

=    This document proposes extensions to BGP SR Policy to ind= icate the

=    scheduling time of each candidate path(segment list) and its

=    associated attributes./

=  

= Old text:/

=  

=    This document proposes extensions to BGP mechanism to pass

=    explicit SR Policy Candidate Paths in order to indicate t= he

=    scheduling time of each candidate path(segment list) and its

=    associated attributes./

=   

= Issue-2. Section 1, Update to [draft-ietf-idr-sr-policy-safi]

=  

= Old text:/

=    [I-D.ietf-idr-segment-routing-te-policy] specifies how BGP may= be

=    used to distribute SR Policy candidate paths.  It introdu= ces a BGP

=    SAFI with new NLRI to advertise a candidate path of a Segment = Routing

=    (SR) Policy./

=   

= new text:/

=    [I-D.ietf-idr-sr-policy-safi] specifies how BGP may be

=    used to distribute explicit SR Policy candidate paths.  I= t introduces a BGP

=    SAFI with new NLRI (SR Policy) and a new tunnel type for the B= GP Tunnel

=    Encapsulation Attribute (SR Policy) to advertise a candid= ate path

=    of a Segment Routing (SR) Policy./

=   

= Old text:/

=    In order to solve these problems, this document proposes exten= sions

=    to BGP SR Policy to indicate the scheduling time of each candi= date

=    path(segment list) and its associated attributes. /

=    

= new text:/

=    In order to solve these problems, this document proposes exten= sions

=    to BGP SR Policy as defined in [draft-ietf-idr-sr-policy-safi]

=    to indicate the scheduling time of each explicit candidat= e

=    path (segment list). /

=    

= Issue-3: Section 3, update to latest drafts

=  

= replace [draft-ietf-idr-segment-routing-te-policy] to

= [draft-ietf-idr-sr-policy-safi].

=  

= old text:/

=    The NLRI defined in [I-D.ietf-idr-segment-routing-te-policy] c= ontains

=    the SR Policy candidate path.  The content of the SR Poli= cy Candidate

=    Path is encoded in the Tunnel Encapsulation Attribute defined = in

=    [RFC9012] using a new Tunnel-Type called SR Policy Type with

=    codepoint 15. /

=   

= new text:/

= The NLRI defined in [I-D.ietf-idr-sr-policy-safi] contains

=    the SR Policy candidate for an explicit policy.  The cont= ent of the SR Policy Candidate

=    Path is encoded in the Tunnel Encapsulation Attribute defined = in

=    [RFC9012] using a new Tunnel-Type called SR Policy (code point= 15)./

=    

=  

= Issue-4: Section 3, English text

=  

= old text:/ The new SR Policy

=    encoding structure is expressed as below:/

=  

= new text:/ The new SR Policy TLV structure

=    is listed below:/

=  

= Issue-5: Section 4.1 and 4.2

=  

= Please Give ranges on the definitions.

=  

= Here are a few questions that your text should answer:

=  

= 1) Is group number zero valid? Are there any invalid group numbers?

=  

= 2) Is index of zero valid?

=  

= 3) Provide clearer diagram on time block.

=  

= [index, reserved] [enable time] [disable time]

= are 12 octets of repeating information.

=  

= Issue-6: Add information to security section

=  

= See [draft-ietf-idr-sr-policy-safi] security section.

= What you need to update here is the protection of

= the critical information for the Scheduled Time Information

= Sub-TLVs you have added.

=  

= Issue-7: Please add a manageability section

=  

= The movement of traffic between SR Candidate

= paths based on time may take different skills

= to debug problems in code or configuration.

=  

= Please provide a short manageability section.

=  

=  

=  

=  

=  

=  

--_000_CO1PR08MB66118ADC323FC9262ACF2216B39E2CO1PR08MB6611namp_--