<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-mna-ps-hdr" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-ps-hdr-04">
   <front>
      <title>Post-Stack MPLS Network Action (MNA) 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="T." surname="Li" fullname="Tony Li">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="November" day="20" year="2025" />
      <abstract>
	 <t>   This document defines the Post-Stack MPLS Network Action (MNA)
   solution for carrying Network Actions and Ancillary Data after the
   MPLS label stack, based on the In-Stack MNA solution defined in &quot;MPLS
   Network Action (MNA) Sub-Stack Solution.&quot;  MPLS Network Actions 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
   addresses the Post-Stack network action and Post-Stack data-specific
   requirements found in RFC 9613.  This document follows the framework
   specified in RFC 9789.

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