[IPFIX] [Errata Held for Document Update] RFC7012 (6564)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 15 January 2024 09:55 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E02C14F6A4; Mon, 15 Jan 2024 01:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W0ceSFZg_QnC; Mon, 15 Jan 2024 01:55:52 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6905C14F6A5; Mon, 15 Jan 2024 01:55:52 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9E4CB1A49952; Mon, 15 Jan 2024 01:55:52 -0800 (PST)
To: paul.aitken@att.com, bclaise@cisco.com, trammell@tik.ee.ethz.ch
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rwilton@cisco.com, iesg@ietf.org, ipfix@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240115095552.9E4CB1A49952@rfcpa.amsl.com>
Date: Mon, 15 Jan 2024 01:55:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/_fUVKnV3H0hM9YH-FHPbnTPFMlw>
Subject: [IPFIX] [Errata Held for Document Update] RFC7012 (6564)
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 15 Jan 2024 09:55:57 -0000

The following errata report has been held for document update 
for RFC7012, "Information Model for IP Flow Information Export (IPFIX)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6564

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

Reported by: Paul Aitken <paul.aitken@att.com>
Date Reported: 2021-04-28
Held by: Rob Wilton (IESG)

Section: 7.2

Original Text
-------------
   The specification
   of new MPLS label types MUST be published using a well-established
   and persistent publication medium.

Corrected Text
--------------
(Deleted)

Notes
-----
This paragraph envisaged that a new RFC be written to specify new label types in the mplsTopLabelType sub-registry.

Since the publication of RFC7012, IANA has added 16 other IPFIX IE sub-registries, none of which have the same requirement. See https://www.iana.org/assignments/ipfix/ipfix.xhtml

Publication in IANA's IPFIX registry should provide a clear and persistent definition. New IPFIX MPLS label type specifications should not be singled out to require persistent publication of an additional document.

--------------------------------------
RFC7012 (draft-ietf-ipfix-information-model-rfc5102bis-10)
--------------------------------------
Title               : Information Model for IP Flow Information Export (IPFIX)
Publication Date    : September 2013
Author(s)           : B. Claise, Ed., B. Trammell, Ed.
Category            : PROPOSED STANDARD
Source              : IP Flow Information Export
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG