[IPFIX][Errata Held for Document Update] RFC7011 (8313)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 12 March 2025 15:43 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ipfix@ietf.org
Delivered-To: ipfix@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 10A3DA6F0B7; Wed, 12 Mar 2025 08:43:59 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id C59B1236A82; Wed, 12 Mar 2025 08:43:58 -0700 (PDT)
To: mohamed.boucadair@orange.com, bclaise@cisco.com, trammell@tik.ee.ethz.ch, paitken@cisco.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250312154358.C59B1236A82@rfcpa.rfc-editor.org>
Date: Wed, 12 Mar 2025 08:43:58 -0700
Message-ID-Hash: YMRWOUP7BONLP46RH3PRSNF3MEFKZLLB
X-Message-ID-Hash: YMRWOUP7BONLP46RH3PRSNF3MEFKZLLB
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
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: mjethanandani@gmail.com, iesg@ietf.org, ipfix@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [IPFIX][Errata Held for Document Update] RFC7011 (8313)
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/QaQHq8apkFbzpCAUzm6Bmvj3FD8>
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>
The following errata report has been held for document update 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 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com> Date Reported: 2025-02-25 Held by: Mahesh Jethanandani (IESG) 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. -------------------------------------- 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][Errata Held for Document Update] RFC7011 … RFC Errata System