Re: [spring] The SPRING WG has placed draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 02 June 2023 07:42 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 495EFC14CF17; Fri, 2 Jun 2023 00:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 AzBqJudpi8A7; Fri, 2 Jun 2023 00:42:44 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56644C151980; Fri, 2 Jun 2023 00:42:44 -0700 (PDT)
Received: from lhrpeml100002.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4QXZjB4fp8z6J753; Fri, 2 Jun 2023 15:42:38 +0800 (CST)
Received: from kwepemi100015.china.huawei.com (7.221.188.125) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Fri, 2 Jun 2023 08:42:42 +0100
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi100015.china.huawei.com (7.221.188.125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Fri, 2 Jun 2023 15:42:40 +0800
Received: from kwepemi500017.china.huawei.com ([7.221.188.110]) by kwepemi500017.china.huawei.com ([7.221.188.110]) with mapi id 15.01.2507.023; Fri, 2 Jun 2023 15:42:40 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: IETF Secretariat <ietf-secretariat-reply@ietf.org>, "draft-schmutzer-spring-cs-sr-policy@ietf.org" <draft-schmutzer-spring-cs-sr-policy@ietf.org>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] The SPRING WG has placed draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"
Thread-Index: AQHZh/+qGzyyZTWgu0ivYG4q3zGP0a93NZ0w
Date: Fri, 02 Jun 2023 07:42:40 +0000
Message-ID: <59f488565b9644fa9379ee83c88ed881@huawei.com>
References: <168424587271.45431.10014516596562429177@ietfa.amsl.com>
In-Reply-To: <168424587271.45431.10014516596562429177@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/6z2o-j6HA87WnQEjRRUJT2Ocb3M>
Subject: Re: [spring] The SPRING WG has placed draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jun 2023 07:42:48 -0000

Hi Chairs,

I've read the latest version of this document and think it is a good starting point to describe a specific usage of SR policy to mimic the characteristics of circuit-based transport paths. Thus I support the adoption. 

I used to have comments about how bandwidth guarantee is achieved with CS-SR policy, and the recent updates in section 3.1 addressed some of my comments. 

While for some of the resource reservation mechanisms, it is not clear in the draft how is a CS-SR policy correlated with the set of reserved resources allocated (logical link, queue, etc.). A dedicate DSCP code point is one option, while it may not always be available. IMO the mechanisms described in draft-ietf-spring-resource-aware-segments could be used for such correlation, and I'd suggest to add that draft as a reference. 

Best regards,
Jie

> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of IETF Secretariat
> Sent: Tuesday, May 16, 2023 10:05 PM
> To: draft-schmutzer-spring-cs-sr-policy@ietf.org; spring-chairs@ietf.org;
> spring@ietf.org
> Subject: [spring] The SPRING WG has placed
> draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"
> 
> 
> The SPRING WG has placed draft-schmutzer-spring-cs-sr-policy in state
> Candidate for WG Adoption (entered by Joel Halpern)
> 
> The document is available at
> https://datatracker.ietf.org/doc/draft-schmutzer-spring-cs-sr-policy/
> 
> Comment:
> This starts a two week adoption call for the subject draft.  Please speak up if
> you support or object to WG adoption.  Two notes: 1) WG adoption is the
> start of the process.  The basic question is whether you agree that the
> subject is worth the working group time to work on, and whether this
> represents a good starting point for the work. 2) Please include explanation
> for your view.  Yes or no are not very helpful answers, as this is not a vote
> but an evaluation of support and concerns. Thank you, Joel (for the WG
> Chairs)
> 
> We expect to close this call at the end of May, 2023.
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring