Re: [RTG-DIR] [Pce] Routing directorate early review of draft-ietf-pce-lsp-extended-flags

xiong.quan@zte.com.cn Wed, 14 September 2022 07:24 UTC

Return-Path: <xiong.quan@zte.com.cn>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72125C14CF0B; Wed, 14 Sep 2022 00:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=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_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 V7w5DDCWQLiI; Wed, 14 Sep 2022 00:24:04 -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 11C1FC14F73A; Wed, 14 Sep 2022 00:24:01 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4MSBf66cg3z4xVnj; Wed, 14 Sep 2022 15:23:58 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.82]) (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 4MSBdX67wkz4y0vN; Wed, 14 Sep 2022 15:23:28 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl2.zte.com.cn with SMTP id 28E7Mv68005576; Wed, 14 Sep 2022 15:22:57 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid201; Wed, 14 Sep 2022 15:22:57 +0800 (CST)
Date: Wed, 14 Sep 2022 15:22:57 +0800
X-Zmail-TransId: 2af963218151ffffffff9024eb48
X-Mailer: Zmail v1.0
Message-ID: <202209141522573999848@zte.com.cn>
In-Reply-To: <202209091513210865386@zte.com.cn>
References: 202209091513210865386@zte.com.cn
Mime-Version: 1.0
From: xiong.quan@zte.com.cn
To: xiong.quan@zte.com.cn
Cc: jonhardwick@microsoft.com, pce-chairs@ietf.org, draft-ietf-pce-lsp-extended-flags.all@ietf.org, rtg-dir@ietf.org, pce@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 28E7Mv68005576
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 6321818E.002 by FangMail milter!
X-FangMail-Envelope: 1663140238/4MSBf66cg3z4xVnj/6321818E.002/192.168.251.13/[192.168.251.13]/mxct.zte.com.cn/<xiong.quan@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6321818E.002/4MSBf66cg3z4xVnj
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/JiYrTDLbehKi1_6a83IkM5Lxhcc>
Subject: Re: [RTG-DIR] [Pce] Routing directorate early review of draft-ietf-pce-lsp-extended-flags
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2022 07:24:08 -0000

Hi Jon and chairs,






Thanks for your suggestions!  A new version of I-D, draft-ietf-pce-lsp-extended-flags-04.txt


has been uploaded.Name:        draft-ietf-pce-lsp-extended-flagsRevision:    04Title:        Label Switched Path (LSP) Object Flag Extension of Stateful PCEDocument date:    2022-09-14Group:        pcePages:        9URL:            https://www.ietf.org/archive/id/draft-ietf-pce-lsp-extended-flags-04.txtStatus:         https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-extended-flags/Html:           https://www.ietf.org/archive/id/draft-ietf-pce-lsp-extended-flags-04.htmlHtmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-pce-lsp-extended-flagsDiff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-lsp-extended-flags-04Best Regards,


Quan                                                                                  
















Original



From: 熊泉00091065
To: jonhardwick@microsoft.com <jonhardwick@microsoft.com>;
Cc: pce-chairs@ietf.org <pce-chairs@ietf.org>;draft-ietf-pce-lsp-extended-flags.all@ietf.org <draft-ietf-pce-lsp-extended-flags.all@ietf.org>;rtg-dir@ietf.org <rtg-dir@ietf.org>;pce@ietf.org <pce@ietf.org>;
Date: 2022年09月09日 15:13
Subject: Re:[Pce] Routing directorate early review of draft-ietf-pce-lsp-extended-flags



Hi Jon and chairs,

Thanks for your review and comments! I will update a new version to modify the first text of Section 3.2 shown as following:

"The LSP Extended Flags field is an array of units of 32 flags and to be allocated starting from the most significant bit. The bits of the LSP Extended Flags field will be assigned by future documents. This document does not define any flags. Unassigned flags MUST be set to zero on transmission and MUST be ignored on receipt. Implementations that do not understand any particular flag MUST ignore the flag. This flags should follow the specification as per RFC8786."

What is your suggestion?

Best Regards,
Quan



<<[Pce] Routing directorate early review of draft-ietf-pce-lsp-extended-flags
Jon Hardwick  Thu, 08 September 2022 15:08 UTCShow header
Hi there I have been selected to do a routing directorate "early" review of this draft. draft-ietf-pce-lsp-extended-flags-03 - Label Switched Path (LSP) Object Flag Extension of Stateful PCEThe routing directorate will, on request from the working group chair, perform an "early" review of a draft before it is submitted for publication to the IESG. The early review can be performed at any time during the draft's lifetime as a working group document. The purpose of the early review depends on the stage that the document has reached. As this document is already post working group last call, my focus for the review was to determine whether the document is ready to be published. For more information about the routing area directorate, please see RtgDir - Routing Area Wiki (ietf.org)ir>. Summary I have some minor concerns about this document that I think should be resolved before the publication process begins. Comments Section 3.2 Please could you add explicit statements that unused flags should be set to zero on sending and ignored on receipt? I know we have RFC 8786 which covers this, but I think it does no harm to say it explicitly anyway.  Probably worth adding a normative reference to RFC 8786 as well. Section 5.1.2 Please note in the instructions to IANA that bits 0-31 should initially be marked as "Unassigned" and that bits with a higher ordinal than 31 will be added to the registry in future documents if necessary.