[rfc-dist] RFC 9546 on Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane
rfc-editor@rfc-editor.org Thu, 29 February 2024 02:18 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E17DC14CF01; Wed, 28 Feb 2024 18:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, 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 qxkxninEk4LN; Wed, 28 Feb 2024 18:18:06 -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 5E123C14CEE3; Wed, 28 Feb 2024 18:18:06 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 30EAC19759CD; Wed, 28 Feb 2024 18:18:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, detnet@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240229021806.30EAC19759CD@rfcpa.amsl.com>
Date: Wed, 28 Feb 2024 18:18:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/-XQhEYuIq-5zew0Er2kThsEqMfE>
Subject: [rfc-dist] RFC 9546 on Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Feb 2024 02:18:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9546
Title: Operations, Administration, and Maintenance (OAM)
for Deterministic Networking (DetNet) with the
MPLS Data Plane
Author: G. Mirsky,
M. Chen,
B. Varga
Status: Standards Track
Stream: IETF
Date: February 2024
Mailbox: gregimirsky@gmail.com,
mach.chen@huawei.com,
balazs.a.varga@ericsson.com
Pages: 12
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-detnet-mpls-oam-15.txt
URL: https://www.rfc-editor.org/info/rfc9546
DOI: 10.17487/RFC9546
This document defines format and usage principles of the
Deterministic Networking (DetNet) service Associated Channel over a
DetNet network with the MPLS data plane. The DetNet service
Associated Channel can be used to carry test packets of active
Operations, Administration, and Maintenance (OAM) protocols that are
used to detect DetNet failures and measure performance metrics.
This document is a product of the Deterministic Networking 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