Re: [IPv6] WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state

Chongfeng Xie <xiechf@chinatelecom.cn> Tue, 06 December 2022 11:23 UTC

Return-Path: <xiechf@chinatelecom.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D02DC14CE34; Tue, 6 Dec 2022 03:23:48 -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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 4nMdNxeITDn5; Tue, 6 Dec 2022 03:23:44 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.220]) by ietfa.amsl.com (Postfix) with ESMTP id 3369BC14CE47; Tue, 6 Dec 2022 03:23:43 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.218:58104.629459668
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-114.250.179.166 (unknown [172.18.0.218]) by chinatelecom.cn (HERMES) with SMTP id D4BAE280090; Tue, 6 Dec 2022 19:23:35 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([114.250.179.166]) by app0025 with ESMTP id ab80a93fadb84003b8b566c755915411 for xiao.min2@zte.com.cn; Tue, 06 Dec 2022 19:23:41 CST
X-Transaction-ID: ab80a93fadb84003b8b566c755915411
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 114.250.179.166
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Tue, 06 Dec 2022 19:23:37 +0800
From: Chongfeng Xie <xiechf@chinatelecom.cn>
To: "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>, Jen Linkova <furry13@gmail.com>
Cc: IPv6 List <ipv6@ietf.org>, 6man Chairs <6man-chairs@ietf.org>
References: CAFU7BAQkdo+21xtL0GSLTcHZVG1hzUQRAwBcx_yNhhMh6yQ=Cw@mail.gmail.com, <202212050934368717655@zte.com.cn>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.24.96[cn]
Mime-Version: 1.0
Message-ID: <202212061923365953563@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart175384447016_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gq62u0mf03m4U9hR_pPkE9ROaxI>
Subject: Re: [IPv6] WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2022 11:23:48 -0000

Hi 6man chairs and all,

I support the adoption of this draft.

This document illustrates the IPv6 Node IOAM Information Query functionality, which enables the IOAM encapsulating node discover the enabled IOAM capabilities of each IOAM transit and decapsulating node. I think this is useful. 

I also have two questions and one suggestion as below,

Q 1. From the perspective of time dimension, is the process described in this document before the process described in the document draft-ietf-ippm-ioam-ipv6-options?The latter describes how packets use the IOAM when they traverses a path between two points in the network。

Q 2.The type of this document is stand track, in which the approach described is based on IPv6 Node Information messages, but RFC4620 mentions that ‘it defines an Experimental Protocol for the Internet community.  It does not specify an Internet standard of any kind’. I don't know whether it is appropriate to define standard track type document based-on the experimental protocol?

One suggestion:
The current document mainly introduces the message format. I suggest adding a figure to describe the the location of the different roles, e.g., IOAM encoding node, IOAM transit and decapitating node in the network. If necessary, the workflow can also be introduced based on this figure.

Best regards

Chongfeng
 
From: xiao.min2@zte.com.cn
Date: 2022-12-05 09:34
To: furry13@gmail.com
CC: ipv6@ietf.org; 6man-chairs@ietf.org
Subject: Re: [IPv6]WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state
Hi Jen,

As a co-author, I support wg adoption of this draft.

Thanks!
Xiao Min
Original
From: JenLinkova <furry13@gmail.com>
To: 6man <ipv6@ietf.org>;
Cc: 6man Chairs <6man-chairs@ietf.org>;
Date: 2022年12月03日 00:01
Subject: [IPv6] WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state
This message starts a call on adopting the following draft as a 6MAN
working group document :

Title:   IPv6 Query for Enabled In-situ OAM Capabilities
Authors:        Xiao Min , Greg Mirsky
File Name:   draft-xiao-6man-icmpv6-ioam-conf-state-02
Datatracker: https://datatracker.ietf.org/doc/draft-xiao-6man-icmpv6-ioam-conf-state/

Substantive comments and statements of support for adopting this
document should be sent to the mailing list. Editorial suggestions can
be sent to the authors.

This adoption call will end on Dec 18th 2022, 23:59:59 UTC

--  
SY, Jen Linkova on behalf of 6MAN chairs.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------