[Idr] Please review draft-li-idr-sr-policy-path-segment-00, comments are wellcome!
"Chengli (Cheng Li)" <chengli13@huawei.com> Thu, 27 June 2019 07:55 UTC
Return-Path: <chengli13@huawei.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 DF697120242 for <idr@ietfa.amsl.com>; Thu, 27 Jun 2019 00:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 4lvvHjTgb3eI for <idr@ietfa.amsl.com>; Thu, 27 Jun 2019 00:55:01 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A2FA12022C for <idr@ietf.org>; Thu, 27 Jun 2019 00:55:00 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id DF9E2B31292A9950A859 for <idr@ietf.org>; Thu, 27 Jun 2019 08:54:58 +0100 (IST)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 27 Jun 2019 08:54:58 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.87]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0439.000; Thu, 27 Jun 2019 15:54:19 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: "Chengli (Cheng Li)" <chengli13@huawei.com>, Shraddha Hegde <shraddha@juniper.net>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Please review draft-li-idr-sr-policy-path-segment-00, comments are wellcome!
Thread-Index: AdUsvUJtdpNL/8jURV+bUXMKaH26bQ==
Date: Thu, 27 Jun 2019 07:54:18 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB0262B488@dggeml529-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.185.75]
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB0262B488dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/l7Y8Y1LR14ZfgsEYaOhu4ejsU9Y>
Subject: [Idr] Please review draft-li-idr-sr-policy-path-segment-00, comments are wellcome!
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: Thu, 27 Jun 2019 07:55:04 -0000
Hi WG, We have updated our draft, welcome to review! Comments are always welcome! Thanks to Shraddha's comments again! Main modifications are: * add IANA text * address comments from Shraddha * update refs * change name since it is longer than limitation. Regards, Cheng -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: Thursday, June 27, 2019 3:29 PM To: Lizhenbin <lizhenbin@huawei.com>; Huanan Chen <chenhn8.gd@chinatelecom.cn>; Mach Chen <mach.chen@huawei.com>; China Telecom <chenhn8.gd@chinatelecom.cn>; Dongjie (Jimmy) <jie.dong@huawei.com>; Mach Chen <mach.chen@huawei.com>; Chengli (Cheng Li) <chengli13@huawei.com> Subject: New Version Notification for draft-li-idr-sr-policy-path-segment-00.txt A new version of I-D, draft-li-idr-sr-policy-path-segment-00.txt has been successfully submitted by Cheng Li and posted to the IETF repository. Name: draft-li-idr-sr-policy-path-segment Revision: 00 Title: SR Policy Extensions for Path Segment and Bidirectional Path Document date: 2019-06-27 Group: Individual Submission Pages: 11 URL: https://www.ietf.org/internet-drafts/draft-li-idr-sr-policy-path-segment-00.txt Status: https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/ Htmlized: https://tools.ietf.org/html/draft-li-idr-sr-policy-path-segment-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-li-idr-sr-policy-path-segment Abstract: A Segment Routing (SR) policy is a set of candidate SR paths consisting of one or more segment lists with necessary path attributes. For each SR path, it may also have its own path attributes, and Path Segment is one of them. A Path Segment is defined to identify an SR path, which can be used for performance measurement, path correlation, and end-2-end path protection. Path Segment can be also used to correlate two unidirctional SR paths into a bidirectional SR path which is required in some scenarios, for example, mobile backhaul transport network. This document defines extensions to BGP to distribute SR policies carrying Path Segment and bidirectional path information. 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 From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Chengli (Cheng Li) Sent: Tuesday, June 11, 2019 11:50 AM To: Shraddha Hegde <shraddha@juniper.net> Cc: idr@ietf.org; draft-li-idr-sr-policy-path-segment-distribution@ietf.org Subject: Re: [Idr] draft-li-idr-sr-policy-path-segment-distribution CC to IDR WG ML Cheng From: Chengli (Cheng Li) Sent: Tuesday, June 11, 2019 11:45 AM To: 'Shraddha Hegde' <shraddha@juniper.net<mailto:shraddha@juniper.net>>; Shraddha Hegde <shraddha=40juniper.net@dmarc.ietf.org<mailto:shraddha=40juniper.net@dmarc.ietf.org>>; draft-li-idr-sr-policy-path-segment-distribution@ietf.org<mailto:draft-li-idr-sr-policy-path-segment-distribution@ietf.org> Subject: RE: draft-li-idr-sr-policy-path-segment-distribution Hi Shraddha, Sorry for my delay. We plan to update the draft by IETF 105. Please see my reply inline. Thanks, Cheng From: Shraddha Hegde [mailto:shraddha@juniper.net] Sent: Monday, June 10, 2019 2:19 PM To: Shraddha Hegde <shraddha=40juniper.net@dmarc.ietf.org<mailto:shraddha=40juniper.net@dmarc.ietf.org>>; draft-li-idr-sr-policy-path-segment-distribution@ietf.org<mailto:draft-li-idr-sr-policy-path-segment-distribution@ietf.org> Subject: RE: draft-li-idr-sr-policy-path-segment-distribution Authors, Any update on these comments? Rgds Shraddha From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Shraddha Hegde Sent: Tuesday, May 7, 2019 9:51 AM To: draft-li-idr-sr-policy-path-segment-distribution@ietf.org<mailto:draft-li-idr-sr-policy-path-segment-distribution@ietf.org> Cc: idr@ietf.org<mailto:idr@ietf.org> Subject: [Idr] draft-li-idr-sr-policy-path-segment-distribution Authors, I have a few comments on the document. 1. Section 3 :SR Policy for Path Identifier Change to "Path Identifier for SR Policy" [Cheng] Looks better. Path Identifier in SR policy? Will update in next revision. 2. sec 3 SR Policy for Path Identifier The path segment can appear at both segment-list level and SR policy level, and it could also appear only at one level depending upon usecase. Path segment at segment list level and at SR-Policy level may be same or may be different based on usecase and the ID allocation scope. [Cheng] Agree. 3. I think there should be a separate section on allocation of Path Identifier. The scope of allocation and resultant scaling considerations. [Cheng] Let's see how to add it on next revision. 4. SR Path Segment Sub-TLV The length of the SR Path Segment is defined to be of variable length. This should be well defined for SR-MPLS to be 20 bit and upto 128 bit for SRv6. [Cheng] Agree, but I think 32bit for SR-MPLS will be better. Rgds Shraddha
- [Idr] Please review draft-li-idr-sr-policy-path-s… Chengli (Cheng Li)