Re: [ippm] Erik Kline's No Objection on draft-ietf-ippm-ioam-conf-state-07: (with COMMENT)

xiao.min2@zte.com.cn Fri, 28 October 2022 03:03 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 90293C1524A2; Thu, 27 Oct 2022 20:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 16Ppd_02bZPG; Thu, 27 Oct 2022 20:03:49 -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 35A79C1524B7; Thu, 27 Oct 2022 20:03:48 -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 4Mz6nZ4FRxz5BNS0; Fri, 28 Oct 2022 11:03:46 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (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 4Mz6n03jHpz510YS; Fri, 28 Oct 2022 11:03:16 +0800 (CST)
Received: from njxh01app02.zte.com.cn ([10.41.132.206]) by mse-fl1.zte.com.cn with SMTP id 29S336TG037761; Fri, 28 Oct 2022 11:03:06 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxh01app01[null]) by mapi (Zmail) with MAPI id mid201; Fri, 28 Oct 2022 11:03:08 +0800 (CST)
Date: Fri, 28 Oct 2022 11:03:08 +0800
X-Zmail-TransId: 2af9635b466cffffffffc132dbe6
X-Mailer: Zmail v1.0
Message-ID: <202210281103081540507@zte.com.cn>
In-Reply-To: <166685760885.46710.2566014568059455494@ietfa.amsl.com>
References: 166685760885.46710.2566014568059455494@ietfa.amsl.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: ek.ietf@gmail.com
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-fl1.zte.com.cn 29S336TG037761
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 635B4692.001 by FangMail milter!
X-FangMail-Envelope: 1666926226/4Mz6nZ4FRxz5BNS0/635B4692.001/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: 635B4692.001/4Mz6nZ4FRxz5BNS0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/9WvzfEFKCA5yDC2WrxZBIZxfe4Y>
Subject: Re: [ippm] Erik Kline's No Objection on draft-ietf-ippm-ioam-conf-state-07: (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: Fri, 28 Oct 2022 03:03:53 -0000

Hi Erik,






Thank you for the review and thoughtful comments.


Please check inline the proposed changes that will be incorporated into the next revision.





Best Regards,


Xiao Min







Original



From: ErikKlineviaDatatracker <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年10月27日 16:00
Subject: Erik Kline's No Objection on draft-ietf-ippm-ioam-conf-state-07: (with COMMENT)


Erik Kline has entered the following ballot position for
draft-ietf-ippm-ioam-conf-state-07: 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:
----------------------------------------------------------------------
 
# Internet AD comments for draft-ietf-ippm-ioam-conf-state-07
CC @ekline
 
I support John's request for clarification.
 
## Comments
 
### S3.1
 
* "MUST send an echo reply without IOAM capabilities or no echo reply" 
 
  I think I understand the intent, and overall I think this text is likely
  to not be an issue in practice.  But I'll note that anything "MUST" where
  ICMP is concerned may not exactly be enforceable.

[XM]>>> Understood. Will remain the text you quoted as is. At the same time, I propose a change in S3.2 as below because I found there is exception out of MUST.

OLD

A list of IOAM capabilities objects (one
 or more objects) which contains the enabled IOAM capabilities MUST be
 included in this container of echo reply.NEW

A list of IOAM capabilities objects (one
 or more objects) which contains the enabled IOAM capabilities MUST be
 included in this container of echo reply except the sender encounters 
 an error (e.g., no matched Namespace-ID).


## Nits
 
### S2.2
 
* Maybe consider adding DEX to this list (it's also fully expanded on first
  use in S1, but it might be nice for ease of reference).

[XM]>>> OK. Will add DEX to this list.


### S3.1, S3.2
 
* /depends on the specific environment it is applied at/ -> 
  /depends on the specific deployment environment/ maybe?
 [XM]>>> OK. Will change the text as you suggested.