Re: [Pce] WG Adoption of draft-chen-pce-bier-11

chen.ran@zte.com.cn Sat, 07 October 2023 02:01 UTC

Return-Path: <chen.ran@zte.com.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63419C151539; Fri, 6 Oct 2023 19:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=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 UeMchBZlkfOp; Fri, 6 Oct 2023 19:01:55 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D042C15108B; Fri, 6 Oct 2023 19:01:53 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4S2T7K6FN9z4xPFs; Sat, 7 Oct 2023 10:01:49 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4S2T6n0WhNz4xVbt; Sat, 7 Oct 2023 10:01:21 +0800 (CST)
Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl2.zte.com.cn with SMTP id 39721B8E017920; Sat, 7 Oct 2023 10:01:11 +0800 (+08) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid203; Sat, 7 Oct 2023 10:01:12 +0800 (CST)
Date: Sat, 07 Oct 2023 10:01:12 +0800
X-Zmail-TransId: 2afe6520bbe8ffffffff97a-ee4cc
X-Mailer: Zmail v1.0
Message-ID: <202310071001124810972@zte.com.cn>
In-Reply-To: <CA+RyBmVtCgw3eots2+WsjD+cLxD=4C3xSa87zFdLRQBkgSs3rw@mail.gmail.com>
References: CAP7zK5ZTXKMgUN6JaXgL7sKc3XTzYD8VrUjq-b5joRLLBHyjbw@mail.gmail.com, CABNhwV0B4LizHTUXgnc=jHt1Ypn4xBaeF44G22JWd2us-GvFHg@mail.gmail.com, CA+RyBmVtCgw3eots2+WsjD+cLxD=4C3xSa87zFdLRQBkgSs3rw@mail.gmail.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: gregimirsky@gmail.com
Cc: dd@dhruvdhody.com, pce@ietf.org, draft-chen-pce-bier@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 39721B8E017920
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6520BC0D.003/4S2T7K6FN9z4xPFs
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/sqemC9NgIE9otHY0U0NP1Db6uoM>
Subject: Re: [Pce] WG Adoption of draft-chen-pce-bier-11
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Oct 2023 02:01:59 -0000

Hi Greg,

Thank you very much for your support and comments. 
Please see inline....

Best Regards,
Ran

Original


From: GregMirsky <gregimirsky@gmail.com>
To: Dhruv Dhody <dd@dhruvdhody.com>;pce@ietf.org <pce@ietf.org>;
Cc: draft-chen-pce-bier@ietf.org <draft-chen-pce-bier@ietf.org>;
Date: 2023年10月05日 15:55
Subject: Re: [Pce] WG Adoption of draft-chen-pce-bier-11

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


Dear All,I've read the draft and support its adoption by the PCE WG. A couple notes for future consideration:
Adrian earlier noted the number of names on the front page. Although the five is not a hard stop, it seems like conforming to the recommendation could be a wise approach.
[Ran]: Okay, the next version will retain five authors.

TE as Tree Engineering is used in the document is hard to distinguish from more used at IETF expansion of the acronym, Traffic engineering. Hence, several questions:

In your view, is Tree Engineering close to the Path Engineering, i.e., defining an explicit path, or it also includes the resource allocation and thus is closer to the true Traffic Engineering?

Assuming it is the former, could using the Path Engineering be acceptable?

If it is the latter, could TE in the draft be expanded as Traffic Engineering?

[Ran]: Follows the definition in RFC9262 (Tree Engineering for Bit Index Explicit Replication (BIER-TE) https://datatracker.ietf.org/doc/rfc9262/  ). In the definition of terms section, for BIER-TE, would it be more clear if I quoted RFC9262?



Regards,

Greg




On Thu, Oct 5, 2023 at 2:36 AM Gyan Mishra <hayabusagsm@gmail.com> wrote:



I support WG adoption.


Thanks 


Gyan


On Mon, Sep 25, 2023 at 12:50 PM Dhruv Dhody <dd@dhruvdhody.com> wrote:



Hi WG,

This email begins the WG adoption poll for draft-chen-pce-bier-11.

https://datatracker.ietf.org/doc/draft-chen-pce-bier/

Should this draft be adopted by the PCE WG? Please state your reasons - Why / Why not? What needs to be fixed before or after adoption? Are you willing to work on this draft? Review comments should be posted to the list.

Please respond by Monday 9th Oct 2023.

Please be more vocal during WG polls!

Thanks!
Dhruv & Julien


_______________________________________________
 Pce mailing list
 Pce@ietf.org
 https://www.ietf.org/mailman/listinfo/pce
 

_______________________________________________
 Pce mailing list
 Pce@ietf.org
 https://www.ietf.org/mailman/listinfo/pce