[OPSAWG] [Errata Verified] RFC9487 (7728)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 15 January 2024 10:11 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90168C14EB17; Mon, 15 Jan 2024 02:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 KgQIt1GO_83e; Mon, 15 Jan 2024 02:11:13 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE955C14F60C; Mon, 15 Jan 2024 02:11:13 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id A1F581A49952; Mon, 15 Jan 2024 02:11:13 -0800 (PST)
To: ahmed.elhassany@swisscom.com, thomas.graf@swisscom.com, benoit.claise@huawei.com, pierre.francois@insa-lyon.fr
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rwilton@cisco.com, iesg@ietf.org, opsawg@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240115101113.A1F581A49952@rfcpa.amsl.com>
Date: Mon, 15 Jan 2024 02:11:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/qhy4HNdaZjBISoQl_0SDRjkh1WY>
Subject: [OPSAWG] [Errata Verified] RFC9487 (7728)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2024 10:11:17 -0000

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