%% You should probably cite draft-ietf-mpls-mna-ps-hdr-19 instead of this revision.
@techreport{ietf-mpls-mna-ps-hdr-12,
    number =    {draft-ietf-mpls-mna-ps-hdr-12},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-mpls-mna-ps-hdr/12/},
    author =    {Jaganbabu Rajamanickam and Rakesh Gandhi and Royi Zigler and Jie Dong and Jisu Bhattacharya},
    title =     {{Post-Stack MPLS Network Action (MNA) Header Specification}},
    pagetotal = 27,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document specifies the Post-Stack MPLS Network Action (MNA) Header encoding and procedures for carrying Network Action encodings and Ancillary Data after the MPLS label stack, based on the MNA Sub- Stack including In-Stack Network Actions and Data specified in RFC 9994. 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 document follows the framework specified in RFC 9789. This document updates RFC 9994: the "Network Action Opcodes" registry fields, the Post-Stack MNA applicability of the opcodes, MNA scope, and Unknown action handling.},
}