MPLS Network Action (MNA) Sub-Stack Specification including In-Stack Network Actions and Data
draft-ietf-mpls-mna-hdr-20

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-mpls-mna-hdr@ietf.org, james.n.guichard@futurewei.com, mpls-chairs@ietf.org, mpls@ietf.org, rfc-editor@rfc-editor.org, tsaad@cisco.com
Subject: Protocol Action: 'MPLS Network Action (MNA) Sub-Stack Solution' to Proposed Standard (draft-ietf-mpls-mna-hdr-17.txt)

The IESG has approved the following document:
- 'MPLS Network Action (MNA) Sub-Stack Solution'
  (draft-ietf-mpls-mna-hdr-17.txt) as Proposed Standard

This document is the product of the Multiprotocol Label Switching 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-mpls-mna-hdr/

Ballot Text

Technical Summary

   This document defines the MPLS Network Actions (MNA) sub-stack
   solution for carrying Network Actions and Ancillary Data in the MPLS
   label stack.  MNA can be used to influence packet forwarding
   decisions, carry additional Operations, Administration, and
   Maintenance information in the MPLS packet or perform user-defined
   operations.  The solution specified in this document addresses the
   requirements for In-stack network action and In-stack data found in
   RFC 9613.  This document follows the architectural framework for the
   MNA technologies specified in RFC 9789.

Working Group Summary

   Broad concensus to move forward to publication. Many directore reviews and 3 WG LCs have significantly improved the document. 

Document Quality

   As per the shepherd writeup, the document includes an implementation section in Section 12. There is one reported implementation of the solution.

Personnel

   The Document Shepherd for this document is Tarek Saad. The Responsible
   Area Director is Jim Guichard.

RFC Editor Note