Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)
draft-ietf-anima-stable-connectivity-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-anima-stable-connectivity@ietf.org, anima-chairs@ietf.org, rfc-editor@rfc-editor.org, Sheng Jiang <jiangsheng@huawei.com>, terry.manderson@icann.org, anima@ietf.org, jiangsheng@huawei.com
Subject: Document Action: 'Using Autonomic Control Plane for Stable Connectivity of Network OAM' to Informational RFC (draft-ietf-anima-stable-connectivity-10.txt)

The IESG has approved the following document:
- 'Using Autonomic Control Plane for Stable Connectivity of Network OAM'
  (draft-ietf-anima-stable-connectivity-10.txt) as Informational RFC

This document is the product of the Autonomic Networking Integrated Model and
Approach Working Group.

The IESG contact persons are Warren Kumari, Benoit Claise and Terry Manderson.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-stable-connectivity/

Ballot Text

Technical Summary

   This document describes how to integrate OAM processes with the autonomic 
   control plane (ACP) in Autonomic Networks (AN) in order to provide stable
   and secure connectivity for those OAM processes.

Working Group Summary

  This document was called draft-eckert-anima-stable-connectivity prior to 
  its adoption. There was unanimous support for it in favor of adoption and 
  none against, so this document was adopted in December 2015. There was 
  interest in this work posts since its adoption. There was never any 
  opposition for this work.

  This document went through a relevant long document development
  period (12 months for individual document period, 22 month for WG 
  document period). It has been reviewed well.

Document Quality

  This document went through multiple reviews by multiple participants.
  So far, there is no existing implementations. 

Personnel

  Sheng Jiang is the document shepherd.
  Terry Manderson is the responsible AD.

RFC Editor Note