[ippm] RFC 9617 on A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)

rfc-editor@rfc-editor.org Tue, 27 August 2024 16:10 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96860C180B61; Tue, 27 Aug 2024 09:10:01 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id DC74D7FA6D; Tue, 27 Aug 2024 09:10:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240827161000.DC74D7FA6D@rfcpa.rfc-editor.org>
Date: Tue, 27 Aug 2024 09:10:00 -0700
Message-ID-Hash: WDHU4AWVJH3FR2SGZPL6EZ7574PXC7AP
X-Message-ID-Hash: WDHU4AWVJH3FR2SGZPL6EZ7574PXC7AP
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ippm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ippm@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [ippm] RFC 9617 on A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/930nCtZ75n0Mm_Lv611_czIB99Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Owner: <mailto:ippm-owner@ietf.org>
List-Post: <mailto:ippm@ietf.org>
List-Subscribe: <mailto:ippm-join@ietf.org>
List-Unsubscribe: <mailto:ippm-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9617

        Title:      A YANG Data Model for 
                    In Situ Operations, Administration, and Maintenance 
                    (IOAM) 
        Author:     T. Zhou, Ed.,
                    J. Guichard,
                    F. Brockners,
                    S. Raghavan
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2024
        Mailbox:    zhoutianran@huawei.com,
                    james.n.guichard@futurewei.com,
                    fbrockne@cisco.com,
                    srihari@cisco.com
        Pages:      28
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-ioam-yang-13.txt

        URL:        https://www.rfc-editor.org/info/rfc9617

        DOI:        10.17487/RFC9617

In situ Operations, Administration, and Maintenance (IOAM) is an
example of an on-path hybrid measurement method. IOAM defines a
method for producing operational and telemetry information that may
be exported using the in-band or out-of-band method. RFCs 9197 and
9326 discuss the data fields and associated data types for IOAM. This
document defines a YANG module for the configuration of IOAM
functions.

This document is a product of the IP Performance Measurement Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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