Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities
draft-ietf-ippm-ioam-conf-state-10

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>, draft-ietf-ippm-ioam-conf-state@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, marcus.ihlar@ericsson.com, martin.h.duke@gmail.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Echo Request/Reply for Enabled In-situ OAM Capabilities' to Proposed Standard (draft-ietf-ippm-ioam-conf-state-10.txt)

The IESG has approved the following document:
- 'Echo Request/Reply for Enabled In-situ OAM Capabilities'
  (draft-ietf-ippm-ioam-conf-state-10.txt) as Proposed Standard

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

The IESG contact persons are Zaheduzzaman Sarker and Martin Duke.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-conf-state/

Ballot Text

Technical Summary

   This document describes an extension to the echo request/reply
   mechanisms used in IPv6 (including Segment Routing with IPv6 data
   plane (SRv6)), MPLS (including Segment Routing with MPLS data plane
   (SR-MPLS)), Service Function Chain (SFC) and Bit Index Explicit
   Replication (BIER) environments, which can be used within the In situ
   Operations, Administration, and Maintenance (IOAM) domain, allowing
   the IOAM encapsulating node to discover the enabled IOAM capabilities
   of each IOAM transit and IOAM decapsulating node.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

   The WG consensus represents the strong concurrence of a few individuals, with
   others being silent.

Personnel

   The shepherd is Marcus Ihlar. The responsible AD is Martin Duke.

RFC Editor Note