IETF Logo Mail Archive

[IPFIX][Editorial Errata Reported] RFC7011 (8313)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 25 February 2025 13:13 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ipfix@mail2.ietf.org
Delivered-To: ipfix@mail2.ietf.org
Received: from mail2.ietf.org (mail2 [166.84.6.31]) (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 ESMTPSA id 252F8FAC9B; Tue, 25 Feb 2025 05:13:03 -0800 (PST)
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 16E50FAC9A; Tue, 25 Feb 2025 05:13:03 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 8667125D912; Tue, 25 Feb 2025 05:13:02 -0800 (PST)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250225131302.8667125D912@rfcpa.rfc-editor.org>
Date: Tue, 25 Feb 2025 05:13:02 -0800
Message-ID-Hash: CTM7S34APCUUFWS4UY6FMH6JZCFD4XER
X-Message-ID-Hash: CTM7S34APCUUFWS4UY6FMH6JZCFD4XER
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: 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][Editorial Errata Reported] RFC7011 (8313)
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/JIQ3AVZKsxiQgCZn7SmYS8YPrcw>
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 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

v2.29.0 | Report a Bug | By Email | System Status