[IPFIX]Re: [Editorial Errata Reported] RFC7011 (8313)
Benoit Claise <benoit.claise@huawei.com> Tue, 25 February 2025 13:33 UTC
Return-Path: <benoit.claise@huawei.com>
X-Original-To: ipfix@mail2.ietf.org
Delivered-To: ipfix@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 67F68FBFF7 for <ipfix@mail2.ietf.org>; Tue, 25 Feb 2025 05:33:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietfa.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQe6FrM9KDtC for <ipfix@mail2.ietf.org>; Tue, 25 Feb 2025 05:33:34 -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 mail2.ietf.org (Postfix) with ESMTPS id CAA14FBFCF for <ipfix@ietf.org>; Tue, 25 Feb 2025 05:33:33 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Z2JPB61Jqz6K5jg; Tue, 25 Feb 2025 21:29:50 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id 5416414038F; Tue, 25 Feb 2025 21:33:32 +0800 (CST)
Received: from [10.48.153.130] (10.48.153.130) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Tue, 25 Feb 2025 14:33:28 +0100
Message-ID: <d36ae3ee-7017-479f-82d9-64c3e6d9d561@huawei.com>
Date: Tue, 25 Feb 2025 14:33:23 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: RFC Errata System <rfc-editor@rfc-editor.org>
References: <20250225131302.8667125D912@rfcpa.rfc-editor.org>
Content-Language: en-US
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <20250225131302.8667125D912@rfcpa.rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.48.153.130]
X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To frapeml500001.china.huawei.com (7.182.85.94)
Message-ID-Hash: H5QBK36P7N3CQOOVUMICXHWCIPEVYLOE
X-Message-ID-Hash: H5QBK36P7N3CQOOVUMICXHWCIPEVYLOE
X-MailFrom: benoit.claise@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipfix.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mohamed.boucadair@orange.com, bclaise@cisco.com, trammell@tik.ee.ethz.ch, paitken@cisco.com, ipfix@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8313)
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/v6vZA55NPMrksvvUtOhJUEWv2FQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Owner: <mailto:ipfix-owner@ietf.org>
List-Post: <mailto:ipfix@ietf.org>
List-Subscribe: <mailto:ipfix-join@ietf.org>
List-Unsubscribe: <mailto:ipfix-leave@ietf.org>
Dear all, Med is right in his thinking. We could have more precise with the specifications. Whether this errata is Verified or Hold for Document Update, I personally don't believe it's important as IMO this was never an issue in collector implementations. Regards, Benoit On 2/25/2025 2:13 PM, RFC Errata System wrote: > The following errata report has been submitted for RFC7011, > "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid8313 > > -------------------------------------- > Type: Editorial > Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com> > > Section: 3.2 > > Original Text > ------------- > E > > Enterprise bit. This is the first bit of the Field Specifier. If > this bit is zero, the Information Element identifier identifies an > Information Element in [IANA-IPFIX], and the four-octet Enterprise > Number field MUST NOT be present. If this bit is one, the > Information Element identifier identifies an enterprise-specific > Information Element, and the Enterprise Number field MUST be > present. > > Information Element identifier > > A numeric value that represents the Information Element. Refer to > [IANA-IPFIX]. > > Corrected Text > -------------- > E > > Enterprise bit. This is the first bit of the Field Specifier. If > this bit is zero, the Information Element identifier identifies an > Information Element in [IANA-IPFIX], and the four-octet Enterprise > Number field MUST NOT be present. If this bit is one, the > Information Element identifier identifies an enterprise-specific > Information Element, and the Enterprise Number field MUST be > present. > > Information Element identifier > > A numeric value that represents the Information Element. This field > takes a value in [IANA-IPFIX] when the E bit is set to zero. > > Notes > ----- > Makes it explicit that the values in [IANA-IPFIX] only applies when the is E-bit is unset. > > An alternative would be to simply delete "Refer to [IANA-IPFIX]." as the exact behavior is already mentioned under the E bit description. > > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it > will be removed shortly by the RFC Production Center.) Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC7011 (draft-ietf-ipfix-protocol-rfc5101bis-10) > -------------------------------------- > Title : Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information > Publication Date : September 2013 > Author(s) : B. Claise, Ed., B. Trammell, Ed., P. Aitken > Category : INTERNET STANDARD > Source : IP Flow Information Export > Stream : IETF > Verifying Party : IESG > > _______________________________________________ > IPFIX mailing list -- ipfix@ietf.org > To unsubscribe send an email to ipfix-leave@ietf.org
- [IPFIX][Editorial Errata Reported] RFC7011 (8313) RFC Errata System
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Benoit Claise
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Andrew Feren
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… mohamed.boucadair
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Paolo Lucente
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… mohamed.boucadair
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Aitken, Paul
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… mohamed.boucadair
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Madison Church
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Mahesh Jethanandani
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Madison Church
- [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8… Mahesh Jethanandani