[IPFIX] [Errata Held for Document Update] RFC7011 (7413)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 26 April 2023 19:03 UTC

To: mwd@cert.org, bclaise@cisco.com, trammell@tik.ee.ethz.ch, paitken@cisco.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, ipfix@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230426190234.DDEDDF3623@rfcpa.amsl.com>
Date: Wed, 26 Apr 2023 12:02:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/ggNnUX33ycx7zxGl1yQ3qEya1EI>
Subject: [IPFIX] [Errata Held for Document Update] RFC7011 (7413)
Precedence: list

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/eid7413

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Michael Duggan <mwd@cert.org>
Date Reported: 2023-04-02
Held by: Wa (IESG)

Section: 3.4.1

Original Text
-------------
Field Count

Number of fields in this Template Record.

Corrected Text
--------------
Field Count

Number of fields in this Template Record. The Field Count MUST NOT be zero, unless used in a Template Withdrawal.

Notes
-----
If the size of data record corresponding to a template can ever be zero, then the only valid size for such a data set is the size of the set header. For normal cases any size greater than that of the set header is a valid size, since records are read from a set until the number of octets remaining is less than the smallest possible record size for that set. If a record size can be zero, then any number of bytes past the header cannot be padding (is not smaller than the smallest record), and a conforming implementation might return an infinite number of zero-sized records. As this could cause a denial of service situation, rejecting templates that define zero-sized records seems to be the simplest solution.

Similar text may be necessary for Option Template records, though the fact that the scope count MUST be non-zero may negate the necessity.

---
WK: See thread https://mailarchive.ietf.org/arch/msg/ipfix/AkCZr1jObLt_x9cyQ73qXBlKC2w/ for more info.
WK - 2023-04-26: Update from the original reporter (Michael) and confirmations from authors (Brian and Benoit) that Field Count can be zero in the case of Template Withdrawal. Changing the state from Verified to HFDU, so that this can be better clarified in any future updates.

--------------------------------------
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
Area : Operations and Management
Stream : IETF
Verifying Party : IESG

[IPFIX] [Errata Held for Document Update] RFC7011… RFC Errata System