IETF Logo Mail Archive

[IPFIX] Fwd: [Errata Verified] RFC9487 (7728)

Benoit Claise <benoit.claise@huawei.com> Mon, 22 January 2024 08:24 UTC

Return-Path: <benoit.claise@huawei.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 456A4C14F686 for <ipfix@ietfa.amsl.com>; Mon, 22 Jan 2024 00:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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, 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 6-1YrboIYr3G for <ipfix@ietfa.amsl.com>; Mon, 22 Jan 2024 00:24:37 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 362AAC14F684 for <ipfix@ietf.org>; Mon, 22 Jan 2024 00:24:37 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TJNVl0Dc7z6K5yJ for <ipfix@ietf.org>; Mon, 22 Jan 2024 16:22:07 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id 49D09140B3C for <ipfix@ietf.org>; Mon, 22 Jan 2024 16:24:34 +0800 (CST)
Received: from [10.81.206.22] (10.81.206.22) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Mon, 22 Jan 2024 09:24:32 +0100
Content-Type: multipart/alternative; boundary="------------0btXkCDfztsb8jCKdQFDvNaN"
Message-ID: <01137cda-94bb-47ca-924e-1fcc69d2a823@huawei.com>
Date: Mon, 22 Jan 2024 09:24:28 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
References: <20240115101113.A1F581A49952@rfcpa.amsl.com>
Content-Language: en-US
To: "ipfix@ietf.org" <ipfix@ietf.org>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <20240115101113.A1F581A49952@rfcpa.amsl.com>
X-Forwarded-Message-Id: <20240115101113.A1F581A49952@rfcpa.amsl.com>
X-Originating-IP: [10.81.206.22]
X-ClientProxiedBy: dggems703-chm.china.huawei.com (10.3.19.180) To frapeml500001.china.huawei.com (7.182.85.94)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/oRWn6klPUwORwRrswWi0NEBX0IA>
Subject: [IPFIX] Fwd: [Errata Verified] RFC9487 (7728)
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2024 08:24:41 -0000

FYI.

Regards, Benoit


-------- Forwarded Message --------
Subject: 	[Errata Verified] RFC9487 (7728)
Date: 	Mon, 15 Jan 2024 02:11:13 -0800
From: 	RFC Errata System <rfc-editor@rfc-editor.org>
To: 	ahmed.elhassany@swisscom.com, thomas.graf@swisscom.com, 
benoit.claise@huawei.com, pierre.francois@insa-lyon.fr
CC: 	rwilton@cisco.com, iesg@ietf.org, opsawg@ietf.org, iana@iana.org, 
rfc-editor@rfc-editor.org



The following errata report has been verified for RFC9487,
"Export of Segment Routing over IPv6 Information in IP Flow Information 
Export (IPFIX)".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7728

--------------------------------------
Status: Verified
Type: Technical

Reported by: Ahmed Elhassany <ahmed.elhassany@swisscom.com>
Date Reported: 2023-12-12
Verified by: Rob Wilton (IESG)

Section: 5.1.10

Original Text
-------------
5.1.10. srhSegmentIPv6LocatorLength

ElementID: 501
Name: srhSegmentIPv6LocatorLength
Data Type Semantics: default
Description: The length of the SRH segment IPv6 locator specified as
the number of significant bits. Together with srhSegmentIPv6, it
enables the calculation of the SRv6 Locator.
Additional Information: See Section 3.1 of [RFC8986] for more
details about the SID format.
Reference: RFC 9487

Corrected Text
--------------
5.1.10. srhSegmentIPv6LocatorLength

ElementID: 501
Name: srhSegmentIPv6LocatorLength
Abstract Data Type: unsigned8
Data Type Semantics: default
Description: The length of the SRH segment IPv6 locator specified as
the number of significant bits. Together with srhSegmentIPv6, it
enables the calculation of the SRv6 Locator.
Additional Information: See Section 3.1 of [RFC8986] for more
details about the SID format.
Reference: RFC 9487

Notes
-----
I'm not an expert on RFC8986, I assumed it's unsigned8 but need help to 
check this is the case indeed

--------------------------------------
RFC9487 (draft-ietf-opsawg-ipfix-srv6-srh-14)
--------------------------------------
Title : Export of Segment Routing over IPv6 Information in IP Flow 
Information Export (IPFIX)
Publication Date : November 2023
Author(s) : T. Graf, B. Claise, P. Francois
Category : PROPOSED STANDARD
Source : Operations and Management Area Working Group
Area : Operations and Management
Stream : IETF
Verifying Party : IESG

v2.23.0 | Report a Bug | By Email