IETF Logo Mail Archive

[IPv6] Fw: I-D Action: draft-ietf-6man-icmpv6-ioam-conf-state-03.txt

xiao.min2@zte.com.cn Tue, 23 April 2024 01:18 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 E3A93C180B5B for <ipv6@ietfa.amsl.com>; Mon, 22 Apr 2024 18:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.893
X-Spam-Level:
X-Spam-Status: No, score=-6.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 i886YfQwwYG5 for <ipv6@ietfa.amsl.com>; Mon, 22 Apr 2024 18:18:20 -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 A5BD6C151062 for <ipv6@ietf.org>; Mon, 22 Apr 2024 18:18:00 -0700 (PDT)
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 mxhk.zte.com.cn (FangMail) with ESMTPS id 4VNkkr6KPXz5R9kC for <ipv6@ietf.org>; Tue, 23 Apr 2024 09:17:56 +0800 (CST)
Received: from njy2app03.zte.com.cn ([10.40.13.14]) by mse-fl1.zte.com.cn with SMTP id 43N1HnMx004674 for <ipv6@ietf.org>; Tue, 23 Apr 2024 09:17:49 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid201; Tue, 23 Apr 2024 09:17:50 +0800 (CST)
Date: Tue, 23 Apr 2024 09:17:50 +0800
X-Zmail-TransId: 2afe66270c3efffffffff42-2115c
X-Mailer: Zmail v1.0
Message-ID: <20240423091750631sAYoYf0ldHBYqO0Z2Cnqi@zte.com.cn>
References: 171374936009.57848.2470533561475667186@ietfa.amsl.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: ipv6@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 43N1HnMx004674
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 66270C44.003/4VNkkr6KPXz5R9kC
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GQqVSQAMwLfWKpLUNFMM-M4JzF8>
Subject: [IPv6] Fw: I-D Action: draft-ietf-6man-icmpv6-ioam-conf-state-03.txt
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, 23 Apr 2024 01:18:22 -0000

Hi all,

This is a keep-alive update of draft-ietf-6man-icmpv6-ioam-conf-state, and there is only one editorial change.
I sincerely ask for your review on this draft. The authors on our own couldn't find something to improve this draft.


Best Regards,
Xiao Min

Original


From: internet-drafts@ietf.org <internet-drafts@ietf.org>
To: i-d-announce@ietf.org <i-d-announce@ietf.org>;
Cc: ipv6@ietf.org <ipv6@ietf.org>;
Date: 2024年04月22日 09:30
Subject: [IPv6] I-D Action: draft-ietf-6man-icmpv6-ioam-conf-state-03.txt

Internet-Draft draft-ietf-6man-icmpv6-ioam-conf-state-03.txt is now available.
It is a work item of the IPv6 Maintenance (6MAN) WG of the IETF.
 
   Title:   IPv6 Query for Enabled In-situ OAM Capabilities
   Authors: Xiao Min
            Greg Mirsky
   Name:    draft-ietf-6man-icmpv6-ioam-conf-state-03.txt
   Pages:   16
   Dates:   2024-04-21
 
Abstract:
 
   This document describes the application of the mechanism of
   discovering In-situ OAM (IOAM) capabilities, described in RFC 9359
   "Ping Enabled IOAM Capabilities", in IPv6 networks.  IPv6 Node IOAM
   Request uses the IPv6 Node Information messages, allowing the IOAM
   encapsulating node to discover the enabled IOAM capabilities of each
   IOAM transit and IOAM decapsulating node.
 
   This document updates RFCs 4620 and 4884.
 
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-icmpv6-ioam-conf-state/
 
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-6man-icmpv6-ioam-conf-state-03
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-6man-icmpv6-ioam-conf-state-03
 
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
 
 
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.43.4 | Report a Bug | By Email | System Status