Re: [Last-Call] [Pce] Opsdir last call review of draft-ietf-pce-lsp-extended-flags-05
xiong.quan@zte.com.cn Wed, 12 October 2022 02:53 UTC
Return-Path: <xiong.quan@zte.com.cn>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F76C14CE40; Tue, 11 Oct 2022 19:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.91
X-Spam-Level:
X-Spam-Status: No, score=-5.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, RCVD_IN_DNSWL_HI=-5, 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] 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 x4FDVPWEYas7; Tue, 11 Oct 2022 19:53:45 -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 529CDC14CF12; Tue, 11 Oct 2022 19:53:44 -0700 (PDT)
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 mxhk.zte.com.cn (FangMail) with ESMTPS id 4MnHKL6rx9z4xVnQ; Wed, 12 Oct 2022 10:53:42 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse-fl2.zte.com.cn with SMTP id 29C2rPg3044098; Wed, 12 Oct 2022 10:53:25 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Wed, 12 Oct 2022 10:53:25 +0800 (CST)
Date: Wed, 12 Oct 2022 10:53:25 +0800
X-Zmail-TransId: 2afb63462c25ffffffffe4c9b910
X-Mailer: Zmail v1.0
Message-ID: <202210121053250683294@zte.com.cn>
Mime-Version: 1.0
From: xiong.quan@zte.com.cn
To: noreply@ietf.org
Cc: ops-dir@ietf.org, draft-ietf-pce-lsp-extended-flags.all@ietf.org, last-call@ietf.org, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl2.zte.com.cn 29C2rPg3044098
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 63462C36.000 by FangMail milter!
X-FangMail-Envelope: 1665543222/4MnHKL6rx9z4xVnQ/63462C36.000/10.5.228.82/[10.5.228.82]/mse-fl2.zte.com.cn/<xiong.quan@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 63462C36.000/4MnHKL6rx9z4xVnQ
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/TS7quqhhHVBMyRR6i746VAqPYdM>
Subject: Re: [Last-Call] [Pce] Opsdir last call review of draft-ietf-pce-lsp-extended-flags-05
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Oct 2022 02:53:50 -0000
Hi Bo, Thanks for your review! Please see inline with Quan>>. Quan <<Original From: BoWuviaDatatracker <noreply@ietf.org> To: ops-dir@ietf.org <ops-dir@ietf.org>; Cc: draft-ietf-pce-lsp-extended-flags.all@ietf.org <draft-ietf-pce-lsp-extended-flags.all@ietf.org>;last-call@ietf.org <last-call@ietf.org>;pce@ietf.org <pce@ietf.org>; Date: 2022年10月11日 21:31 Subject: Opsdir last call review of draft-ietf-pce-lsp-extended-flags-05 Reviewer: Bo Wu Review result: Has Nits I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. The draft defines the PCE LSP object flag extension. The original 12 bits flags have been allocated, but a new individual draft requires new flags. In summary, the document is ready, with only small issues. Major issues: Minor issues: Introduction: The bits from 1 to 3 are assigned in [RFC8623] for Explicit Route Object (ERO)-compression, fragmentation and Point-to-Multipoint (P2MP) respectively. [Bo Wu] Here uses ERO object. But the title and abstract say Label Switched Path (LSP) Object Flag Extension, contradict? Quan>>The description of the two objects do not contradict. The flag extension is carried in LSP Object. And one bit of this flag is assigned and named ERO-compression flag. And if the ERO-compression flag is set to 1, it indicates the route is in compressed format as per [RFC8623]. 5. Backward Compatibility The LSP-EXTENDED-FLAG TLV defined in this document does not introduce any interoperability issues. [Bo Wu] I feel there are interoperability issues introduced, correct? But the issue will be resolved by the future use? Quan>>I think the TLV itself does not introduce any interoperability issues and the use of flag may introduce interoperability issues which may be resolved and considered by the future use. Maybe we should add this sentence in draft? Nits/editorial comments: Introduction: OLD The bit value 4 is assigned in [RFC8281] for create for PCE-Initiated LSPs. New The bit value 4 is assigned in [RFC8281] for creation and deletion for PCE-Initiated LSPs. Quan>>Thanks, will revise it in the new version.
- [Last-Call] Opsdir last call review of draft-ietf… Bo Wu via Datatracker
- Re: [Last-Call] [Pce] Opsdir last call review of … xiong.quan
- Re: [Last-Call] [Pce] Opsdir last call review of … Dhruv Dhody
- Re: [Last-Call] [Pce] Opsdir last call review of … xiong.quan
- Re: [Last-Call] [Pce] Opsdir last call review of … Wubo (lana)