Skip to main content

Operations, Administration and Maintenance (OAM) for Deterministic Networks (DetNet) with MPLS Data Plane
draft-ietf-detnet-mpls-oam-15

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, detnet-chairs@ietf.org, detnet@ietf.org, draft-ietf-detnet-mpls-oam@ietf.org, janos.farkas@ericsson.com, jgs@juniper.net, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Operations, Administration and Maintenance (OAM) for Deterministic Networks (DetNet) with MPLS Data Plane' to Proposed Standard (draft-ietf-detnet-mpls-oam-15.txt)

The IESG has approved the following document:
- 'Operations, Administration and Maintenance (OAM) for Deterministic
   Networks (DetNet) with MPLS Data Plane'
  (draft-ietf-detnet-mpls-oam-15.txt) as Proposed Standard

This document is the product of the Deterministic Networking Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-oam/


Ballot Text

Technical Summary

   This document defines format and usage principles of the
   Deterministic Network (DetNet) service Associated Channel (ACH) over
   a DetNet network with the MPLS data plane.  The DetNet service ACH
   can be used to carry test packets of active Operations,
   Administration, and Maintenance protocols that are used to detect
   DetNet failures and measure performance metrics.

Working Group Summary

   "The normal WG process has been followed and the documents 
   reflect WG consensus with nothing special worth mentioning." 

Document Quality

   "While there is interest in this specification from multiple 
   vendors, there are no publicly known implementations yet. The 
   document is one of the key deliverables of the WG."

Personnel

   The Document Shepherd for this document is János Farkas. The Responsible
   Area Director is John Scudder.

RFC Editor Note

RFC Editor Note

  Please consider alphabetizing Section 2.1. ("Terminology and Acronyms").