Extension/update to RFC 4620 for IOAM Capabilities
xiao.min2@zte.com.cn Tue, 02 August 2022 09:13 UTC
Return-Path: <xiao.min2@zte.com.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 3B339C15C52C for <ipv6@ietfa.amsl.com>; Tue, 2 Aug 2022 02:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.911
X-Spam-Level:
X-Spam-Status: No, score=-0.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=no 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 f3CmLmQ1kDj0 for <ipv6@ietfa.amsl.com>; Tue, 2 Aug 2022 02:13:42 -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 0E988C15A730 for <ipv6@ietf.org>; Tue, 2 Aug 2022 02:13:41 -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 4Lxq6X0wwdz5BNRf; Tue, 2 Aug 2022 17:13:40 +0800 (CST)
Received: from njxapp02.zte.com.cn ([10.41.132.201]) by mse-fl2.zte.com.cn with SMTP id 2729DZgf083258; Tue, 2 Aug 2022 17:13:35 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Tue, 2 Aug 2022 17:13:35 +0800 (CST)
Date: Tue, 02 Aug 2022 17:13:35 +0800
X-Zmail-TransId: 2afd62e8eabffffffffff72a7ccd
X-Mailer: Zmail v1.0
Message-ID: <202208021713357006135@zte.com.cn>
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: evyncke@cisco.com, ek.ietf@gmail.com, bob.hinden@gmail.com
Cc: ipv6@ietf.org
Subject: Extension/update to RFC 4620 for IOAM Capabilities
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl2.zte.com.cn 2729DZgf083258
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 62E8EAC4.000 by FangMail milter!
X-FangMail-Envelope: 1659431620/4Lxq6X0wwdz5BNRf/62E8EAC4.000/10.5.228.82/[10.5.228.82]/mse-fl2.zte.com.cn/<xiao.min2@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 62E8EAC4.000/4Lxq6X0wwdz5BNRf
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/L5DuBbb9PAPiBK30PZ_IujcqoIE>
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, 02 Aug 2022 09:13:43 -0000
Dear éric, Erik, Bob, et al., I've finished exploring an extension/update to RFC 4620 for IOAM Capabilities. I'd like to share my thoughts with you. Firstly, I conclude that an extensible ICMPv6 format for IPv6 Node Information Queries can be achieved by combining RFC 4620 and RFC 4884 which defines ICMP Extension Structure, so I believe it's possible to define an extension/update to RFC 4620 for IOAM Capabilities Queries. Secondly, if it's decided to go down this way, one approach is to submit a new -00 draft replacing draft-xiao-6man-icmpv6-ioam-conf-state-01, with a title like *IPv6 Node Information Queries Version 2* (INIQv2), defining INIQv2 and having Enabled IOAM Capabilities carried by INIQv2. Due to the extensibility of INIQv2, more IPv6 Node Information can be added later, in a separate document. Best Regards, Xiao Min