Re: [Idr] draft-li-idr-sr-policy-path-segment-distribution

"Chengli (Cheng Li)" <chengli13@huawei.com> Tue, 11 June 2019 03:50 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 D8CA71200FF; Mon, 10 Jun 2019 20:50:37 -0700 (PDT)
X-Quarantine-ID: <Vu0EDSNsraIG>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...130@SN6PR05MB3950.namprd05.prod.outlook.com>\n
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Vu0EDSNsraIG; Mon, 10 Jun 2019 20:50:35 -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 6DFBB1200FE; Mon, 10 Jun 2019 20:50:35 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id B5A594851E2CF8903EB9; Tue, 11 Jun 2019 04:50:33 +0100 (IST)
Received: from DGGEML423-HUB.china.huawei.com (10.1.199.40) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 11 Jun 2019 04:50:33 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.38]) by dggeml423-hub.china.huawei.com ([10.1.199.40]) with mapi id 14.03.0439.000; Tue, 11 Jun 2019 11:50:11 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: Shraddha Hegde <shraddha@juniper.net>
CC: "idr@ietf.org" <idr@ietf.org>, "draft-li-idr-sr-policy-path-segment-distribution@ietf.org" <draft-li-idr-sr-policy-path-segment-distribution@ietf.org>
Thread-Topic: draft-li-idr-sr-policy-path-segment-distribution
Thread-Index: AdUEi/lYsgagiyOKQv6W3D1f7ronogax+OGwACxRGyAAAOIrgA==
Date: Tue, 11 Jun 2019 03:50:11 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB0260C268@dggeml529-mbx.china.huawei.com>
References: <BYAPR05MB3943AB92D1AAED526DCC9AAED5310@BYAPR05MB3943.namprd05.prod.outlook.com> <SN6PR05MB395011E24179B5B947395B81D5130@SN6PR05MB3950.namprd05.prod.outlook.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_C7C2E1C43D652C4E9E49FE7517C236CB0260C268dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/cI-Y5BksFqjkHUBC0Sps5Txtulk>
Subject: Re: [Idr] draft-li-idr-sr-policy-path-segment-distribution
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, 11 Jun 2019 03:50:38 -0000

CC to IDR WG ML

Cheng


From: Chengli (Cheng Li)
Sent: Tuesday, June 11, 2019 11:45 AM
To: 'Shraddha Hegde' <shraddha@juniper.net>et>; Shraddha Hegde <shraddha=40juniper.net@dmarc.ietf.org>rg>; 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