[Teas] [Errata Verified] RFC9522 (7815)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 20 February 2024 18:37 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61455C180B5B; Tue, 20 Feb 2024 10:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 VopxcsLvue19; Tue, 20 Feb 2024 10:37:48 -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 8DB63C180B53; Tue, 20 Feb 2024 10:37:48 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 68E061D5C; Tue, 20 Feb 2024 10:37:48 -0800 (PST)
To: nmalykh@protokols.ru, adrian@olddog.co.uk
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, teas@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240220183748.68E061D5C@rfcpa.amsl.com>
Date: Tue, 20 Feb 2024 10:37:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/mTVlkSCYa37RMhDNnWjvP5tiuEc>
Subject: [Teas] [Errata Verified] RFC9522 (7815)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Feb 2024 18:37:52 -0000
The following errata report has been verified for RFC9522, "Overview and Principles of Internet Traffic Engineering". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7815 -------------------------------------- Status: Verified Type: Editorial Reported by: Nikolai Malykh <nmalykh@protokols.ru> Date Reported: 2024-02-20 Verified by: RFC Editor Section: 5.1.3.7 Original Text ------------- IP Flow Information Export (IPFIX) [RFC5470] defines an architecture that is very similar to the RTFM architecture and includes Metering, Exporting, and Collecting Processes. [RFC5472] describes the applicability of IPFIX and makes a comparison with RTFM, pointing out that, architecturally, while RTM talks about devices, IPFIX deals with processes to clarify that multiple of those processes may be co- located on the same machine. The IPFIX protocol [RFC7011] is widely implemented. Corrected Text -------------- IP Flow Information Export (IPFIX) [RFC5470] defines an architecture that is very similar to the RTFM architecture and includes Metering, Exporting, and Collecting Processes. [RFC5472] describes the applicability of IPFIX and makes a comparison with RTFM, pointing out that, architecturally, while RTFM talks about devices, IPFIX deals with processes to clarify that multiple of those processes may be co- located on the same machine. The IPFIX protocol [RFC7011] is widely implemented. Notes ----- Missing a letter in the acronym RTFM. RTM > RTFM -------------------------------------- RFC9522 (draft-ietf-teas-rfc3272bis-27) -------------------------------------- Title : Overview and Principles of Internet Traffic Engineering Publication Date : January 2024 Author(s) : A. Farrel, Ed. Category : INFORMATIONAL Source : Traffic Engineering Architecture and Signaling Area : Routing Stream : IETF
- [Teas] [Errata Verified] RFC9522 (7815) RFC Errata System