<?xml version='1.0' encoding='US-ASCII'?>

<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<rfc
      xmlns:xi="http://www.w3.org/2001/XInclude"
      category="std"
      docName="draft-liu-mpls-mna-sr-service-metadata-00"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">

 <!-- ***** FRONT MATTER ***** -->

 <front>

   <title abbrev="MNA for Metadata">MNA for Metadata in SR-MPLS Service Programming</title>
    <seriesInfo name="Internet-Draft" value="draft-liu-mpls-mna-sr-service-metadata-00"/>
   <author fullname="Yao Liu" surname="Liu">
      <organization>ZTE</organization>
      <address>
        <postal>
          <street/>
          <!-- Reorder these if your country does things differently -->
         <city>Nanjing</city>
          <region/>
          <code/>
          <country>China</country>
        </postal>
        <phone></phone>
        <email>liu.yao71@zte.com.cn</email>
        <!-- uri and facsimile elements may also be added -->
     </address>
    </author>
 
    <date year="2025"/>

   <!-- Meta-data Declarations -->

   <area>RTG</area>
    <workgroup>MPLS</workgroup>
    <!-- WG name at the upperleft corner of the doc,
        IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
        which is used by the RFC Editor as a nod to the history of the IETF. -->

   <keyword>MNA</keyword>
   <keyword>SR</keyword>
   <keyword>metadata</keyword>
    <!-- Keywords will be incorporated into HTML output
        files in a meta tag but they have no effect on text or nroff
        output. If you submit your draft to the RFC Editor, the
        keywords will be used for the search engine. -->

   <abstract>
      <t>This document defines MPLS Network Action(MNA) encoding to carry metadata in SR service programming with SR-MPLS data plane. </t>
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Introduction</name>
	  <t><xref target="I-D.ietf-spring-sr-service-programming"></xref> defines data plane functionality required to implement service segments and achieve service programming in SR-enabled MPLS and IPv6 networks. Metadata<xref target="RFC7665" format="default"></xref> provides contextual information about the data packets which traverse a programmed service path.</t>
	<t>However, there's yet no standard method to carry service metadata with the SR-MPLS data plane, which make the solution for service programming in SR-MPLS incomplete</t>
	<t>MPLS Network Action (MNA) <xref target="I-D.ietf-mpls-mna-fwk"></xref> is used to indicate action for Label Switched Paths (LSPs) and/or MPLS packets, and to transfer data needed for the action. <xref target="I-D.ietf-mpls-mna-hdr"></xref> defines the MNA sub-stack solution for carrying Network Action Indicators and Ancillary Data in the label stack.</t>
<t>This document defines MPLS Network Action(MNA) encoding to carry metadata in SR service programming with SR-MPLS data plane.</t>

	  </section>

<section numbered="true" toc="default">
        <name>Terminology</name>
		<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119" format="default"></xref> <xref target="RFC8174" format="default"></xref> when, and only when, they appear in all capitals, as shown here.</t>
      </section>

<section numbered="true" toc="default">
        <name>MNA ISD Encoding for Metadata in SR-MPLS Service Programming</name>
		<t>The metadata in SR-MPLS Service Programming is placed as part of the ISD block in an MPLS label stack according to the MNA encoding principles defined in <xref target="I-D.ietf-mpls-mna-hdr"></xref>. Two types of metadata for SR-MPLS service programming are defined: fixed-length service metadata and variable-length service metadata.</t>

<section numbered="true" toc="default">
        <name>Fixed-Length Service Metadata</name>
		
<t>The format of fixed-length service metadata is shown as follows,</t>		
		  <artwork align="center" name="Fixed-Length Service Metadata"><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               MNA Label               | TC  |S|    TTL        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opcode = TBA1 |   Servie Metadata     |R|IHS|S|U| NASL  | NAL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|                       Servie Metadata     |S|               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|                       Servie Metadata     |S|               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|                       Servie Metadata     |S|               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           ]]></artwork>	

<t>Where:</t>
		<ul spacing="normal">
        <li>The MNA Label is defined in <xref target="I-D.ietf-mpls-mna-hdr"></xref>.</li>
		<li>S: the Bottom of Stack field [RFC3032].</li>
		<li>Opcode: TBA1, indicating the fixed-length service metadata.</li>
		<li>R,IHS and U fields are set as specified in <xref target="I-D.ietf-mpls-mna-hdr"></xref>.</li>
		<li>NASL: The Network Action Sub-Stack Length (NASL) as specified in <xref target="I-D.ietf-mpls-mna-hdr"></xref>. The value is 3.</li>
		<li>NAL: Network Action Length as specified in <xref target="I-D.ietf-mpls-mna-hdr"></xref>. The number of extra LSEs used for servie metadata encoding. The value is 3.</li>
		<li>Opcode is MNA-IOAM-DEX opcode (value TBA2) to be assigned by IANA.</li>
		<li>Servie Metadata: 102-bit field to carry metadata</li>
		</ul>		   
		   
      </section>	
<section numbered="true" toc="default">
        <name>Variable-Length Service Metadata</name>
		
<t>The format of variable-length service metadata is shown as follows,</t>			
		  <artwork align="center" name="Variable-Length Service Metadata"><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               MNA Label               | TC  |S|    TTL        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opcode = TBA2 |   Servie Metadata     |R|IHS|S|U| NASL  | NAL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~1|                      Servie Metadata      |S|               ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           ]]></artwork>		

<t>Where:</t>
		<ul spacing="normal">
        <li>The MNA Label is defined in <xref target="I-D.ietf-mpls-mna-hdr"></xref>.</li>
		<li>S: the Bottom of Stack field [RFC3032].</li>
		<li>Opcode: TBA2, indicating the variable-length service metadata.</li>
		<li>R,IHS and U fields are set as specified in <xref target="I-D.ietf-mpls-mna-hdr"></xref>.</li>
		<li>NASL: The Network Action Sub-Stack Length (NASL) as specified in <xref target="I-D.ietf-mpls-mna-hdr"></xref>. </li>
		<li>NAL: Network Action Length as specified in <xref target="I-D.ietf-mpls-mna-hdr"></xref>. The number of extra LSEs used for servie metadata encoding.</li>
		<li>Servie Metadata: The field length depends on the value of NAL.</li>
		</ul>			   
		   
      </section>			
	
		
      </section>	

	
<section numbered="true" toc="default">
	<name>IANA Considerations</name>
		<t>IANA is requested to assign codepoints from its Network Action Opcodes registry (creation requested in <xref target="I-D.ietf-mpls-mna-hdr"></xref>) as specified in Table 1.

</t>
		
		  <artwork align="center" name=""><![CDATA[
     +------+--------------------------------+-------------+
     |Opcode|              Name              |  Reference  | 
     |      |                                |             |
     +------+--------------------------------+-------------+
     | TBA1 | In-Stack Network Action for    |This document|
     |      | Fixed-Length Servie Metadata   |             |
     +------+--------------------------------+-------------+
     | TBA2 | In-Stack Network Action for    |This document|
     |      | Variable-Length Servie Metadata|             |
     +------+--------------------------------+-------------+	  
           ]]></artwork>
	
	</section>




<section numbered="true" toc="default">
	<name>Security Considerations</name>
<t>Security considerations discussed in  <xref target="I-D.ietf-mpls-mna-fwk"></xref>, <xref target="I-D.ietf-mpls-mna-hdr"></xref> and <xref target="I-D.ietf-spring-sr-service-programming"></xref> apply to this document.</t>

</section>	


	
  </middle>
  <!--  *****BACK MATTER ***** -->

 <back>

   <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
		<?rfc include="reference.RFC.2119.xml"?>
		<?rfc include="reference.RFC.8174.xml"?>
		<?rfc include='reference.I-D.ietf-mpls-mna-fwk.xml'?>
		<?rfc include='reference.I-D.ietf-mpls-mna-hdr.xml'?>
		<?rfc include='reference.I-D.ietf-spring-sr-service-programming.xml'?>		
      </references>
      <references>
        <name>Informative References</name>
		<?rfc include="reference.RFC.7665.xml"?>
	
      </references>
    </references>


 </back>
</rfc>
