<?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-02">
   <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="B." surname="Wen" fullname="Bin Wen">
         <organization>Comcast</organization>
      </author>
      <author initials="D." surname="Ceccarelli" fullname="Daniele Ceccarelli">
         <organization>Cisco Systems Inc.</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>
      <author initials="R." surname="Chen" fullname="Ran Chen">
         <organization>ZTE Corporation</organization>
      </author>
      <author initials="X." surname="Liu" fullname="Xufeng Liu">
         <organization>IBM Corporation</organization>
      </author>
      <author initials="L. M." surname="Contreras" fullname="Luis M. Contreras">
         <organization>Telefonica</organization>
      </author>
      <author initials="R." surname="Rokui" fullname="Reza Rokui">
         <organization>Ciena</organization>
      </author>
      <author initials="L." surname="Jalil" fullname="Luay Jalil">
         <organization>Verizon</organization>
      </author>
      <date month="March" day="13" year="2023" />
      <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 relying on compliant domains and nodes to provide
   forwarding treatment (scheduling, drop policy, resource usage) on to
   packets that carry identifiers that indicate the slicing service that
   is to be applied to the packets.

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