[IPFIX] [Errata Verified] RFC7011 (4396)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 17 July 2015 15:50 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A43271A1BB0; Fri, 17 Jul 2015 08:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGC3pLYORL20; Fri, 17 Jul 2015 08:50:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 645961A1B11; Fri, 17 Jul 2015 08:50:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 89052180204; Fri, 17 Jul 2015 08:46:49 -0700 (PDT)
To: rick.hofstede@redsocks.nl, bclaise@cisco.com, trammell@tik.ee.ethz.ch, paitken@cisco.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150717154649.89052180204@rfc-editor.org>
Date: Fri, 17 Jul 2015 08:46:49 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipfix/41ByHLuSNzE3J9cVkeG1_j1BzwQ>
Cc: iesg@ietf.org, ipfix@ietf.org, rfc-editor@rfc-editor.org
Subject: [IPFIX] [Errata Verified] RFC7011 (4396)
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 17 Jul 2015 15:50:55 -0000
The following errata report has been verified 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: http://www.rfc-editor.org/errata_search.php?rfc=7011&eid=4396 -------------------------------------- Status: Verified Type: Editorial Reported by: Rick Hofstede <rick.hofstede@redsocks.nl> Date Reported: 2015-06-19 Verified by: Benoit Claise (IESG) Section: 3.1 Original Text ------------- Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process. Corrected Text -------------- Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process, prior to the receipt of this IPFIX Message. Notes ----- The original specification can be interpreted in two ways: (1) Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process *up to* this Message. (2) Incremental sequence counter modulo 2^32 of all IPFIX Data Records sent in the current stream from the current Observation Domain by the Exporting Process *up to and including* this Message. It seems that only Section 10.3.2 â Reliability explains which of the two interpretations is right: In the case of UDP, the IPFIX Sequence Number contains the total number of IPFIX Data Records sent for the Transport Session *prior* to the receipt of this IPFIX Message, modulo 2^32. In my opinion, it would be good to clarify the use of sequence numbers in Message headers already in the definition of sequence numbers in RFC 7011, namely in Section 3.1. Discussed here: https://mailarchive.ietf.org/arch/msg/ipfix/AQKObQ2WA_zIXgRzdxRsDrIWjx0 -------------------------------------- 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] [Editorial Errata Reported] RFC7011 (4396) RFC Errata System
- [IPFIX] [Errata Verified] RFC7011 (4396) RFC Errata System