Re: [ippm] John Scudder's No Objection on draft-ietf-ippm-ioam-conf-state-09: (with COMMENT)

xiao.min2@zte.com.cn Tue, 22 November 2022 02:57 UTC

Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8BCDC14CE2E; Mon, 21 Nov 2022 18:57:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 oTnkyyctK_nk; Mon, 21 Nov 2022 18:57:28 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FAAEC14CE34; Mon, 21 Nov 2022 18:57:25 -0800 (PST)
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 4NGTSh1MCFz8RV7H; Tue, 22 Nov 2022 10:57:24 +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 4NGTS52gy2z4y0vG; Tue, 22 Nov 2022 10:56:53 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl2.zte.com.cn with SMTP id 2AM2ukA3019342; Tue, 22 Nov 2022 10:56:46 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Tue, 22 Nov 2022 10:56:47 +0800 (CST)
Date: Tue, 22 Nov 2022 10:56:47 +0800
X-Zmail-TransId: 2afd637c3a6f7dab4339
X-Mailer: Zmail v1.0
Message-ID: <202211221056476305902@zte.com.cn>
In-Reply-To: <166906708875.63924.16574150698267395095@ietfa.amsl.com>
References: 166906708875.63924.16574150698267395095@ietfa.amsl.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: jgs@juniper.net
Cc: iesg@ietf.org, draft-ietf-ippm-ioam-conf-state@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, marcus.ihlar@ericsson.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 2AM2ukA3019342
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.137.novalocal with ID 637C3A94.000 by FangMail milter!
X-FangMail-Envelope: 1669085844/4NGTSh1MCFz8RV7H/637C3A94.000/192.168.251.13/[192.168.251.13]/mxct.zte.com.cn/<xiao.min2@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 637C3A94.000/4NGTSh1MCFz8RV7H
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/TgQLeym2u909WJXkYNHVneUSRsQ>
Subject: Re: [ippm] John Scudder's No Objection on draft-ietf-ippm-ioam-conf-state-09: (with COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2022 02:57:32 -0000

Hi John,






Thank you for clearing your DISCUSS position.


I've posted -10 revision to incorporate your new text, which looks good to me, although the old one is also from you. :-)


Besides, in this revision the reference to draft-ietf-ippm-ioam-direct-export has been replaced by reference to published RFC9326. Link as below.


https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-conf-state-10 






Best Regards,


Xiao Min



Original



From: JohnScudderviaDatatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>;
Cc: draft-ietf-ippm-ioam-conf-state@ietf.org <draft-ietf-ippm-ioam-conf-state@ietf.org>;ippm-chairs@ietf.org <ippm-chairs@ietf.org>;ippm@ietf.org <ippm@ietf.org>;marcus.ihlar@ericsson.com <marcus.ihlar@ericsson.com>;marcus.ihlar@ericsson.com <marcus.ihlar@ericsson.com>;
Date: 2022年11月22日 05:44
Subject: John Scudder's No Objection on draft-ietf-ippm-ioam-conf-state-09: (with COMMENT)


John Scudder has entered the following ballot position for
draft-ietf-ippm-ioam-conf-state-09: No Objection
 
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
 
 
Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/  
for more information about how to handle DISCUSS and COMMENT positions.
 
 
The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-conf-state/
 
 
 
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
 
Thanks for the revisions. I have one further comment that occurred to me
in looking at the revised text:
 
                                                Note that since the
   Default-Namespace-ID of 0x0000 is mandated to appear first in the
   list, if it appears any trailing 0x0000 octets must therefore be
   padding and MUST be disregarded.
 
it seems to me it can be tightened up a little more, as in
 
   Since the Default-Namespace-ID of 0x0000 is mandated to appear first in
   the list, any other occurrences of 0x0000 MUST be disregarded.
 
That is, unless you want to mandate some kind of error response to
0x0000 appearing in a non-first, non-trailing position.