<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-teas-ns-ip-mpls" target="https://datatracker.ietf.org/doc/html/draft-ietf-teas-ns-ip-mpls-06">
   <front>
      <title>Realizing Network Slices in IP/MPLS Networks</title>
      <author initials="T." surname="Saad" fullname="Tarek Saad">
         <organization>Cisco Systems Inc.</organization>
      </author>
      <author initials="V. P." surname="Beeram" fullname="Vishnu Pavan Beeram">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="J. M." surname="Halpern" fullname="Joel M. Halpern">
         <organization>Ericsson</organization>
      </author>
      <author initials="S." surname="Peng" fullname="Shaofu Peng">
         <organization>ZTE Corporation</organization>
      </author>
      <date month="October" day="20" year="2025" />
      <abstract>
	 <t>   Realizing network slices may require the Service Provider to have the
   ability to partition a physical network into multiple logical
   networks of varying sizes, structures, and functions so that each
   slice can be dedicated to specific services or customers.  Multiple
   network slices can be realized on the same network while ensuring
   slice elasticity in terms of network resource allocation.  This
   document describes a scalable solution to realize network slicing in
   IP/MPLS networks by supporting multiple services on top of a single
   physical network by by requiring compliant domains and nodes to
   provide forwarding treatment (scheduling, drop policy, resource
   usage) based on slice identifiers.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-teas-ns-ip-mpls-06" />
   
</reference>
