RFC 9232 on Network Telemetry Framework
rfc-editor@rfc-editor.org Fri, 27 May 2022 15:14 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE68C26D458; Fri, 27 May 2022 08:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 hQV04i2Q9Vpk; Fri, 27 May 2022 08:14:30 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 678D2C1D5AA2; Fri, 27 May 2022 08:14:30 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 4842E2262275; Fri, 27 May 2022 08:14:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9232 on Network Telemetry Framework
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, opsawg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220527151430.4842E2262275@rfcpa.amsl.com>
Date: Fri, 27 May 2022 08:14:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/EvzLKr-ACiw6unNfyYgLONVKn_8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2022 15:14:34 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9232
Title: Network Telemetry Framework
Author: H. Song,
F. Qin,
P. Martinez-Julia,
L. Ciavaglia,
A. Wang
Status: Informational
Stream: IETF
Date: May 2022
Mailbox: haoyu.song@futurewei.com,
qinfengwei@chinamobile.com,
pedro@nict.go.jp,
laurent.ciavaglia@rakuten.com,
wangaj3@chinatelecom.cn
Pages: 33
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-opsawg-ntf-13.txt
URL: https://www.rfc-editor.org/info/rfc9232
DOI: 10.17487/RFC9232
Network telemetry is a technology for gaining network insight and
facilitating efficient and automated network management. It
encompasses various techniques for remote data generation,
collection, correlation, and consumption. This document describes an
architectural framework for network telemetry, motivated by
challenges that are encountered as part of the operation of networks
and by the requirements that ensue. This document clarifies the
terminology and classifies the modules and components of a network
telemetry system from different perspectives. The framework and
taxonomy help to set a common ground for the collection of related
work and provide guidance for related technique and standard
developments.
This document is a product of the Operations and Management Area Working Group Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
- RFC 9232 on Network Telemetry Framework rfc-editor