Re: [IPv6] ipv6 Digest, Vol 224, Issue 9
"wanghaojie@chinamobile.com" <wanghaojie@chinamobile.com> Thu, 08 December 2022 09:39 UTC
Return-Path: <wanghaojie@chinamobile.com>
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 553A3C14CE26 for <ipv6@ietfa.amsl.com>; Thu, 8 Dec 2022 01:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.875
X-Spam-Level:
X-Spam-Status: No, score=-6.875 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_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_MIME_MALF=0.01, 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 s6swC3LoQ6Bb for <ipv6@ietfa.amsl.com>; Thu, 8 Dec 2022 01:39:45 -0800 (PST)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 24E6DC14CF10 for <ipv6@ietf.org>; Thu, 8 Dec 2022 01:39:44 -0800 (PST)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.7]) by rmmx-syy-dmz-app09-12009 (RichMail) with SMTP id 2ee96391b0dc520-da6dd; Thu, 08 Dec 2022 17:39:41 +0800 (CST)
X-RM-TRANSID: 2ee96391b0dc520-da6dd
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from LAPTOP-5GS3BPC8 (unknown[10.1.6.6]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee46391b0dac50-13d9a; Thu, 08 Dec 2022 17:39:41 +0800 (CST)
X-RM-TRANSID: 2ee46391b0dac50-13d9a
Date: Thu, 08 Dec 2022 17:39:39 +0800
From: "wanghaojie@chinamobile.com" <wanghaojie@chinamobile.com>
To: ipv6 <ipv6@ietf.org>
References: <mailman.3736.1670432286.13241.ipv6@ietf.org>
X-Priority: 3
X-GUID: 004C3B28-FE08-4950-AB27-F7F299A0F7C0
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.178[cn]
Mime-Version: 1.0
Message-ID: <202212081739393705665@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart737465845563_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/fOdQ-lp1g-YApk4xvBmLpI1Z1y4>
Subject: Re: [IPv6] ipv6 Digest, Vol 224, Issue 9
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: Thu, 08 Dec 2022 09:39:50 -0000
Hi WG, I support the adoption for draft-xiao-6man-icmpv6-ioam-conf-state. I think the proposed discovery mechanism is helpful to IOAM applicaiton. Best regards, Haojie Wang China Mobile Research Institute Department of Fundamental Network Technology wanghaojie@chinamobile.com From: ipv6-request Date: 2022-12-08 00:58 To: ipv6 Subject: ipv6 Digest, Vol 224, Issue 9 Send ipv6 mailing list submissions to ipv6@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www.ietf.org/mailman/listinfo/ipv6 or, via email, send a message with subject or body 'help' to ipv6-request@ietf.org You can reach the person managing the list at ipv6-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6 digest..." Today's Topics: 1. Re: WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state (xiao.min2@zte.com.cn) 2. Re: WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state (Gyan Mishra) ---------------------------------------------------------------------- Message: 1 Date: Wed, 7 Dec 2022 11:19:36 +0800 (CST) From: <xiao.min2@zte.com.cn> To: <xiechf@chinatelecom.cn> Cc: <furry13@gmail.com>, <ipv6@ietf.org>, <6man-chairs@ietf.org> Subject: Re: [IPv6] WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state Message-ID: <202212071119365115366@zte.com.cn> Content-Type: text/plain; charset="utf-8" Hi Chongfeng, Thanks for your support and thoughtful review. I believe all your comments can be addressed after wg adoption. Please see inline... Best Regards, Xiao Min Original From: ChongfengXie <xiechf@chinatelecom.cn> To: ??10093570;Jen Linkova <furry13@gmail.com>; Cc: IPv6 List <ipv6@ietf.org>;6man Chairs <6man-chairs@ietf.org>; Date: 2022?12?06? 19:23 Subject: Re: Re: [IPv6]WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state 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. [XM]>>> Thank you. 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? [XM]>>> Yes, your're absolutely right. 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? [XM]>>> Good catch. I've mentioned the similar question in page 8 of my slides for IETF 115 presentation, and it's preferred to answer this question after wg adoption. 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. [XM]>>> I believe a reference to RFC 9197 would address your comment. RFC 9197 is the core spec for IOAM and it specifies what you want clearly. This draft doesn't change that in any way. 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 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 -------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://mailarchive.ietf.org/arch/browse/ipv6/attachments/20221207/262b3f0f/attachment.htm> ------------------------------ Message: 2 Date: Wed, 7 Dec 2022 11:57:44 -0500 From: Gyan Mishra <hayabusagsm@gmail.com> To: Jen Linkova <furry13@gmail.com> Cc: 6man <ipv6@ietf.org>, 6man Chairs <6man-chairs@ietf.org> Subject: Re: [IPv6] WG Adoption call for draft-xiao-6man-icmpv6-ioam-conf-state Message-ID: <CABNhwV3yG+LRgpm2MW87RahT0EZaq8y8XEXbQMw_f5vLQ2BCzQ@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Jen I support WG adoption of this draft. This draft provides a critical IOAM data node capabilities discovery mechanism feature for IOAM data functionality for HBH and DOH to carry IOAM data. This draft will be very useful for operators deploying SRv6 and have requirements for in situ IOAM data telemetry. Kind Regards Gyan On Fri, Dec 2, 2022 at 11:01 AM Jen Linkova <furry13@gmail.com> wrote: > 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 > -------------------------------------------------------------------- > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>* *M 301 502-1347* -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://mailarchive.ietf.org/arch/browse/ipv6/attachments/20221207/d51c590b/attachment.htm> ------------------------------ Subject: Digest Footer _______________________________________________ ipv6 mailing list ipv6@ietf.org https://www.ietf.org/mailman/listinfo/ipv6 ------------------------------ End of ipv6 Digest, Vol 224, Issue 9 ************************************
- Re: [IPv6] ipv6 Digest, Vol 224, Issue 9 wanghaojie@chinamobile.com