A YANG Data Model for OSPF Segment Routing over the MPLS Data Plane
draft-ietf-ospf-sr-yang-50

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: Christian Hopps <chopps@chopps.org>, The IESG <iesg@ietf.org>, chopps@chopps.org, draft-ietf-ospf-sr-yang@ietf.org, gunter@vandevelde.cc, lsr-chairs@ietf.org, lsr@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'A YANG Data Model for OSPF Segment Routing over the MPLS Data Plane' to Proposed Standard (draft-ietf-ospf-sr-yang-48.txt)

The IESG has approved the following document:
- 'A YANG Data Model for OSPF Segment Routing over the MPLS Data Plane'
  (draft-ietf-ospf-sr-yang-48.txt) as Proposed Standard

This document is the product of the Link State Routing Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan
Talaulikar.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ospf-sr-yang/

Ballot Text

Technical Summary

   This document defines a YANG data module that can be used to
   configure and manage OSPF Extensions for Segment Routing for the MPLS
   data plane.

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? 

Nothing particular to mention

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

YANG doctor review completed and the module complies with the Network Management Datastore Architecture (NMDA)

Personnel

   The Document Shepherd for this document is Christian Hopps. The
   Responsible Area Director is Gunter Van de Velde.

RFC Editor Note