Re: [IPFIX] Data type for srhSegmentIPv6LocatorLength in IPFIX Entities registry

"Brian Trammell (IETF)" <ietf@trammell.ch> Tue, 12 December 2023 08:46 UTC

Return-Path: <ietf@trammell.ch>
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 B8105C00891F for <ipfix@ietfa.amsl.com>; Tue, 12 Dec 2023 00:46:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trammell.ch
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 HFdlapBZAJ4u for <ipfix@ietfa.amsl.com>; Tue, 12 Dec 2023 00:46:46 -0800 (PST)
Received: from smtp-8fad.mail.infomaniak.ch (smtp-8fad.mail.infomaniak.ch [83.166.143.173]) (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 064BCC09C23D for <ipfix@ietf.org>; Tue, 12 Dec 2023 00:46:44 -0800 (PST)
Received: from smtp-2-0001.mail.infomaniak.ch (unknown [10.5.36.108]) by smtp-2-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4SqC020L3FzMq4Rh; Tue, 12 Dec 2023 08:46:42 +0000 (UTC)
Received: from unknown by smtp-2-0001.mail.infomaniak.ch (Postfix) with ESMTPA id 4SqC014Q1czMpnPm; Tue, 12 Dec 2023 09:46:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=trammell.ch; s=20191114; t=1702370801; bh=AakkkufXV8604lQ0YTYBwwLNkqbCk1tEfFiuTcEVIf4=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=JZCNxoSS8tgvFjlR/D04gK8Wbs9OtT1uc9OBhnJwfUPXPoDNjzWz6tUx8NVkGDPWQ kdfi9l0ag25Atz325E5Cn03iIdaEB656J2CNCqErLP0oFVl+rjpliUfYaDqhAPvOuF MEUwEgE/dDTgRDll9Nr5DkvP6legJz2dzs4C4n1g=
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <5F28CBFD-6D6D-4D38-A7F6-E5110B5D0B02@trammell.ch>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8FD83FAF-9FCA-44CD-9E65-66C73ED1AAD9"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
Date: Tue, 12 Dec 2023 09:46:31 +0100
In-Reply-To: <D6C94B32-C9DA-4EEB-85E9-2FE9687F7591@swisscom.com>
Cc: ipfix@ietf.org
To: Ahmed.Elhassany@swisscom.com
References: <D6C94B32-C9DA-4EEB-85E9-2FE9687F7591@swisscom.com>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
X-Infomaniak-Routing: alpha
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/P6NPYE5blkb9gwT6w_K9fO4lQIo>
Subject: Re: [IPFIX] Data type for srhSegmentIPv6LocatorLength in IPFIX Entities registry
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: Tue, 12 Dec 2023 08:46:51 -0000

hi Ahmed,

Yep, this is an erratum. 

Not an SR expert but as this is a “significant bit counter” I suspect unsigned8 is the appropriate type here.

Cheers, 

Brian

> On 12 Dec 2023, at 09:42, <Ahmed.Elhassany@swisscom.com> <Ahmed.Elhassany@swisscom.com> wrote:
> 
> Hello all, 
>  
> I noticed IE 501 srhSegmentIPv6LocatorLength is recently added to the ipfix registry https://www.iana.org/assignments/ipfix/ipfix.xmlwithout an abstract data type defined (in XML registry <dataType/>). I checked RFC 9487 that added this element to the registry, and it also doesn’t define an abstract data type for IE 501 srhSegmentIPv6LocatorLength.
>  
>  
> This sound contradictory to RFC  7012 which states that:
> dataType - One of the types listed in Section 3.1 <https://www.rfc-editor.org/rfc/rfc7012.html#section-3.1> of this document or
>       registered in the IANA "IPFIX Information Element Data Types"
>       subregistry.
>  
> The implication for not putting a data type in the registry that automated code generators for parsing and handling IPFIX will not work. A user must intervene manually and read the references RFCs to figure out the appropriate data type to be used.
>  
> My question to the mailing list: Is my understanding for RFC7012 correct that a data type must be defined as one of IPFIX Information Element Data Types? And if so, I think we need to report an erratum for the RFC9487 and update the registry accordingly.
>  
>  
> Best,
> -Ahmed
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org <mailto:IPFIX@ietf.org>
> https://www.ietf.org/mailman/listinfo/ipfix