<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-mna-hdr" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-hdr-12">
   <front>
      <title>MPLS Network Action (MNA) Sub-Stack Solution</title>
      <author initials="J." surname="Rajamanickam" fullname="Jaganbabu Rajamanickam">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="R." surname="Zigler" fullname="Royi Zigler">
         <organization>Broadcom</organization>
      </author>
      <author initials="H." surname="Song" fullname="Haoyu Song">
         <organization>Futurewei Technologies</organization>
      </author>
      <author initials="K." surname="Kompella" fullname="Kireeti Kompella">
         <organization>Juniper Networks</organization>
      </author>
      <date month="March" day="3" year="2025" />
      <abstract>
	 <t>   This document defines the MPLS Network Actions (MNA) sub-stack
   solution for carrying Network Actions and Ancillary Data in the 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.
   This solution document specifies In-stack network action and In-stack
   data specific requirements found in &quot;Requirements for MPLS Network
   Actions&quot;.  This document follows the architectural framework for the
   MNA technologies specified in &quot;MPLS Network Actions (MNA) Framework&quot;.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-mna-hdr-12" />
   
</reference>
