<?xml version='1.0'encoding='utf-8'?>encoding='UTF-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.27 (Ruby 3.3.6) --> <?rfc compact="yes"?> <?rfc comments="yes"?><rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-teas-5g-ns-ip-mpls-18" number="9889" updates="" obsoletes="" xml:lang="en" category="info" consensus="true" submissionType="IETF" tocDepth="2" tocInclude="true" sortRefs="true" symRefs="true" version="3"> <!--xml2rfc v2v3 conversion 3.28.1[rfced] We updated the abbreviated title (only appears in the running header in the PDF output) as follows to more closely align with the document title. Please let us know if you prefer otherwise. Original: Implementing 5G Transport Slices Updated: Realization of Network Slices for 5G Networks --> <!-- [rfced] This is a question for Luis. How would you like for your initials to appear in the first-page header? For now, we have updated to "L. Contreras" per the format used in the most recent documents you have authored, but we see that some documents use "LM. Contreras" in the first-page header. L. Contreras - RFCs 9543, 9439, 9013 LM. Contreras - RFCs 8597, 8568, 8432, 7161, 7028 --> <front> <titleabbrev="Implementingabbrev="Realization of Network Slices for 5GTransport Slices">A RealizationNetworks">Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies</title> <seriesInfoname="Internet-Draft" value="draft-ietf-teas-5g-ns-ip-mpls-18"/>name="RFC" value="9889"/> <author fullname="Krzysztof G. Szarkowicz" surname="Szarkowicz" initials="K." role="editor"> <organization>Juniper Networks</organization> <address> <postal> <city>Wien</city> <country>Austria</country> </postal> <email>kszarkowicz@juniper.net</email> </address> </author> <author fullname="Richard Roberts" surname="Roberts" initials="R" role="editor"> <organization>Juniper Networks</organization> <address> <postal> <city>Rennes</city> <country>France</country> </postal> <email>rroberts@juniper.net</email> </address> </author> <author fullname="JulianLucek">Lucek" surname="Lucek" initials="J"> <organization>Juniper Networks</organization> <address> <postal> <city>London</city> <country>United Kingdom</country> </postal> <email>jlucek@juniper.net</email> </address> </author> <author fullname="Mohamed Boucadair" surname="Boucadair" initials="M" role="editor"> <organization>Orange</organization> <address> <postal> <country>France</country> </postal> <email>mohamed.boucadair@orange.com</email> </address> </author> <author fullname="Luis M.Contreras">Contreras" surname="Contreras" initials="L."> <organization>Telefonica</organization> <address> <postal> <street>Ronda de la Comunicacion, s/n</street> <city>Madrid</city> <country>Spain</country> </postal> <email>luismiguel.contrerasmurillo@telefonica.com</email> <uri>https://lmcontreras.com/</uri> </address> </author> <date year="2025"month="April" day="03"/> <area>Routing</area> <workgroup>TEAS</workgroup>month="October"/> <area>RTG</area> <workgroup>teas</workgroup> <keyword>L3VPN</keyword> <keyword>L2VPN</keyword> <keyword>Slice Service</keyword> <!-- [rfced] How may we update these sentences to improve readability of "5G slicing connectivity service objectives" and "currently commonly"? Original: This document describes a Network Slice realization model for IP/MPLS networks with a focus on the Transport Network fulfilling 5G slicing connectivity service objectives. The realization model reuses many building blocks currently commonly used in service provider networks. Perhaps: This document describes a Network Slice realization model for IP/MPLS networks with a focus on the Transport Network fulfilling the connectivity service objectives for 5G slicing. The realization model reuses many building blocks commonly used in service provider networks at the current time. --> <abstract><?line 174?><t>Network slicing is a feature that was introduced by the 3rd Generation Partnership Project (3GPP) in mobile networks. Realization of 5G slicing implies requirements for all mobile domains, including the Radio Access Network (RAN), Core Network (CN), and Transport Network (TN).</t> <t>This document describes a Network Slice realization model for IP/MPLS networks with a focus on the Transport Network fulfilling the service objectives for 5G slicingconnectivity service objectives.connectivity. The realization model reuses many building blocks currently commonly used in service provider networks.</t> </abstract><note removeInRFC="true"> <name>Discussion Venues</name> <t>Discussion of this document takes place on the Traffic Engineering Architecture and Signaling Working Group mailing list (teas@ietf.org), which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/teas/"/>.</t> <t>Source for this draft and an issue tracker can be found at <eref target="https://github.com/boucadair/5g-slice-realization"/>.</t> </note></front> <middle><?line 181?><section anchor="introduction"> <name>Introduction</name> <t>This document focuses on network slicing for 5G networks, covering the connectivity between Network Functions (NFs) across multiple domains such as edge clouds, data centers, and the Wide Area Network (WAN). The document describes a Network Slice realization approach that fulfills 5G slicing requirements by using existing IP/MPLS technologies (at the time of publication of this document) to optimally control connectivity Service Level Agreements (SLAs) offered for 5G slices. To that aim, this document describes the scope of the Transport Network in 5G architectures (<xref target="sec-scope"/>), disambiguates 5G Network Slicing versus Transport Network Slicing (<xref target="sec-5gtn"/>), draws the perimeter of the various orchestration domains to realize slices (<xref target="sec-orch"/>), and identifies the required coordination between these orchestration domains for adequate setup of Attachment Circuits (ACs) (<xref target="sec-tn-nsi"/>).</t> <t>This work is compatible with the framework defined in <xreftarget="RFC9543"/>target="RFC9543"/>, which describes network slicing in the context of networks built from IETF technologies. Specifically, this document describes an approach to how RFC 9543 Network Slices are realized within provider networks and how such slices are stitched to Transport Network resources in a customer site in the context of Transport Network Slices (<xref target="fig-end-to-end"/>). The realization of an RFC 9543 Network Slice (i.e., connectivity with performance commitments) involves the provider network and partially the AC (thePE-sideProvider Edge (PE) side of the AC). This document assumes that the customer site infrastructure is over-provisioned and involves short distances (low latency) where basic QoS/scheduling logic is sufficient to comply with the Service Level Objectives (SLOs).</t> <figure anchor="fig-end-to-end"> <name>Transport Network Slice&and RFC 9543 Network Slice Scopes</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="320" width="520" viewBox="0 0 520 320" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,144 L 8,288" fill="none" stroke="black"/> <path d="M 24,208 L 24,240" fill="none" stroke="black"/> <path d="M 56,208 L 56,240" fill="none" stroke="black"/> <path d="M 88,208 L 88,240" fill="none" stroke="black"/> <path d="M 112,144 L 112,208" fill="none" stroke="black"/> <path d="M 112,240 L 112,288" fill="none" stroke="black"/> <path d="M 128,208 L 128,240" fill="none" stroke="black"/> <path d="M 184,80 L 184,128" fill="none" stroke="black"/> <path d="M 184,192 L 184,256" fill="none" stroke="black"/> <path d="M 200,144 L 200,192" fill="none" stroke="black"/> <path d="M 200,256 L 200,288" fill="none" stroke="black"/> <path d="M 208,96 L 208,136" fill="none" stroke="black"/> <path d="M 224,192 L 224,256" fill="none" stroke="black"/> <path d="M 312,192 L 312,256" fill="none" stroke="black"/> <path d="M 320,96 L 320,136" fill="none" stroke="black"/> <path d="M 328,144 L 328,192" fill="none" stroke="black"/> <path d="M 328,256 L 328,288" fill="none" stroke="black"/> <path d="M 344,80 L 344,128" fill="none" stroke="black"/> <path d="M 352,192 L 352,256" fill="none" stroke="black"/> <path d="M 392,208 L 392,240" fill="none" stroke="black"/> <path d="M 408,144 L 408,208" fill="none" stroke="black"/> <path d="M 408,240 L 408,288" fill="none" stroke="black"/> <path d="M 424,208 L 424,240" fill="none" stroke="black"/> <path d="M 512,144 L 512,288" fill="none" stroke="black"/> <path d="M 48,32 L 184,32" fill="none" stroke="black"/> <path d="M 256,32 L 392,32" fill="none" stroke="black"/> <path d="M 184,80 L 224,80" fill="none" stroke="black"/> <path d="M 312,80 L 344,80" fill="none" stroke="black"/> <path d="M 8,144 L 112,144" fill="none" stroke="black"/> <path d="M 200,144 L 328,144" fill="none" stroke="black"/> <path d="M 408,144 L 512,144" fill="none" stroke="black"/> <path d="M 184,192 L 224,192" fill="none" stroke="black"/> <path d="M 312,192 L 352,192" fill="none" stroke="black"/> <path d="M 24,208 L 56,208" fill="none" stroke="black"/> <path d="M 88,208 L 128,208" fill="none" stroke="black"/> <path d="M 392,208 L 424,208" fill="none" stroke="black"/> <path d="M 128,224 L 184,224" fill="none" stroke="black"/> <path d="M 352,224 L 392,224" fill="none" stroke="black"/> <path d="M 24,240 L 56,240" fill="none" stroke="black"/> <path d="M 88,240 L 128,240" fill="none" stroke="black"/> <path d="M 392,240 L 424,240" fill="none" stroke="black"/> <path d="M 184,256 L 224,256" fill="none" stroke="black"/> <path d="M 312,256 L 352,256" fill="none" stroke="black"/> <path d="M 8,288 L 112,288" fill="none" stroke="black"/> <path d="M 200,288 L 328,288" fill="none" stroke="black"/> <path d="M 408,288 L 512,288" fill="none" stroke="black"/> <polygon class="arrowhead" points="352,128 340,122.4 340,133.6" fill="black" transform="rotate(90,344,128)"/> <polygon class="arrowhead" points="328,136 316,130.4 316,141.6" fill="black" transform="rotate(90,320,136)"/> <polygon class="arrowhead" points="216,136 204,130.4 204,141.6" fill="black" transform="rotate(90,208,136)"/> <polygon class="arrowhead" points="192,128 180,122.4 180,133.6" fill="black" transform="rotate(90,184,128)"/> <g class="text"> <text x="40" y="36">|</text> <text x="196" y="36">TN</text> <text x="232" y="36">Slice</text> <text x="400" y="36">|</text> <text x="192" y="68">RFC</text> <text x="228" y="68">9543</text> <text x="280" y="68">Network</text> <text x="336" y="68">Slice</text> <text x="240" y="84">SDP</text> <text x="276" y="84">Type</text> <text x="304" y="84">3</text> <text x="216" y="100">-</text> <text x="240" y="100">SDP</text> <text x="276" y="100">Type</text> <text x="308" y="100">4-</text> <text x="60" y="164">Customer</text> <text x="268" y="164">Provider</text> <text x="460" y="164">Customer</text> <text x="52" y="180">Site</text> <text x="80" y="180">1</text> <text x="264" y="180">Network</text> <text x="452" y="180">Site</text> <text x="480" y="180">2</text> <text x="156" y="212">AC</text> <text x="372" y="212">AC</text> <text x="36" y="228">NF</text> <text x="72" y="228">...</text> <text x="108" y="228">CE</text> <text x="204" y="228">PE</text> <text x="332" y="228">PE</text> <text x="404" y="228">NF</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ |------------------TN Slice------------------| RFC 9543 Network Slice .-----SDP Type 3----. | .- SDP Type 4-. | | | | | v v v v +------------+ +---------------+ +------------+ | Customer | | Provider | | Customer | | Site 1 | | Network | | Site 2 | | | +-+--+ +-+--+ | | | +---+ +--+-+ AC | | | | AC +-+-+ | | |NF +...+ CE +------+ PE | | PE +----+NF | | | +---+ +--+-+ | | | | +-+-+ | | | +-+--+ +-+--+ | | | | | | | | +------------+ +---------------+ +------------+ ]]></artwork> </artset> </figure> <t>This document focuses onRFC9543RFC 9543 Network Slice deployments where the Service Demarcation Points (SDPs) are located per Types 3 and 4ofin Figure 1 of <xref target="RFC9543"/>.</t> <!-- [rfced] Section 1 of RFC 9543 notes the following: It is intended that the terms "IETF Network Slice" and "IETF Network Slice Service" be used only in this document. Other documents that need to indicate the type of network slice or network slice service described in this document can use the terms "RFC 9543 Network Slice" and "RFC 9543 Network Slice Service". Based on this, should "IETF Network Slice Service" and "IETF Network Slice" in the sentences below be updated to "RFC 9543 Network Slice Service" and "RFC 9543 Network Slice", respectively? Original: Mapping considerations between 3GPP and IETF Network Slice Service (e.g., mapping of service parameters) are discussed, e.g., in [I-D.ietf-teas-5g-network-slice-application]. ... Data Confidentiality and Integrity of an IETF Network Slice: As desc ribed in Section 5.1.2.1 of [RFC9543], the customer might request a Service Level Expectation (SLE) that mandates encryption. --> <!-- [rfced] We have a few questions about the sentence below (which is also mentioned in the question above). a) How may we revise "Mapping considerations between 3GPP and IETF Network Slice Service" to improve clarity? b) Is the second "e.g." needed? Original: Mapping considerations between 3GPP and IETF Network Slice Service (e.g., mapping of service parameters) are discussed, e.g., in [I-D.ietf-teas-5g-network-slice-application]. Perhaps: Considerations regarding the mapping between the 5G Network Slice Service and RFC 9543 Network Slice Service (e.g., mapping of service parameters) are discussed in [NS-APP]. --> <t>The realization approach described in this document is typically triggered by Network Slice Service requests. How a Network Slice Service request is placed for realization, including how it is derived from a 5G Slice Service request, is out of scope. Mapping considerations between 3GPP and IETF Network Slice Service (e.g., mapping of service parameters) are discussed, e.g., in <xref target="I-D.ietf-teas-5g-network-slice-application"/>.</t> <t>The 5G control plane uses the Single Network Slice Selection Assistance Information (S-NSSAI) for slice identification <xref target="TS-23.501"/>. Because S-NSSAIs are not visible to the transport domain, 5G domains can expose the 5G slices to the transport domain by mapping to explicit data plane identifiers (e.g., Layer 2, Layer 3, or Layer 4). Passing information between customer sites and provider networks is referred to as the"hand-off"."handoff". <xref target="sec-handoff-domains"/> lists a set ofhand-offhandoff methods for slice mapping purposes.</t> <t>Unlike approaches that require new protocol extensions (e.g., <xref target="I-D.ietf-teas-ns-ip-mpls"/>), the realization model described in this document uses a set of building blocks commonly used in service provider networks (at the time of publication of this document). The model uses (1)Layer 2 Virtual Private Network (L2VPN)L2VPN <xref target="RFC4664"/> and/orLayer 3 Virtual Private Network (L3VPN)L3VPN <xref target="RFC4364"/> service instances for logical separation, (2) fine-grained resource control at theProvider Edges (PEs),PEs, (3) coarse-grained resource control within the provider network, and (4) capacityplanning/management.planning and management. More details are provided in Sections <xref format="counter" target="sec-over-rea-model"/>, <xref format="counter" target="sec-qos-map"/>, <xref format="counter" target="transport-plane-mapping-models"/>, and <xref format="counter" target="sec-capacity-planning"/>.</t> <t>This realization model uses a single Network Resource Partition (NRP) (<xref section="7.1" sectionFormat="of" target="RFC9543"/>). The applicability to multiple NRPs is out of scope.</t> <t>Although this document focuses on 5G, the realizations are not fundamentally constrained by the 5G use case. The document is not intended to be a BCP and does not claim to specify mandatory mechanisms to realize network slices. Rather, a key goal of the document is to provide pragmatic implementation approaches by leveraging existingreadily-available, widely-deployed techniques.techniques that are readily available and widely deployed. The document is also intended to align the mobile and the IETF perspectives of slicing from a realization perspective.</t> <t>For a definitive description of 3GPP network architectures, the reader should refer to <xref target="TS-23.501"/>. More details can be found in <xref target="Book-5G"/>.</t> </section> <section anchor="terms"> <name>Terminology</name> <section anchor="definitions"> <name>Definitions</name> <t>The document uses the terms defined in <xref target="RFC9543"/>. Specifically, the use of "Customer" is consistent with <xref target="RFC9543"/> but with the following contextualization (see also <xref target="sec-ref-design"/>):</t> <dl> <dt>Customer:</dt> <dd> <t>An entity that is responsible for managing and orchestrating the end-to-end 5G Mobile Network, notably the Radio Access Network (RAN) and Core Network (CN).</t></dd> <dt/> <dd><t>This entity is distinct from the customer of a 5G Network Slice Service.</t> </dd> </dl> <t>This document makes use of the following terms:</t> <dl> <dt>Customer site:</dt> <dd> <t>A customer manages and deploys 5G NFs (e.g., gNodeB (gNB) and 5G Core (5GC)) in customer sites. A customer site can be either a physical or a virtual location. A provider is responsible for interconnecting customer sites.</t></dd> <dt/> <dd><t>Examples of customer sites are a customer private locations(Point(e.g., Point of Presence(PoP),(PoP) and Data Center (DC)), a Virtual Private Cloud (VPC), or servers hosted within the provider network or colocation service.</t> </dd> <dt>Resource Control:</dt> <dd> <t>In the context of this document, resource control is used mainly to refer to buffer management and relevant Quality of Service (QoS) functions.</t> </dd></dl> <t>"5G<dt>"5G Network Slicing"(orand "5G NetworkSlice") refersSlice":</dt> <dd>Refer to "Network Slicing"(orand "NetworkSlice")Slice" as defined inthe 3GPP<xreftarget="TS-28.530"/>.</t> <t>An extended listtarget="TS-28.530"/>.</dd> </dl> </section> <section anchor="ext-abbr"> <name>Abbreviations</name> <dl> <dt>3GPP:</dt> <dd> <t>3rd Generation Partnership Project</t> </dd> <dt>5GC:</dt> <dd> <t>5G Core</t> </dd> <dt>5QI:</dt> <dd> <t>5G QoS Indicator</t> </dd> <dt>A2A:</dt> <dd> <t>Any-to-Any</t> </dd> <dt>AC:</dt> <dd> <t>Attachment Circuit</t> </dd> <dt>CE:</dt> <dd> <t>Customer Edge</t> </dd> <dt>CIR:</dt> <dd> <t>Committed Information Rate</t> </dd> <dt>CS:</dt> <dd> <t>Customer Site</t> </dd> <dt>CN:</dt> <dd> <t>Core Network</t> </dd> <dt>CoS:</dt> <dd> <t>Class ofabbreviations used in this document is provided in <xref target="ext-abbr"/>.</t>Service</t> </dd> <dt>CP:</dt> <dd> <t>Control Plane</t> </dd> <dt>CU:</dt> <dd> <t>Centralized Unit</t> </dd> <dt>CU-CP:</dt> <dd> <t>Centralized Unit Control Plane</t> </dd> <dt>CU-UP:</dt> <dd> <t>Centralized Unit User Plane</t> </dd> <dt>DC:</dt> <dd> <t>Data Center</t> </dd> <dt>DDoS:</dt> <dd> <t>Distributed Denial of Service</t> </dd> <dt>DSCP:</dt> <dd> <t>Differentiated Services Code Point</t> </dd> <dt>eCPRI:</dt> <dd> <t>enhanced Common Public Radio Interface</t> </dd> <dt>FIB:</dt> <dd> <t>Forwarding Information Base</t> </dd> <dt>GPRS:</dt> <dd> <t>General Packet Radio Service</t> </dd> <dt>gNB:</dt> <dd> <t>gNodeB</t> </dd> <dt>GTP:</dt> <dd> <t>GPRS Tunneling Protocol</t> </dd> <dt>GTP-U:</dt> <dd> <t>GPRS Tunneling Protocol User Plane</t> </dd> <dt>IGP:</dt> <dd> <t>Interior Gateway Protocol</t> </dd> <dt>L2VPN:</dt> <dd> <t>Layer 2 Virtual Private Network</t> </dd> <dt>L3VPN:</dt> <dd> <t>Layer 3 Virtual Private Network</t> </dd> <dt>LSP:</dt> <dd> <t>Label Switched Path</t> </dd> <dt>MACsec:</dt> <dd>Media Access Control Security</dd> <dt>MIoT:</dt> <dd> <t>Massive Internet of Things</t> </dd> <dt>MNO:</dt> <dd>Mobile Network Operator</dd> <dt>MPLS:</dt> <dd> <t>Multiprotocol Label Switching</t> </dd> <dt>NF:</dt> <dd> <t>Network Function</t> </dd> <dt>NS:</dt> <dd> <t>Network Slice</t> </dd> <dt>NRP:</dt> <dd> <t>Network Resource Partition</t> </dd> <dt>NSC:</dt> <dd> <t>Network Slice Controller</t> </dd> <dt>PE:</dt> <dd> <t>Provider Edge</t> </dd> <dt>PIR:</dt> <dd> <t>Peak Information Rate</t> </dd> <dt>QoS:</dt> <dd> <t>Quality of Service</t> </dd> <dt>RAN:</dt> <dd> <t>Radio Access Network</t> </dd> <dt>RIB:</dt> <dd> <t>Routing Information Base</t> </dd> <dt>RSVP:</dt> <dd> <t>Resource Reservation Protocol</t> </dd> <dt>SD:</dt> <dd> <t>Slice Differentiator</t> </dd> <dt>SDP:</dt> <dd> <t>Service Demarcation Point</t> </dd> <dt>SLA:</dt> <dd> <t>Service Level Agreement</t> </dd> <dt>SLO:</dt> <dd> <t>Service Level Objective</t> </dd> <dt>S-NSSAI:</dt> <dd> <t>Single Network Slice Selection Assistance Information</t> </dd> <dt>SST:</dt> <dd> <t>Slice/Service Type</t> </dd> <dt>SR:</dt> <dd> <t>Segment Routing</t> </dd> <dt>SRv6:</dt> <dd> <t>Segment Routing version 6</t> </dd> <dt>TC:</dt> <dd> <t>Traffic Class</t> </dd> <dt>TE:</dt> <dd> <t>Traffic Engineering</t> </dd> <dt>TN:</dt> <dd> <t>Transport Network</t> </dd> <dt>UP:</dt> <dd> <t>User Plane</t> </dd> <dt>UPF:</dt> <dd> <t>User Plane Function</t> </dd> <dt>URLLC:</dt> <dd> <t>Ultra-Reliable Low-Latency Communication</t> </dd> <dt>VLAN:</dt> <dd> <t>Virtual Local Area Network</t> </dd> <dt>VPN:</dt> <dd> <t>Virtual Private Network</t> </dd> <dt>VRF:</dt> <dd> <t>Virtual Routing and Forwarding</t> </dd> <dt>VXLAN:</dt> <dd> <t>Virtual Extensible Local Area Network</t> </dd> </dl> </section> </section> <section anchor="sec-5g"> <name>5G Network Slicing Integration in Transport Networks</name> <section anchor="sec-scope"> <name>Scope of the Transport Network</name> <t>The main 5G network building blocksare:are the Radio Access Network (RAN), Core Network (CN), and Transport Network (TN). The Transport Network is defined by the 3GPPas (Sectionin Section 1 of <xreftarget="TS-28.530"/>):</t>target="TS-28.530"/>:</t> <blockquote> <t>part supporting connectivity within and between CN and RAN parts.</t> </blockquote><t>As discussed in Section 4.4.1 of <xref target="TS-28.530"/>, the<t>The 3GPP management system does not directly control the TransportNetwork:Network; it is consideredasa non-3GPP managedsystem.</t>system. This is discussed in Section 4.4.1 of <xref target="TS-28.530"/>:</t> <blockquote> <t>The non-3GPP part includes TN parts. The 3GPP management system provides the network slice requirements to the corresponding management systems of those non-3GPP parts, e.g. the TN part supports connectivity within and between CN and AN parts.</t> </blockquote> <t>In practice, the TN may not map to a monolithic architecture and management domain. It is frequently segmented, non-uniform, and managed by different entities. For example, <xref target="fig-1"/> depicts an NF instance that is deployed in an edge data center (DC) connected to an NF located in a Public Cloud via a WAN (e.g., MPLS-VPN service). In this example, the TN can be seen as an abstraction representing an end-to-end connectivity based upon three distinct domains: DC, WAN, and Public Cloud. A model for the Transport Network based on orchestration domains is introduced in <xref target="sec-orch"/>.</t> <figure anchor="fig-1"><name>An Example<name>Example of Transport Network Decomposition</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="368" width="400" viewBox="0 0 400 368" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,112 L 8,144" fill="none" stroke="black"/> <path d="M 8,192 L 8,352" fill="none" stroke="black"/> <path d="M 16,48 L 16,104" fill="none" stroke="black"/> <path d="M 24,224 L 24,240" fill="none" stroke="black"/> <path d="M 32,112 L 32,144" fill="none" stroke="black"/> <path d="M 56,32 L 56,64" fill="none" stroke="black"/> <path d="M 56,112 L 56,144" fill="none" stroke="black"/> <path d="M 64,224 L 64,240" fill="none" stroke="black"/> <path d="M 80,144 L 80,176" fill="none" stroke="black"/> <path d="M 88,224 L 88,240" fill="none" stroke="black"/> <path d="M 128,224 L 128,240" fill="none" stroke="black"/> <path d="M 152,192 L 152,352" fill="none" stroke="black"/> <path d="M 168,224 L 168,256" fill="none" stroke="black"/> <path d="M 168,288 L 168,320" fill="none" stroke="black"/> <path d="M 176,192 L 176,216" fill="none" stroke="black"/> <path d="M 176,264 L 176,280" fill="none" stroke="black"/> <path d="M 176,328 L 176,352" fill="none" stroke="black"/> <path d="M 192,224 L 192,256" fill="none" stroke="black"/> <path d="M 192,288 L 192,320" fill="none" stroke="black"/> <path d="M 208,144 L 208,176" fill="none" stroke="black"/> <path d="M 248,224 L 248,256" fill="none" stroke="black"/> <path d="M 248,288 L 248,320" fill="none" stroke="black"/> <path d="M 264,192 L 264,216" fill="none" stroke="black"/> <path d="M 264,264 L 264,280" fill="none" stroke="black"/> <path d="M 264,328 L 264,352" fill="none" stroke="black"/> <path d="M 272,224 L 272,256" fill="none" stroke="black"/> <path d="M 272,288 L 272,320" fill="none" stroke="black"/> <path d="M 288,224 L 288,256" fill="none" stroke="black"/> <path d="M 296,192 L 296,216" fill="none" stroke="black"/> <path d="M 296,264 L 296,352" fill="none" stroke="black"/> <path d="M 312,144 L 312,176" fill="none" stroke="black"/> <path d="M 312,224 L 312,256" fill="none" stroke="black"/> <path d="M 336,32 L 336,64" fill="none" stroke="black"/> <path d="M 336,112 L 336,144" fill="none" stroke="black"/> <path d="M 360,112 L 360,144" fill="none" stroke="black"/> <path d="M 368,192 L 368,352" fill="none" stroke="black"/> <path d="M 376,48 L 376,104" fill="none" stroke="black"/> <path d="M 384,112 L 384,144" fill="none" stroke="black"/> <path d="M 56,32 L 336,32" fill="none" stroke="black"/> <path d="M 16,48 L 56,48" fill="none" stroke="black"/> <path d="M 336,48 L 376,48" fill="none" stroke="black"/> <path d="M 56,64 L 336,64" fill="none" stroke="black"/> <path d="M 8,112 L 32,112" fill="none" stroke="black"/> <path d="M 56,112 L 336,112" fill="none" stroke="black"/> <path d="M 360,112 L 384,112" fill="none" stroke="black"/> <path d="M 32,128 L 56,128" fill="none" stroke="black"/> <path d="M 336,128 L 360,128" fill="none" stroke="black"/> <path d="M 8,144 L 32,144" fill="none" stroke="black"/> <path d="M 56,144 L 336,144" fill="none" stroke="black"/> <path d="M 360,144 L 384,144" fill="none" stroke="black"/> <path d="M 8,192 L 24,192" fill="none" stroke="black"/> <path d="M 136,192 L 152,192" fill="none" stroke="black"/> <path d="M 24,224 L 64,224" fill="none" stroke="black"/> <path d="M 88,224 L 128,224" fill="none" stroke="black"/> <path d="M 168,224 L 192,224" fill="none" stroke="black"/> <path d="M 248,224 L 272,224" fill="none" stroke="black"/> <path d="M 288,224 L 312,224" fill="none" stroke="black"/> <path d="M 24,240 L 64,240" fill="none" stroke="black"/> <path d="M 88,240 L 128,240" fill="none" stroke="black"/> <path d="M 168,256 L 192,256" fill="none" stroke="black"/> <path d="M 248,256 L 272,256" fill="none" stroke="black"/> <path d="M 288,256 L 312,256" fill="none" stroke="black"/> <path d="M 168,288 L 192,288" fill="none" stroke="black"/> <path d="M 248,288 L 272,288" fill="none" stroke="black"/> <path d="M 168,320 L 192,320" fill="none" stroke="black"/> <path d="M 248,320 L 272,320" fill="none" stroke="black"/> <path d="M 8,352 L 152,352" fill="none" stroke="black"/> <path d="M 176,352 L 264,352" fill="none" stroke="black"/> <path d="M 296,352 L 368,352" fill="none" stroke="black"/> <polygon class="arrowhead" points="384,104 372,98.4 372,109.6" fill="black" transform="rotate(90,376,104)"/> <polygon class="arrowhead" points="320,176 308,170.4 308,181.6" fill="black" transform="rotate(90,312,176)"/> <polygon class="arrowhead" points="216,176 204,170.4 204,181.6" fill="black" transform="rotate(90,208,176)"/> <polygon class="arrowhead" points="88,176 76,170.4 76,181.6" fill="black" transform="rotate(90,80,176)"/> <polygon class="arrowhead" points="24,104 12,98.4 12,109.6" fill="black" transform="rotate(90,16,104)"/> <g class="text"> <text x="116" y="52">5G</text> <text x="144" y="52">RAN</text> <text x="172" y="52">or</text> <text x="204" y="52">Core</text> <text x="256" y="52">Network</text> <text x="20" y="132">NF</text> <text x="160" y="132">Transport</text> <text x="232" y="132">Network</text> <text x="372" y="132">NF</text> <text x="52" y="196">Data</text> <text x="100" y="196">Center</text> <text x="200" y="196">-MPLS</text> <text x="244" y="196">VPN-</text> <text x="332" y="196">-Public-</text> <text x="220" y="212">Backbone</text> <text x="336" y="212">Cloud</text> <text x="180" y="244">PE</text> <text x="260" y="244">PE</text> <text x="300" y="244">GW</text> <text x="32" y="260">.-.</text> <text x="64" y="260">.-.</text> <text x="96" y="260">.-.</text> <text x="128" y="260">.-.</text> <text x="32" y="276">'-'</text> <text x="64" y="276">'-'</text> <text x="96" y="276">'-'</text> <text x="128" y="276">'-'</text> <text x="180" y="308">PE</text> <text x="260" y="308">PE</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +----------------------------------+ +----+ 5G RAN or Core Network +----+ | +----------------------------------+ | | | v v +--+ +----------------------------------+ +--+ |NF+--+ Transport Network +--+NF| +--+ +--+---------------+------------+--+ +--+ | | | v v v +-- Data Center --+ +-MPLS VPN-+ +-Public-+ | | | Backbone | | Cloud | | +----+ +----+ | +--+ +--+ +--+ | | '----' '----' | |PE| |PE| |GW| | | .-. .-. .-. .-. | +--+ +--+ +--+ | | '-' '-' '-' '-' | | | | | | | +--+ +--+ | | | | |PE| |PE| | | | | +--+ +--+ | | | | | | | | +-----------------+ +----------+ +--------+ ]]></artwork> </artset> </figure> </section> <section anchor="sec-5gtn"> <name>5G Network SlicingversusVersus Transport Network Slicing</name> <t>Network slicing has a different meaning in the 3GPP mobile world and transport world. This difference can be seen from the descriptions below that set out the objectives of 5G Network Slicing (<xref target="sec-5g-slicing"/>) and Transport Network Slicing (<xref target="sec-tn-slicing"/>). These descriptions are not intended to be exhaustive.</t> <section anchor="sec-5g-slicing"> <name>5G Network Slicing</name><t>5G Network Slicing is defined by<t>In <xref target="TS-28.530"/>, the 3GPP<xref target="TS-28.530"/>defines 5G Network Slicing as an approach:</t> <blockquote> <t>where logical networks/partitions are created, with appropriate isolation, resources and optimized topology to serve a purpose or service category (e.g. use case/traffic category, or for MNO internal reasons) or customers (logical system created "on demand").</t> </blockquote> <t>These resources are from the TN, RAN, CN domains, and the underlying infrastructure.</t> <t>Section 3.1 of <xref target="TS-28.530"/> defines a 5G Network Slice as:</t> <blockquote> <t>a logical network that provides specific network capabilities and network characteristics, supporting various service properties for network slice customers.</t> </blockquote> </section> <section anchor="sec-tn-slicing"> <name>Transport Network Slicing</name> <t>The term "TN slice" refers to a slice in the Transport Network domain of the 5G architecture.The following furtherThis section elaborates on how Transport Network Slicing is defined in the context of this document. It draws on the 3GPP definitions ofTransport Network"Transport Network" andNetwork Slicing as described"Network Slicing" in <xref target="TS-28.530"/>.</t> <t>The objective of Transport Network Slicing is to isolate, guarantee, or prioritize Transport Network resources for Slice Services. Examples of such resourcesare:include buffers, link capacity, or even Routing Information Base (RIB) and Forwarding Information Base (FIB).</t> <t>Transport Network Slicing provides various degrees of sharing of resources between slices (<xref section="8" sectionFormat="of" target="RFC9543"/>). For example, the network capacity can be shared by all slices, usually with a guaranteed minimum per slice, or each individual slice can be allocated dedicated network capacity. Parts of a given network may use the former, while others use the latter. For example, in order to satisfy local engineering guidelines and specific service requirements, shared TN resources could be provided in the backhaul (or midhaul), and dedicated TN resources could be provided in the midhaul (or backhaul). The capacity partitioning strategy is deployment specific.</t> <t>There are different components to implement TN slices based upon mechanisms such as Virtual Routing and Forwarding (VRF) instances(VRFs)for logical separation, QoS, and Traffic Engineering (TE). Whether all or a subset of these components are enabled is a deployment choice.</t> </section> </section> <section anchor="sec-ref-design"> <name>Transport Network Reference Design</name> <t><xref target="fig-tn-arch"/> depicts the reference design used in this document for modeling the Transport Network based on management perimeters(Customer(customer vs.Provider).</t>provider).</t> <figure anchor="fig-tn-arch"> <name>Reference Design with Customer Site and Provider Network</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="288" width="600" viewBox="0 0 600 288" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,96 L 8,240" fill="none" stroke="black"/> <path d="M 24,160 L 24,192" fill="none" stroke="black"/> <path d="M 48,160 L 48,192" fill="none" stroke="black"/> <path d="M 88,144 L 88,208" fill="none" stroke="black"/> <path d="M 128,144 L 128,208" fill="none" stroke="black"/> <path d="M 144,96 L 144,168" fill="none" stroke="black"/> <path d="M 144,184 L 144,240" fill="none" stroke="black"/> <path d="M 200,96 L 200,168" fill="none" stroke="black"/> <path d="M 200,184 L 200,240" fill="none" stroke="black"/> <path d="M 216,144 L 216,208" fill="none" stroke="black"/> <path d="M 256,144 L 256,208" fill="none" stroke="black"/> <path d="M 320,144 L 320,208" fill="none" stroke="black"/> <path d="M 360,144 L 360,208" fill="none" stroke="black"/> <path d="M 376,96 L 376,168" fill="none" stroke="black"/> <path d="M 376,184 L 376,240" fill="none" stroke="black"/> <path d="M 440,96 L 440,168" fill="none" stroke="black"/> <path d="M 440,184 L 440,240" fill="none" stroke="black"/> <path d="M 456,144 L 456,208" fill="none" stroke="black"/> <path d="M 496,144 L 496,208" fill="none" stroke="black"/> <path d="M 576,96 L 576,240" fill="none" stroke="black"/> <path d="M 8,96 L 144,96" fill="none" stroke="black"/> <path d="M 200,96 L 376,96" fill="none" stroke="black"/> <path d="M 440,96 L 576,96" fill="none" stroke="black"/> <path d="M 88,144 L 128,144" fill="none" stroke="black"/> <path d="M 216,144 L 256,144" fill="none" stroke="black"/> <path d="M 320,144 L 360,144" fill="none" stroke="black"/> <path d="M 456,144 L 496,144" fill="none" stroke="black"/> <path d="M 24,160 L 48,160" fill="none" stroke="black"/> <path d="M 128,176 L 216,176" fill="none" stroke="black"/> <path d="M 360,176 L 456,176" fill="none" stroke="black"/> <path d="M 24,192 L 48,192" fill="none" stroke="black"/> <path d="M 88,208 L 128,208" fill="none" stroke="black"/> <path d="M 216,208 L 256,208" fill="none" stroke="black"/> <path d="M 320,208 L 360,208" fill="none" stroke="black"/> <path d="M 456,208 L 496,208" fill="none" stroke="black"/> <path d="M 8,240 L 144,240" fill="none" stroke="black"/> <path d="M 200,240 L 376,240" fill="none" stroke="black"/> <path d="M 440,240 L 576,240" fill="none" stroke="black"/> <path d="M 48,272 L 184,272" fill="none" stroke="black"/> <path d="M 328,272 L 448,272" fill="none" stroke="black"/> <polygon class="arrowhead" points="456,272 444,266.4 444,277.6" fill="black" transform="rotate(0,448,272)"/> <polygon class="arrowhead" points="56,272 44,266.4 44,277.6" fill="black" transform="rotate(180,48,272)"/> <g class="text"> <text x="84" y="36">Customer</text> <text x="284" y="36">Provider</text> <text x="516" y="36">Customer</text> <text x="80" y="52">Orchestration</text> <text x="280" y="52">Orchestration</text> <text x="520" y="52">Orchestration</text> <text x="76" y="68">Domain</text> <text x="276" y="68">Domain</text> <text x="508" y="68">Domain</text> <text x="76" y="116">Customer</text> <text x="252" y="116">Provider</text> <text x="320" y="116">Network</text> <text x="508" y="116">Customer</text> <text x="76" y="132">Site</text> <text x="104" y="132">1</text> <text x="508" y="132">Site</text> <text x="536" y="132">2</text> <text x="172" y="164">AC</text> <text x="404" y="164">AC</text> <text x="36" y="180">NF</text> <text x="68" y="180">....</text> <text x="108" y="180">CE</text> <text x="236" y="180">PE</text> <text x="340" y="180">PE</text> <text x="476" y="180">NF</text> <text x="476" y="228">(CE)</text> <text x="224" y="276">Transport</text> <text x="296" y="276">Network</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ Customer Provider Customer Orchestration Orchestration Orchestration Domain Domain Domain +----------------+ +---------------------+ +----------------+ | Customer | | Provider Network | | Customer | | Site 1 | | | | Site 2 | | +----+ | | +----+ +----+ | | +----+ | | +--+ | | | AC | | | | | | AC | | | | | |NF|....| CE +----------+ PE | | PE +-----------+ NF | | | +--+ | | | | | | | | | | | | | | +----+ | | +----+ +----+ | | +----+ | | | | | | (CE) | +----------------+ +---------------------+ +----------------+ <-----------------Transport Network---------------> ]]></artwork> </artset> </figure> <t>The description of the main components shown in <xref target="fig-tn-arch"/> is provided in the following subsections.</t> <section anchor="sec-cs"> <name>Customer Site (CS)</name> <t>On top of 5G NFs, a customer may manage additional TN elements (e.g., servers, routers, and switches) within a customer site.</t> <t>NFs may be hosted on a CE, directly connected to a CE, orbelocated multiple IP hops from a CE.</t> <t>In some contexts, the connectivity between NFs that belong to the same site can beviaachieved via the provider network.</t> <t>The orchestration of the TN within a customer site involves a set of controllers for automation purposes (e.g., NetworkFunctionsFunction Virtualization Infrastructure (NFVI), Container Network Interface (CNI), Fabric Managers, or Public Cloud APIs).It is out of scope to documentDocumenting how these controllers areimplemented.</t>implemented is out of scope for this document.</t> </section> <section anchor="sec-ce"> <name>Customer Edge (CE)</name> <t>A CE is a function that provides logical connectivity of a customer site (<xref target="sec-cs"/>) to the provider network (<xref target="sec-pn"/>). The logical connectivity is enforced at Layer 2 and/or Layer 3 and is denominated an Attachment Circuit (AC) (<xref target="sec-ac"/>). Examples of CEs include TN components (e.g., router, switch, and firewalls) and also 5G NFs (i.e., an element of the 5G domain such as Centralized Unit (CU), Distributed Unit (DU), or User Plane Function (UPF)).</t> <t>A CE is typically managed by the customer, but it can also be co-managed with the provider. A co-managed CE is orchestrated by both the customer and the provider. In this case, the customer and provider usually have control on distinct device configuration perimeters. A co-managed CE has both PE and CEfunctionsfunctions, and there is no strict AC connection, although one may consider that the AC stitching logic happens internally within the CE itself. The provider manages the AC between the CE and the PE.</t> <t>This document generalizes the definition of a CE with the introduction of"Distributed"distributed CE"; that is, the logical connectivity is realized by configuring multiple devices in the customer domain. The CE function is distributed. An example of distributed CE is the realization of an interconnection usingaan L3VPN service based on a distributed CE composed of a switch (Layer 2) and a router (Layer 3) (<xref target="fig-distribute-ce"/>). Another example of distributed CE is shown in <xref target="fig-50"/>.</t> <!-- [rfced] Figure 4 contains "SW" and "RTR", which are not used elsewhere in the document. We believe these stand for "switch" and "router", respectively. May we update this sentence in one of the following ways to make this clear? Original: An example of distributed CE is the realization of an interconnection using a L3VPN service based on a distributed CE composed of a switch (Layer 2) and a router (Layer 3) (Figure 4). Perhaps: An example of distributed CE is the realization of an interconnection using an L3VPN service based on a distributed CE composed of a switch (SW) in Layer 2 and a router (RTR) in Layer 3, as shown in Figure 4. Or: An example of distributed CE is the realization of an interconnection using an L3VPN service based on a distributed CE composed of a switch (Layer 2) and a router (Layer 3); see SW and RTR in Figure 4. --> <figure anchor="fig-distribute-ce"> <name>Example of Distributed CE</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="256" width="424" viewBox="0 0 424 256" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,240" fill="none" stroke="black"/> <path d="M 24,80 L 24,208" fill="none" stroke="black"/> <path d="M 40,112 L 40,176" fill="none" stroke="black"/> <path d="M 72,112 L 72,176" fill="none" stroke="black"/> <path d="M 96,112 L 96,136" fill="none" stroke="black"/> <path d="M 96,152 L 96,176" fill="none" stroke="black"/> <path d="M 128,32 L 128,72" fill="none" stroke="black"/> <path d="M 128,224 L 128,240" fill="none" stroke="black"/> <path d="M 152,80 L 152,112" fill="none" stroke="black"/> <path d="M 152,176 L 152,208" fill="none" stroke="black"/> <path d="M 296,32 L 296,104" fill="none" stroke="black"/> <path d="M 296,184 L 296,240" fill="none" stroke="black"/> <path d="M 312,112 L 312,176" fill="none" stroke="black"/> <path d="M 416,32 L 416,240" fill="none" stroke="black"/> <path d="M 8,32 L 128,32" fill="none" stroke="black"/> <path d="M 296,32 L 416,32" fill="none" stroke="black"/> <path d="M 24,80 L 152,80" fill="none" stroke="black"/> <path d="M 40,112 L 72,112" fill="none" stroke="black"/> <path d="M 96,112 L 136,112" fill="none" stroke="black"/> <path d="M 272,112 L 312,112" fill="none" stroke="black"/> <path d="M 136,126 L 272,126" fill="none" stroke="black"/> <path d="M 136,130 L 272,130" fill="none" stroke="black"/> <path d="M 72,144 L 168,144" fill="none" stroke="black"/> <path d="M 192,144 L 272,144" fill="none" stroke="black"/> <path d="M 136,158 L 272,158" fill="none" stroke="black"/> <path d="M 136,162 L 272,162" fill="none" stroke="black"/> <path d="M 40,176 L 72,176" fill="none" stroke="black"/> <path d="M 96,176 L 136,176" fill="none" stroke="black"/> <path d="M 272,176 L 312,176" fill="none" stroke="black"/> <path d="M 24,208 L 40,208" fill="none" stroke="black"/> <path d="M 136,208 L 152,208" fill="none" stroke="black"/> <path d="M 8,240 L 128,240" fill="none" stroke="black"/> <path d="M 296,240 L 416,240" fill="none" stroke="black"/> <g class="text"> <text x="68" y="52">Customer</text> <text x="356" y="52">Provider</text> <text x="68" y="68">Site</text> <text x="360" y="68">Network</text> <text x="180" y="148">AC</text> <text x="292" y="148">PE</text> <text x="56" y="164">RTR</text> <text x="116" y="164">SW</text> <text x="88" y="212">Distributed</text> <text x="76" y="228">CE</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +--------------+ +--------------+ | Customer | | Provider | | Site | | Network | | +---------------+ | | | | | | | | | +---+ +----+ | +----+ | | | | | | ================== | | | | | +------------AC----------+ PE | | | | |RTR| | SW ================== | | | | +---+ +----+ | +----+ | | | | | | | +--Distributed--+ | | | CE | | | +--------------+ +--------------+ ]]></artwork> </artset> </figure><t>While in<t>In mostcasescases, CEs connect to PEs using IP (e.g., via Layer 3 VLAN subinterfaces), but a CE may also connect to the provider network using other technologies such as MPLS-potentially(potentially over IPtunnels-tunnels) or Segment Routing over IPv6 (SRv6) <xref target="RFC8986"/>.TheThus, the CE hasthusawareness of providerservicesservice configuration (e.g., control plane identifiers such as Route Targets (RTs) and Route Distinguishers (RDs)). However, the CE is still managed by thecustomercustomer, and the AC is based on MPLS or SRv6 data plane technologies. The complete termination of the AC within the provider network may happen on distinctrouters:routers; this is another example of distributed PE. Service-aware CEs are used, for example, in the deployments discussed in Sections <xref format="counter" target="sec-10b"/> and <xref format="counter" target="sec-10c"/>.</t> </section> <section anchor="sec-pn"> <name>Provider Network</name> <t>A provider uses a provider network to interconnect customer sites. This document assumes that the provider network is based on IP, MPLS, or both.</t> </section> <section anchor="sec-pe"> <name>Provider Edge (PE)</name><t>PE<t>A PE is a device managed by a provider that is connected to a CE. The connectivity between a CE and a PE is achieved using one or multiple ACs (<xref target="sec-ac"/>).</t> <t>This document generalizes the PE definition with the introduction of"Distributed"distributed PE"; that is, the logical connectivity is realized by configuring multiple devices in the provider network (i.e., the provider orchestration domain). The PE function is distributed.</t> <t>An example of a distributed PE is the"Managed"managed CE service". For example, a provider delivers VPN services using CEs and PEswhichthat are both managed by the provider(case(example (i) in <xref target="fig-50"/>). The managed CE can also be a Data Center Gateway as depicted intheexample (ii) of <xref target="fig-50"/>. A provider-managed CE may attach to CEs of multiple customers. However, this device is part of the provider network.</t> <figure anchor="fig-50"> <name>Examples of Distributed PE</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="480" width="424" viewBox="0 0 424 480" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,208" fill="none" stroke="black"/> <path d="M 8,256 L 8,448" fill="none" stroke="black"/> <path d="M 32,304 L 32,400" fill="none" stroke="black"/> <path d="M 56,336 L 56,352" fill="none" stroke="black"/> <path d="M 96,96 L 96,160" fill="none" stroke="black"/> <path d="M 96,336 L 96,352" fill="none" stroke="black"/> <path d="M 112,336 L 112,352" fill="none" stroke="black"/> <path d="M 128,32 L 128,88" fill="none" stroke="black"/> <path d="M 128,168 L 128,208" fill="none" stroke="black"/> <path d="M 128,256 L 128,296" fill="none" stroke="black"/> <path d="M 128,416 L 128,448" fill="none" stroke="black"/> <path d="M 152,336 L 152,352" fill="none" stroke="black"/> <path d="M 176,304 L 176,320" fill="none" stroke="black"/> <path d="M 176,384 L 176,400" fill="none" stroke="black"/> <path d="M 256,80 L 256,96" fill="none" stroke="black"/> <path d="M 256,160 L 256,176" fill="none" stroke="black"/> <path d="M 256,304 L 256,320" fill="none" stroke="black"/> <path d="M 256,384 L 256,400" fill="none" stroke="black"/> <path d="M 296,32 L 296,72" fill="none" stroke="black"/> <path d="M 296,192 L 296,208" fill="none" stroke="black"/> <path d="M 296,256 L 296,296" fill="none" stroke="black"/> <path d="M 296,416 L 296,448" fill="none" stroke="black"/> <path d="M 312,96 L 312,160" fill="none" stroke="black"/> <path d="M 312,320 L 312,384" fill="none" stroke="black"/> <path d="M 344,96 L 344,160" fill="none" stroke="black"/> <path d="M 344,320 L 344,384" fill="none" stroke="black"/> <path d="M 384,96 L 384,160" fill="none" stroke="black"/> <path d="M 384,320 L 384,384" fill="none" stroke="black"/> <path d="M 400,80 L 400,176" fill="none" stroke="black"/> <path d="M 400,304 L 400,400" fill="none" stroke="black"/> <path d="M 416,32 L 416,208" fill="none" stroke="black"/> <path d="M 416,256 L 416,448" fill="none" stroke="black"/> <path d="M 8,32 L 128,32" fill="none" stroke="black"/> <path d="M 296,32 L 416,32" fill="none" stroke="black"/> <path d="M 256,80 L 400,80" fill="none" stroke="black"/> <path d="M 96,96 L 136,96" fill="none" stroke="black"/> <path d="M 272,96 L 312,96" fill="none" stroke="black"/> <path d="M 344,96 L 384,96" fill="none" stroke="black"/> <path d="M 136,110 L 272,110" fill="none" stroke="black"/> <path d="M 136,114 L 272,114" fill="none" stroke="black"/> <path d="M 136,128 L 200,128" fill="none" stroke="black"/> <path d="M 224,128 L 272,128" fill="none" stroke="black"/> <path d="M 312,128 L 344,128" fill="none" stroke="black"/> <path d="M 136,142 L 272,142" fill="none" stroke="black"/> <path d="M 136,146 L 272,146" fill="none" stroke="black"/> <path d="M 96,160 L 136,160" fill="none" stroke="black"/> <path d="M 272,160 L 312,160" fill="none" stroke="black"/> <path d="M 344,160 L 384,160" fill="none" stroke="black"/> <path d="M 256,176 L 280,176" fill="none" stroke="black"/> <path d="M 376,176 L 400,176" fill="none" stroke="black"/> <path d="M 8,208 L 128,208" fill="none" stroke="black"/> <path d="M 296,208 L 416,208" fill="none" stroke="black"/> <path d="M 8,256 L 128,256" fill="none" stroke="black"/> <path d="M 296,256 L 416,256" fill="none" stroke="black"/> <path d="M 32,304 L 176,304" fill="none" stroke="black"/> <path d="M 256,304 L 400,304" fill="none" stroke="black"/> <path d="M 272,320 L 312,320" fill="none" stroke="black"/> <path d="M 344,320 L 384,320" fill="none" stroke="black"/> <path d="M 56,336 L 96,336" fill="none" stroke="black"/> <path d="M 112,336 L 152,336" fill="none" stroke="black"/> <path d="M 176,334 L 272,334" fill="none" stroke="black"/> <path d="M 176,338 L 272,338" fill="none" stroke="black"/> <path d="M 56,352 L 96,352" fill="none" stroke="black"/> <path d="M 112,352 L 152,352" fill="none" stroke="black"/> <path d="M 176,352 L 216,352" fill="none" stroke="black"/> <path d="M 240,352 L 272,352" fill="none" stroke="black"/> <path d="M 312,352 L 344,352" fill="none" stroke="black"/> <path d="M 176,366 L 272,366" fill="none" stroke="black"/> <path d="M 176,370 L 272,370" fill="none" stroke="black"/> <path d="M 272,384 L 312,384" fill="none" stroke="black"/> <path d="M 344,384 L 384,384" fill="none" stroke="black"/> <path d="M 32,400 L 56,400" fill="none" stroke="black"/> <path d="M 152,400 L 176,400" fill="none" stroke="black"/> <path d="M 256,400 L 280,400" fill="none" stroke="black"/> <path d="M 376,400 L 400,400" fill="none" stroke="black"/> <path d="M 8,448 L 24,448" fill="none" stroke="black"/> <path d="M 296,448 L 416,448" fill="none" stroke="black"/> <g class="text"> <text x="68" y="52">Customer</text> <text x="356" y="52">Provider</text> <text x="68" y="68">Site</text> <text x="360" y="68">Network</text> <text x="292" y="116">Mngd</text> <text x="116" y="132">CE</text> <text x="212" y="132">AC</text> <text x="292" y="132">CE</text> <text x="364" y="132">PE</text> <text x="328" y="180">Distributed</text> <text x="324" y="196">PE</text> <text x="160" y="228">(i)</text> <text x="224" y="228">Distributed</text> <text x="284" y="228">PE</text> <text x="68" y="276">Customer</text> <text x="356" y="276">Provider</text> <text x="68" y="292">Site</text> <text x="360" y="292">Network</text> <text x="76" y="324">IP</text> <text x="116" y="324">Fabric</text> <text x="292" y="340">DC</text> <text x="228" y="356">AC</text> <text x="292" y="356">GW</text> <text x="364" y="356">PE</text> <text x="56" y="372">.-.</text> <text x="88" y="372">.-.</text> <text x="120" y="372">.-.</text> <text x="152" y="372">.-.</text> <text x="56" y="388">'-'</text> <text x="88" y="388">'-'</text> <text x="120" y="388">'-'</text> <text x="152" y="388">'-'</text> <text x="104" y="404">Distributed</text> <text x="328" y="404">Distributed</text> <text x="100" y="420">CE</text> <text x="324" y="420">PE</text> <text x="44" y="452">Data</text> <text x="96" y="452">Center-</text> <text x="132" y="468">(ii)</text> <text x="200" y="468">Distributed</text> <text x="260" y="468">PE</text> <text x="288" y="468">and</text> <text x="316" y="468">CE</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +--------------+ +--------------+ | Customer | | Provider | | Site | | Network | | | +-----------------+ | | +----+ | +----+ +----+ | | | | ==================Mngd| | | | | | | CE +--------AC------+ CE +---+ PE | | | | | ================== | | | | | | +----+ | +----+ +----+ | | | | +---Distributed---+ | | | | PE | +--------------+ +--------------+ (i) Distributed PE +--------------+ +--------------+ | Customer | | Provider | | Site | | Network | | +-----------------+ +-----------------+ | | | IP Fabric | | +----+ +----+ | | | | +----+ +----+ ============= DC | | | | | | | '----' '----' +-----AC----+ GW +---+ PE | | | | | .-. .-. .-. .-. ============= | | | | | | | '-' '-' '-' '-' | | +----+ +----+ | | | +---Distributed---+ +---Distributed---+ | | CE | | PE | | | | | +--Data Center-+ +--------------+ (ii) Distributed PE and CE ]]></artwork> </artset> </figure> <t>In subsequent sections of this document, the termsCE"CE" andPE"PE" are used for both single and distributed devices.</t> </section> <section anchor="sec-ac"> <name>Attachment Circuit (AC)</name> <t>The AC is the logical connection that attaches a CE (<xref target="sec-ce"/>) to a PE (<xref target="sec-pe"/>). A CE is connected to a PE via one or multiple ACs.</t> <t>This document uses the concept of distributed CE and PE (Sections <xref format="counter" target="sec-ce"/> and <xref format="counter" target="sec-pe"/>) to consolidate a CE/AC/PE definition that is consistent with the orchestration perimeters (<xref target="sec-orch"/>). The CEs and PEs delimitrespectivelythe customer and provider orchestration domains, respectively, while an AC interconnects these domains.</t> <t>For consistency with the terminology used in AC data modelsterminology(e.g., the data models defined in <xreftarget="I-D.ietf-opsawg-teas-attachment-circuit"/>target="RFC9834"/> and <xreftarget="I-D.ietf-opsawg-ntw-attachment-circuit"/>),target="RFC9835"/>), this document assumes that an AC is configured on a "bearer", which represents the underlying connectivity. For example, the bearer is illustrated with "===" in Figures <xref format="counter" target="fig-distribute-ce"/> and <xref format="counter" target="fig-50"/>.</t> <!-- [rfced] Are the two instances of "(AC)" needed here? Original: Examples of ACs are Virtual Local Area Networks (VLANs) (AC) configured on a physical interface (bearer) or an Overlay VXLAN EVI (AC) configured on an IP underlay (bearer). Perhaps: Examples of ACs are Virtual Local Area Networks (VLANs) configured on a physical interface (bearer) or an Overlay VXLAN EVI configured on an IP underlay (bearer). --> <t>An AC istechnology-specific.technology specific. Examples of ACs are Virtual Local Area Networks (VLANs) (AC) configured on a physical interface (bearer) or an Overlay VXLAN EVI (AC) configured on an IP underlay (bearer).</t> <t>Deployment cases where the AC is also managed by the provider are not discussed inthethis document because the setup of such an AC does not require any coordination between the customer and provider orchestration domains.</t> <aside><t>In<t>Note: In order to keep the figures simple, only one AC and single-homed CEs are represented. Also, the underlying bearers are not represented in most of the figures. However, this document does not exclude the instantiation of multiple ACs between a CE and a PE nor the presence of CEs that are attached to more than one PE.</t> </aside> </section> </section> <section anchor="sec-orch"> <name>Orchestration Overview</name> <section anchor="sec-5g-sli-arch"> <name>5G End-to-End Slice Orchestration Architecture</name> <t>This section introduces a global framework for the orchestration of a 5G end-to-end slice (a.k.a. 5G Network Slice) with a zoom on TN parts. This framework helps to delimit the realization scope ofRFC 9543RFC 9543 Network Slices and identify interactions that are required for the realization of such slices.</t> <t>This framework is consistent with the management coordination example shown in Figure 4.7.1 of <xref target="TS-28.530"/>.</t><t>In<!-- [rfced] Is "End-to-End" intended to be part of the expansion for "5G NSO"? Original: In reference to Figure 6, a 5G End-to-End Network Slice Orchestrator (5G NSO) is responsible for orchestrating 5G Network Slices end-to- end. Perhaps: In Figure 6, a 5G Network Slice Orchestrator (5G NSO) is responsible for orchestrating 5G Network Slices end-to- end. --> <t>In <xref target="_figure-orch"/>, a 5G End-to-End Network Slice Orchestrator (5G NSO) is responsible for orchestrating 5G Network Slices end-to-end. The details of the 5G NSO are out of the scope of this document. The realization of the 5G Network Slices spans RAN, CN, and TN. As mentioned in <xref target="sec-scope"/>, the RAN and CN are under the responsibility of the 3GPPManagement System,management system, while the TN is not. The orchestration of the TN is split into two subdomains in conformance with the reference design in <xref target="sec-ref-design"/>:</t> <dl> <dt>Provider Network Orchestration domain:</dt> <dd> <t>As defined in <xref target="RFC9543"/>, the provider relies on a Network Slice Controller (NSC) to manage and orchestrate RFC 9543 Network Slices in the provider network. This framework allows for managing connectivity with SLOs.</t> </dd> <dt>Customer Site Orchestration domain:</dt> <dd> <t>TheOrchestrationorchestration of TN elements of the customer sites relies upon a variety of controllers (e.g., Fabric Manager, Element Management System, or Virtualized Infrastructure Manager (VIM)).</t> </dd> </dl> <t>A TN slice relies upon resources that can involve both the provider and customer TN domains. More details are provided in <xref target="sec-tn-nsi"/>.</t> <t>A TN slice might be considered as a variant of horizontal composition of Network Slices mentioned inAppendix A.6 of<xref section="A.6" target="RFC9543"/>.</t> <figure anchor="_figure-orch"> <name>5G End-to-End Slice Orchestration with TN</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="592" width="544" viewBox="0 0 544 592" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,368 L 8,512" fill="none" stroke="black"/> <path d="M 24,416 L 24,448" fill="none" stroke="black"/> <path d="M 32,144 L 32,408" fill="none" stroke="black"/> <path d="M 48,416 L 48,448" fill="none" stroke="black"/> <path d="M 56,224 L 56,288" fill="none" stroke="black"/> <path d="M 72,240 L 72,288" fill="none" stroke="black"/> <path d="M 88,416 L 88,448" fill="none" stroke="black"/> <path d="M 96,296 L 96,360" fill="none" stroke="black"/> <path d="M 120,128 L 120,160" fill="none" stroke="black"/> <path d="M 120,368 L 120,408" fill="none" stroke="black"/> <path d="M 120,456 L 120,512" fill="none" stroke="black"/> <path d="M 128,416 L 128,448" fill="none" stroke="black"/> <path d="M 184,400 L 184,464" fill="none" stroke="black"/> <path d="M 192,240 L 192,288" fill="none" stroke="black"/> <path d="M 200,368 L 200,392" fill="none" stroke="black"/> <path d="M 200,472 L 200,512" fill="none" stroke="black"/> <path d="M 208,240 L 208,288" fill="none" stroke="black"/> <path d="M 224,400 L 224,464" fill="none" stroke="black"/> <path d="M 232,64 L 232,104" fill="none" stroke="black"/> <path d="M 248,128 L 248,160" fill="none" stroke="black"/> <path d="M 256,296 L 256,360" fill="none" stroke="black"/> <path d="M 264,64 L 264,136" fill="none" stroke="black"/> <path d="M 264,152 L 264,200" fill="none" stroke="black"/> <path d="M 304,240 L 304,288" fill="none" stroke="black"/> <path d="M 320,240 L 320,288" fill="none" stroke="black"/> <path d="M 320,400 L 320,464" fill="none" stroke="black"/> <path d="M 344,368 L 344,392" fill="none" stroke="black"/> <path d="M 344,472 L 344,512" fill="none" stroke="black"/> <path d="M 360,400 L 360,464" fill="none" stroke="black"/> <path d="M 416,400 L 416,448" fill="none" stroke="black"/> <path d="M 424,368 L 424,392" fill="none" stroke="black"/> <path d="M 424,456 L 424,512" fill="none" stroke="black"/> <path d="M 432,296 L 432,360" fill="none" stroke="black"/> <path d="M 440,240 L 440,288" fill="none" stroke="black"/> <path d="M 456,224 L 456,288" fill="none" stroke="black"/> <path d="M 464,400 L 464,448" fill="none" stroke="black"/> <path d="M 488,144 L 488,416" fill="none" stroke="black"/> <path d="M 512,368 L 512,512" fill="none" stroke="black"/> <path d="M 224,32 L 288,32" fill="none" stroke="black"/> <path d="M 224,64 L 288,64" fill="none" stroke="black"/> <path d="M 136,112 L 232,112" fill="none" stroke="black"/> <path d="M 32,144 L 120,144" fill="none" stroke="black"/> <path d="M 248,144 L 488,144" fill="none" stroke="black"/> <path d="M 136,176 L 232,176" fill="none" stroke="black"/> <path d="M 72,208 L 440,208" fill="none" stroke="black"/> <path d="M 72,240 L 192,240" fill="none" stroke="black"/> <path d="M 208,240 L 304,240" fill="none" stroke="black"/> <path d="M 320,240 L 440,240" fill="none" stroke="black"/> <path d="M 72,288 L 192,288" fill="none" stroke="black"/> <path d="M 208,288 L 304,288" fill="none" stroke="black"/> <path d="M 320,288 L 440,288" fill="none" stroke="black"/> <path d="M 72,304 L 88,304" fill="none" stroke="black"/> <path d="M 104,304 L 248,304" fill="none" stroke="black"/> <path d="M 264,304 L 424,304" fill="none" stroke="black"/> <path d="M 8,368 L 24,368" fill="none" stroke="black"/> <path d="M 40,368 L 120,368" fill="none" stroke="black"/> <path d="M 200,368 L 344,368" fill="none" stroke="black"/> <path d="M 424,368 L 480,368" fill="none" stroke="black"/> <path d="M 496,368 L 512,368" fill="none" stroke="black"/> <path d="M 184,400 L 224,400" fill="none" stroke="black"/> <path d="M 320,400 L 360,400" fill="none" stroke="black"/> <path d="M 416,400 L 464,400" fill="none" stroke="black"/> <path d="M 24,416 L 48,416" fill="none" stroke="black"/> <path d="M 88,416 L 128,416" fill="none" stroke="black"/> <path d="M 472,416 L 488,416" fill="none" stroke="black"/> <path d="M 128,432 L 184,432" fill="none" stroke="black"/> <path d="M 360,432 L 416,432" fill="none" stroke="black"/> <path d="M 24,448 L 48,448" fill="none" stroke="black"/> <path d="M 88,448 L 128,448" fill="none" stroke="black"/> <path d="M 416,448 L 464,448" fill="none" stroke="black"/> <path d="M 184,464 L 224,464" fill="none" stroke="black"/> <path d="M 320,464 L 360,464" fill="none" stroke="black"/> <path d="M 8,512 L 120,512" fill="none" stroke="black"/> <path d="M 200,512 L 344,512" fill="none" stroke="black"/> <path d="M 424,512 L 512,512" fill="none" stroke="black"/> <path d="M 192,544 L 224,544" fill="none" stroke="black"/> <path d="M 336,544 L 352,544" fill="none" stroke="black"/> <path d="M 48,576 L 200,576" fill="none" stroke="black"/> <path d="M 272,576 L 416,576" fill="none" stroke="black"/> <path d="M 224,32 C 215.16936,32 208,39.16936 208,48" fill="none" stroke="black"/> <path d="M 288,32 C 296.83064,32 304,39.16936 304,48" fill="none" stroke="black"/> <path d="M 224,64 C 215.16936,64 208,56.83064 208,48" fill="none" stroke="black"/> <path d="M 288,64 C 296.83064,64 304,56.83064 304,48" fill="none" stroke="black"/> <path d="M 136,112 C 127.16936,112 120,119.16936 120,128" fill="none" stroke="black"/> <path d="M 232,112 C 240.83064,112 248,119.16936 248,128" fill="none" stroke="black"/> <path d="M 136,176 C 127.16936,176 120,168.83064 120,160" fill="none" stroke="black"/> <path d="M 232,176 C 240.83064,176 248,168.83064 248,160" fill="none" stroke="black"/> <path d="M 72,208 C 63.16936,208 56,215.16936 56,224" fill="none" stroke="black"/> <path d="M 440,208 C 448.83064,208 456,215.16936 456,224" fill="none" stroke="black"/> <path d="M 72,304 C 63.16936,304 56,296.83064 56,288" fill="none" stroke="black"/> <path d="M 440,304 C 448.83064,304 456,296.83064 456,288" fill="none" stroke="black"/> <polygon class="arrowhead" points="480,416 468,410.4 468,421.6" fill="black" transform="rotate(180,472,416)"/> <polygon class="arrowhead" points="440,360 428,354.4 428,365.6" fill="black" transform="rotate(90,432,360)"/> <polygon class="arrowhead" points="272,200 260,194.4 260,205.6" fill="black" transform="rotate(90,264,200)"/> <path class="jump" d="M 264,152 C 270,152 270,136 264,136" fill="none" stroke="black"/> <polygon class="arrowhead" points="264,360 252,354.4 252,365.6" fill="black" transform="rotate(90,256,360)"/> <polygon class="arrowhead" points="240,104 228,98.4 228,109.6" fill="black" transform="rotate(90,232,104)"/> <polygon class="arrowhead" points="104,360 92,354.4 92,365.6" fill="black" transform="rotate(90,96,360)"/> <polygon class="arrowhead" points="40,408 28,402.4 28,413.6" fill="black" transform="rotate(90,32,408)"/> <g class="text"> <text x="236" y="52">5G</text> <text x="264" y="52">NSO</text> <text x="148" y="132">3GPP</text> <text x="200" y="132">domains</text> <text x="184" y="148">Orchestration</text> <text x="148" y="164">(RAN</text> <text x="184" y="164">and</text> <text x="216" y="164">CN)</text> <text x="76" y="228">TN</text> <text x="144" y="228">Orchestration</text> <text x="108" y="260">Customer</text> <text x="164" y="260">Site</text> <text x="240" y="260">RFC9543</text> <text x="288" y="260">NSC</text> <text x="356" y="260">Customer</text> <text x="412" y="260">Site</text> <text x="128" y="276">Orchestration</text> <text x="376" y="276">Orchestration</text> <text x="268" y="388">Provider</text> <text x="272" y="404">Network</text> <text x="164" y="420">AC</text> <text x="388" y="420">AC</text> <text x="436" y="420">NF</text> <text x="36" y="436">NF</text> <text x="68" y="436">....</text> <text x="108" y="436">CE</text> <text x="204" y="436">PE</text> <text x="340" y="436">PE</text> <text x="444" y="436">(CE)</text> <text x="60" y="484">Customer</text> <text x="468" y="484">Customer</text> <text x="60" y="500">Site</text> <text x="468" y="500">Site</text> <text x="256" y="532">RFC</text> <text x="292" y="532">9543</text> <text x="184" y="548">|</text> <text x="256" y="548">Network</text> <text x="312" y="548">Slice</text> <text x="360" y="548">|</text> <text x="40" y="580">|</text> <text x="212" y="580">TN</text> <text x="248" y="580">Slice</text> <text x="424" y="580">|</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ .---------. | 5G NSO | '-+---+---' | | v | .-------------. | | 3GPP domains | | .----------+ Orchestration +-)---------------------------. | | (RAN and CN) | | | | '-------------' | | | v | | .-----------------------------------------------. | | | TN Orchestration | | | | +--------------+ +-----------+ +--------------+ | | | | |Customer Site | |RFC9543 NSC| |Customer Site | | | | | |Orchestration | | | |Orchestration | | | | | +--------------+ +-----------+ +--------------+ | | | '---|-------------------|---------------------|-' | | | | | | | | | | | | v v v | +--|----------+ +-----------------+ +-------|--+ | | | | Provider | | | | | v | +----+ Network +----+ +-----+ | | | +--+ +----+ AC | | | | AC | NF |<-+ | | |NF+....+ CE +------+ PE | | PE +------+ (CE)| | | +--+ +----+ | | | | +-----+ | | | +----+ +----+ | | | Customer | | | | Customer | | Site | | | | Site | +-------------+ +-----------------+ +----------+ RFC 9543 |-----Network Slice---| |--------------------TN Slice-------------------| ]]></artwork> </artset> </figure> <!-- [rfced] Should "various orchestration" in this sentence be updated to either "various orchestration domains" or "various orchestrations"? Also, is "e.g." needed in the sentence? Original: The various orchestration depicted in Figure 6 encompass the 3GPP's Network Slice Subnet Management Function (NSSMF) mentioned, e.g., in Figure 5 of [I-D.ietf-teas-5g-network-slice-application]. Perhaps: The various orchestration domains depicted in Figure 6 encompass the 3GPP's Network Slice Subnet Management Function (NSSMF) mentioned in Figure 5 of [NS-APP]. Or: The various orchestrations depicted in Figure 6 encompass the 3GPP's Network Slice Subnet Management Function (NSSMF) mentioned in Figure 5 of [NS-APP]. --> <t>The various orchestration depicted in <xref target="_figure-orch"/> encompass the 3GPP's Network Slice Subnet Management Function (NSSMF) mentioned, e.g., in Figure 5 of <xref target="I-D.ietf-teas-5g-network-slice-application"/>.</t> </section> <section anchor="sec-tn-nsi"> <name>Transport Network Segments and Network Slice Instantiation</name> <t>The concept of distributed PE (<xref target="sec-pe"/>) assimilates the CE-based SDPs defined in <xref section="5.2" sectionFormat="of" target="RFC9543"/> (i.e., Types 1 and 2) as SDPTypeTypes 3 or 4 in this document.</t> <t>Inreference tothe architecture depicted in <xref target="sec-5g-sli-arch"/>, the connectivity between NFs can be decomposed into three main segment types:</t> <dl> <dt>Customer Site:</dt> <dd> <t>Either connects NFs located in the same customer site or connects an NF to a CE.</t></dd> <dt/> <dd><t>This segment may not be present if the NF is the CE. In thiscasecase, the AC connects the NF to a PE.</t></dd> <dt/> <dd><t>The realization of this segment is driven by the 5G Network Orchestration (e.g.,NFsNF instantiation) and the Customer Site Orchestration for the TN part.</t> </dd> <dt>Provider Network:</dt> <dd> <t>Represents the connectivity between two PEs. The realization of this segment is controlled by an NSC (<xref section="6.3" sectionFormat="of" target="RFC9543"/>).</t> </dd> <dt>Attachment Circuit:</dt> <dd> <t>The orchestration of this segment relies partially upon an NSC for the configuration of the AC on the PE customer-facing interfaces and the Customer Site Orchestration for the configuration of the AC on the CE.</t></dd> <dt/> <dd><t>PEs and CEs that are connected via an AC need to be provisioned with consistent data plane and control plane information(VLAN-(VLAN IDs, IP addresses/subnets, BGP Autonomous System(AS) Number,Number (ASN), etc.). Hence, the realization of this interconnection istechnology-specifictechnology specific and requires coordination between the Customer Site Orchestration and an NSC. Automating the provisioning and management of the AC is thus key to automate the overall service provisioning. Aligned with <xref target="RFC8969"/>, this document assumes that this coordination is based upon standard YANG data models and APIs.</t></dd> <dt/> <dd><t>The provisioning ofa RFC9543an RFC 9543 Network Slice may rely on new or existing ACs.</t></dd> <dt/> <dd><t><xref target="_figure-4"/> is a basic example of a Layer 3 CE-PE link realization with shared network resources (such asVLAN-IDsVLAN IDs and IPprefixes)prefixes), which are passed betweenOrchestratorsorchestrators via a dedicated interface, e.g., the Network Slice Service Model (NSSM) <xref target="I-D.ietf-teas-ietf-network-slice-nbi-yang"/> ortheAttachmentCircuit-as-a-ServiceCircuits as a Service (ACaaS) <xreftarget="I-D.ietf-opsawg-teas-attachment-circuit"/>.</t>target="RFC9834"/>.</t> </dd> </dl> <figure anchor="_figure-4"> <name>Coordination of Transport Network Resources fortheAC Provisioning</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="320" width="472" viewBox="0 0 472 320" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,160 L 8,272" fill="none" stroke="black"/> <path d="M 24,48 L 24,96" fill="none" stroke="black"/> <path d="M 24,192 L 24,224" fill="none" stroke="black"/> <path d="M 48,192 L 48,224" fill="none" stroke="black"/> <path d="M 96,192 L 96,224" fill="none" stroke="black"/> <path d="M 120,192 L 120,224" fill="none" stroke="black"/> <path d="M 136,120 L 136,184" fill="none" stroke="black"/> <path d="M 152,48 L 152,96" fill="none" stroke="black"/> <path d="M 152,160 L 152,200" fill="none" stroke="black"/> <path d="M 152,216 L 152,272" fill="none" stroke="black"/> <path d="M 312,48 L 312,96" fill="none" stroke="black"/> <path d="M 320,160 L 320,200" fill="none" stroke="black"/> <path d="M 320,216 L 320,272" fill="none" stroke="black"/> <path d="M 336,120 L 336,176" fill="none" stroke="black"/> <path d="M 344,192 L 344,224" fill="none" stroke="black"/> <path d="M 368,192 L 368,224" fill="none" stroke="black"/> <path d="M 464,48 L 464,96" fill="none" stroke="black"/> <path d="M 464,160 L 464,272" fill="none" stroke="black"/> <path d="M 40,32 L 136,32" fill="none" stroke="black"/> <path d="M 328,32 L 448,32" fill="none" stroke="black"/> <path d="M 160,96 L 304,96" fill="none" stroke="black"/> <path d="M 40,112 L 136,112" fill="none" stroke="black"/> <path d="M 328,112 L 448,112" fill="none" stroke="black"/> <path d="M 8,160 L 128,160" fill="none" stroke="black"/> <path d="M 344,160 L 464,160" fill="none" stroke="black"/> <path d="M 24,192 L 48,192" fill="none" stroke="black"/> <path d="M 96,192 L 120,192" fill="none" stroke="black"/> <path d="M 344,192 L 368,192" fill="none" stroke="black"/> <path d="M 120,208 L 344,208" fill="none" stroke="black"/> <path d="M 24,224 L 48,224" fill="none" stroke="black"/> <path d="M 96,224 L 120,224" fill="none" stroke="black"/> <path d="M 344,224 L 368,224" fill="none" stroke="black"/> <path d="M 8,272 L 152,272" fill="none" stroke="black"/> <path d="M 320,272 L 464,272" fill="none" stroke="black"/> <path d="M 136,304 L 216,304" fill="none" stroke="black"/> <path d="M 256,304 L 336,304" fill="none" stroke="black"/> <path d="M 40,32 C 31.16936,32 24,39.16936 24,48" fill="none" stroke="black"/> <path d="M 136,32 C 144.83064,32 152,39.16936 152,48" fill="none" stroke="black"/> <path d="M 328,32 C 319.16936,32 312,39.16936 312,48" fill="none" stroke="black"/> <path d="M 448,32 C 456.83064,32 464,39.16936 464,48" fill="none" stroke="black"/> <path d="M 40,112 C 31.16936,112 24,104.83064 24,96" fill="none" stroke="black"/> <path d="M 136,112 C 144.83064,112 152,104.83064 152,96" fill="none" stroke="black"/> <path d="M 328,112 C 319.16936,112 312,104.83064 312,96" fill="none" stroke="black"/> <path d="M 448,112 C 456.83064,112 464,104.83064 464,96" fill="none" stroke="black"/> <polygon class="arrowhead" points="344,176 332,170.4 332,181.6" fill="black" transform="rotate(90,336,176)"/> <polygon class="arrowhead" points="312,96 300,90.4 300,101.6" fill="black" transform="rotate(0,304,96)"/> <polygon class="arrowhead" points="168,96 156,90.4 156,101.6" fill="black" transform="rotate(180,160,96)"/> <polygon class="arrowhead" points="144,184 132,178.4 132,189.6" fill="black" transform="rotate(90,136,184)"/> <g class="text"> <text x="368"y="52">RFC9543</text>y="52">RFC 9543</text> <text x="416" y="52">NSC</text> <text x="68" y="68">Customer</text> <text x="124" y="68">Site</text> <text x="88" y="84">Orchestration</text> <text x="204" y="84">IETF</text> <text x="256" y="84">APIs/DM</text> <text x="352" y="84">(Provider</text> <text x="424" y="84">Network</text> <text x="388" y="100">Orchestration)</text> <text x="144" y="164">-</text> <text x="328" y="164">-</text> <text x="140" y="196">.1</text> <text x="236" y="196">192.0.2.0/31</text> <text x="332" y="196">.0</text> <text x="36" y="212">NF</text> <text x="72" y="212">.....</text> <text x="108" y="212">CE</text> <text x="356" y="212">PE</text> <text x="220" y="228">VLAN</text> <text x="256" y="228">100</text> <text x="76" y="244">Customer</text> <text x="396" y="244">Provider</text> <text x="76" y="260">Site</text> <text x="392" y="260">Network</text> <text x="128" y="308">|</text> <text x="236" y="308">AC</text> <text x="344" y="308">|</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ .-------------. .----------------. | | |RFC9543RFC 9543 NSC | | Customer Site | | | | Orchestration | IETF APIs/DM |(Provider Network | | |<----------------->| Orchestration) | '-------------' '----------------' | | | | +---------------|-+ +-|---------------+ | v | | v | | +--+ +--+ .1| 192.0.2.0/31 |.0+--+ | | |NF+.....+CE+---------------------------+PE| | | +--+ +--+ | VLAN 100 | +--+ | | Customer | | Provider | | Site | | Network | +-----------------+ +-----------------+ |----------- AC -----------| ]]></artwork> </artset> </figure> </section> </section> <section anchor="sec-mapping"> <name>Mapping 5G Network Slices to Transport Network Slices</name> <t>There are multiple options for mapping 5G Network Slices to TN slices:</t><ul spacing="normal"> <li> <t>1 to N: A<dl spacing="normal" newline="false"> <dt>1-to-N mapping:</dt> <dd>A single 5G Network Slice can be mapped to multiple TNslices (1 to N).slices. For instance, consider the scenario depicted in <xref target="_figure-5"/>,illustratingwhich illustrates the separation of the 5G control plane and user plane in TN slices for a single 5G Enhanced Mobile Broadband (eMBB) network slice. It is important to note that this mapping can serve as an interim step toM to NM-to-N mapping. Further details about this scheme are described in <xreftarget="sec-firstslice"/>.</t> </li> <li> <t>M to 1: Multipletarget="sec-firstslice"/>.</dd> <dt>M-to-1 mapping:</dt> <dd>Multiple 5G Network Slices may rely upon the same TN slice. In such a case, the Service Level Agreement (SLA) differentiation of slices would be entirely controlled at the 5G control plane, for example, with appropriate placementstrategies: thisstrategies. This use case is illustrated in <xref target="_figure-6"/>, where a User Plane Function (UPF) for theUltra Reliable Low LatencyUltra-Reliable Low-Latency Communication (URLLC) slice is instantiated at the edge cloud, close to the gNBCentralized Unit User Plane (CU-UP),CU-UP, to improve latency and jitter control. The 5G control plane and the UPF for the eMBB slice are instantiated in the regionalcloud.</t> </li> <li> <t>Mcloud.</dd> <!-- [rfced] Will readers understand the ">>" notation here? We see it defined as "bitwise right shift", "logical right shift", and "arithmetic right shift of the two's complement integer representation of M by N binary digits" in various RFCs. Original: In practice, for operational and scaling reasons, typically M toN: TheN would be used, with M >> N. --> <dt>M-to-N mapping:</dt> <dd><t>The mapping of 5G to TN slicemappingcombines both approaches with a mix of shared and dedicated associations. </t><t> In<t>In this scenario, a subset of the TN slices can be intended for sharing by multiple 5G Network Slices (e.g., the control plane TN slice is shared by multiple 5GnetworkNetwork Slices). </t><t> In<t>In practice, for operational and scaling reasons,typically M to NM-to-N mapping would typically be used, with M >> N.</t></li> </ul></dd> </dl> <!-- [rfced] Titles of figures a) Should "Site" be plural in this title as Figure 3 shows two sites? Original: Figure 3: Reference Design with Customer Site and Provider Network Perhaps: Figure 3: Reference Design with Customer Sites and Provider Network b) Should the title of Figure 9 use "M" rather than "N"? We ask because "N to 1" is not included in the list above the figure. The list only includes "1 to N", "M to 1", and "M to N". Also, may revise the titles of Figures 8 and 9 in one of the following ways to improve readability? Original: Figure 8: 1 (5G Slice) to N (TN Slice) Mapping Figure 9: N (5G Slice) to 1 (TN Slice) Mapping Perhaps: Figure 8: 1-to-N Mapping Figure 9: M-to-1 Mapping Or: Figure 8: 1-to-N Mapping (Single 5G Slice to Multiple TN Slices) Figure 9: M-to-1 Mapping (Multiple 5G Slices to Single TN Slice) c) FYI - We added "Example of" to the title of Figure 16 to align with the title of Figure 15. Original: Figure 15: Example of MPLS Hand-off with Option B Figure 16: MPLS Hand-off with Option C Updated: Figure 15: Example of MPLS Handoff with Option B Figure 16: Example of MPLS Handoff with Option C d) Is "Ingress" correct in the title of Figure 21, or should it be updated to "Egress"? Also, is "Output" needed? We included the title of Figure 20 below for comparison. Original: Figure 20: Ingress Slice Admission Control (5QI-unaware Model) Figure 21: Ingress Slice Admission control (5QI-unaware Model) - Output Perhaps: Figure 20: Ingress Slice Admission Control (5QI-Unaware Model) Figure 21: Egress Slice Admission Control (5QI-Unaware Model) e) FYI - We included "Model" to the parenthetical in these figure titles. Original: Figure 25: Ingress Slice Admission Control (5QI-Aware) - Hierarchical Figure 26: Egress Slice Admission Control (5QI-Aware) Perhaps: Figure 25: Ingress Slice Admission Control (5QI-Aware Model) - Hierarchical Figure 26: Egress Slice Admission Control (5QI-Aware Model) f) We revised the figure titles below as follows to avoid awkward hyphenation with "Mapping". For Figure 28, we also removed "PEs" for consistency with the title of Figure 29. For the title of Figure 17, should "Slice" be updated to "Network Slice", or is the current okay? Original: Figure 17: Slice to TN QoS Mapping (5QI-Unaware Model) Figure 22: Slice 5Q QoS to TN QoS Mapping (5QI-Aware Model) Figure 28: Network Slice to PEs Underlay Transport Mapping (5QI-Unaware Model) Figure 29: Network Slice to Underlay Transport Mapping (5QI-Aware Model) Updated: Figure 17: Mapping of Slice to TN QoS (5QI-Unaware Model) Figure 22: Mapping of Slice 5Q QoS to TN QoS (5QI-Aware Model) Figure 28: Mapping of Network Slice to Underlay Transport (5QI-Unaware Model) Figure 29: Mapping of Network Slice to Underlay Transport (5QI-Aware Model) --> <figure anchor="_figure-5"> <name>1 (5G Slice) to N (TN Slice) Mapping</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="256" width="544" viewBox="0 0 544 256" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,192" fill="none" stroke="black"/> <path d="M 24,80 L 24,112" fill="none" stroke="black"/> <path d="M 24,144 L 24,176" fill="none" stroke="black"/> <path d="M 72,80 L 72,112" fill="none" stroke="black"/> <path d="M 72,144 L 72,176" fill="none" stroke="black"/> <path d="M 112,64 L 112,88" fill="none" stroke="black"/> <path d="M 112,104 L 112,152" fill="none" stroke="black"/> <path d="M 112,168 L 112,240" fill="none" stroke="black"/> <path d="M 128,80 L 128,112" fill="none" stroke="black"/> <path d="M 128,144 L 128,176" fill="none" stroke="black"/> <path d="M 392,80 L 392,112" fill="none" stroke="black"/> <path d="M 392,144 L 392,176" fill="none" stroke="black"/> <path d="M 408,64 L 408,88" fill="none" stroke="black"/> <path d="M 408,104 L 408,152" fill="none" stroke="black"/> <path d="M 408,168 L 408,240" fill="none" stroke="black"/> <path d="M 456,80 L 456,112" fill="none" stroke="black"/> <path d="M 456,144 L 456,176" fill="none" stroke="black"/> <path d="M 504,80 L 504,112" fill="none" stroke="black"/> <path d="M 504,144 L 504,176" fill="none" stroke="black"/> <path d="M 520,32 L 520,192" fill="none" stroke="black"/> <path d="M 8,32 L 520,32" fill="none" stroke="black"/> <path d="M 112,64 L 408,64" fill="none" stroke="black"/> <path d="M 24,80 L 72,80" fill="none" stroke="black"/> <path d="M 128,80 L 392,80" fill="none" stroke="black"/> <path d="M 456,80 L 504,80" fill="none" stroke="black"/> <path d="M 72,96 L 128,96" fill="none" stroke="black"/> <path d="M 392,96 L 456,96" fill="none" stroke="black"/> <path d="M 24,112 L 72,112" fill="none" stroke="black"/> <path d="M 128,112 L 392,112" fill="none" stroke="black"/> <path d="M 456,112 L 504,112" fill="none" stroke="black"/> <path d="M 24,144 L 72,144" fill="none" stroke="black"/> <path d="M 128,144 L 392,144" fill="none" stroke="black"/> <path d="M 456,144 L 504,144" fill="none" stroke="black"/> <path d="M 72,160 L 128,160" fill="none" stroke="black"/> <path d="M 392,160 L 456,160" fill="none" stroke="black"/> <path d="M 24,176 L 72,176" fill="none" stroke="black"/> <path d="M 128,176 L 392,176" fill="none" stroke="black"/> <path d="M 456,176 L 504,176" fill="none" stroke="black"/> <path d="M 8,192 L 104,192" fill="none" stroke="black"/> <path d="M 120,192 L 400,192" fill="none" stroke="black"/> <path d="M 416,192 L 520,192" fill="none" stroke="black"/> <path d="M 112,240 L 408,240" fill="none" stroke="black"/> <g class="text"> <text x="212" y="52">5G</text> <text x="248" y="52">Slice</text> <text x="292" y="52">eMBB</text> <text x="92" y="84">N3</text> <text x="436" y="84">N3</text> <text x="48" y="100">CU-UP</text> <text x="212" y="100">TN</text> <text x="248" y="100">Slice</text> <text x="304" y="100">UP_eMBB</text> <text x="480" y="100">UPF</text> <text x="92" y="148">N2</text> <text x="436" y="148">N2</text> <text x="48" y="164">CU-CP</text> <text x="236" y="164">TN</text> <text x="272" y="164">Slice</text> <text x="308" y="164">CP</text> <text x="480" y="164">AMF</text> <text x="240" y="228">Transport</text> <text x="312" y="228">Network</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +---------------------------------------------------------------+ | 5G Slice eMBB | | +------------------------------------+ | | +-----+ N3 | +--------------------------------+ | N3 +-----+ | | |CU-UP+------+ TN Slice UP_eMBB +-------+ UPF | | | +-----+ | +--------------------------------+ | +-----+ | | | | | | +-----+ N2 | +--------------------------------+ | N2 +-----+ | | |CU-CP+------+ TN Slice CP +-------+ AMF | | | +-----+ | +--------------------------------+ | +-----+ | +------------|------------------------------------|-------------+ | | | Transport Network | +------------------------------------+ ]]></artwork> </artset> </figure> <figure anchor="_figure-6"> <name>N (5G Slice) to 1 (TN Slice) Mapping</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="416" width="552" viewBox="0 0 552 416" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,160 L 8,336" fill="none" stroke="black"/> <path d="M 24,224 L 24,256" fill="none" stroke="black"/> <path d="M 24,288 L 24,320" fill="none" stroke="black"/> <path d="M 120,224 L 120,256" fill="none" stroke="black"/> <path d="M 120,288 L 120,320" fill="none" stroke="black"/> <path d="M 136,160 L 136,232" fill="none" stroke="black"/> <path d="M 136,248 L 136,296" fill="none" stroke="black"/> <path d="M 136,312 L 136,336" fill="none" stroke="black"/> <path d="M 152,32 L 152,128" fill="none" stroke="black"/> <path d="M 152,160 L 152,232" fill="none" stroke="black"/> <path d="M 152,248 L 152,296" fill="none" stroke="black"/> <path d="M 152,312 L 152,400" fill="none" stroke="black"/> <path d="M 168,64 L 168,96" fill="none" stroke="black"/> <path d="M 168,192 L 168,352" fill="none" stroke="black"/> <path d="M 216,96 L 216,192" fill="none" stroke="black"/> <path d="M 248,64 L 248,96" fill="none" stroke="black"/> <path d="M 264,32 L 264,128" fill="none" stroke="black"/> <path d="M 384,192 L 384,352" fill="none" stroke="black"/> <path d="M 400,160 L 400,248" fill="none" stroke="black"/> <path d="M 400,264 L 400,312" fill="none" stroke="black"/> <path d="M 400,328 L 400,400" fill="none" stroke="black"/> <path d="M 416,192 L 416,248" fill="none" stroke="black"/> <path d="M 416,264 L 416,312" fill="none" stroke="black"/> <path d="M 416,328 L 416,368" fill="none" stroke="black"/> <path d="M 432,240 L 432,272" fill="none" stroke="black"/> <path d="M 432,304 L 432,336" fill="none" stroke="black"/> <path d="M 520,240 L 520,272" fill="none" stroke="black"/> <path d="M 520,304 L 520,336" fill="none" stroke="black"/> <path d="M 536,192 L 536,368" fill="none" stroke="black"/> <path d="M 152,32 L 264,32" fill="none" stroke="black"/> <path d="M 168,64 L 248,64" fill="none" stroke="black"/> <path d="M 168,96 L 248,96" fill="none" stroke="black"/> <path d="M 152,128 L 208,128" fill="none" stroke="black"/> <path d="M 224,128 L 264,128" fill="none" stroke="black"/> <path d="M 8,160 L 136,160" fill="none" stroke="black"/> <path d="M 152,160 L 208,160" fill="none" stroke="black"/> <path d="M 224,160 L 400,160" fill="none" stroke="black"/> <path d="M 168,192 L 384,192" fill="none" stroke="black"/> <path d="M 416,192 L 536,192" fill="none" stroke="black"/> <path d="M 24,224 L 120,224" fill="none" stroke="black"/> <path d="M 120,240 L 168,240" fill="none" stroke="black"/> <path d="M 432,240 L 520,240" fill="none" stroke="black"/> <path d="M 24,256 L 120,256" fill="none" stroke="black"/> <path d="M 384,256 L 432,256" fill="none" stroke="black"/> <path d="M 432,272 L 520,272" fill="none" stroke="black"/> <path d="M 24,288 L 120,288" fill="none" stroke="black"/> <path d="M 120,304 L 168,304" fill="none" stroke="black"/> <path d="M 432,304 L 520,304" fill="none" stroke="black"/> <path d="M 24,320 L 120,320" fill="none" stroke="black"/> <path d="M 384,320 L 432,320" fill="none" stroke="black"/> <path d="M 8,336 L 136,336" fill="none" stroke="black"/> <path d="M 432,336 L 520,336" fill="none" stroke="black"/> <path d="M 168,352 L 384,352" fill="none" stroke="black"/> <path d="M 416,368 L 536,368" fill="none" stroke="black"/> <path d="M 152,400 L 400,400" fill="none" stroke="black"/> <g class="text"> <text x="188" y="52">Edge</text> <text x="232" y="52">Cloud</text> <text x="208" y="84">UPF_URLLC</text> <text x="52" y="196">Cell</text> <text x="92" y="196">Site</text> <text x="476" y="212">Regional</text> <text x="480" y="228">Cloud</text> <text x="72" y="244">CU-UP_URLLC</text> <text x="236" y="260">TN</text> <text x="272" y="260">Slice</text> <text x="312" y="260">ALL</text> <text x="464" y="260">5GC</text> <text x="492" y="260">CP</text> <text x="68" y="308">CU-UP_eMBB</text> <text x="476" y="324">UPF_eMBB</text> <text x="240" y="388">Transport</text> <text x="312" y="388">Network</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +-------------+ | Edge Cloud | | +---------+ | | |UPF_URLLC| | | +-----+---+ | | | | +-------|-----+ | +---------------+ +-------|----------------------+ | | | | | | Cell Site | | +-----+--------------------+ | +--------------+ | | | | | | | Regional | | +-----------+ | | | | | | Cloud | | |CU-UP_URLLC+-----+ | | | +----------+ | | +-----------+ | | | TN Slice ALL +-----+ 5GC CP | | | | | | | | | +----------+ | | +-----------+ | | | | | | | | |CU-UP_eMBB +-----+ | | | +----------+ | | +-----------+ | | | +-----+ UPF_eMBB | | +---------------+ | | | | | +----------+ | | +--------------------------+ | | | | | +--------------+ | Transport Network | +------------------------------+ ]]></artwork> </artset> </figure> <t>Note that the actual realization of the mapping depends on several factors, such as the actual business cases, the NF vendor capabilities, the NF vendor reference designs, as well as service provider or even legal requirements.</t> <t>Mapping approaches that preserve the 5G slice identification in the TN (e.g., the approach in <xref target="sec-ip-hof"/>) may simplify required operations to mapbackTN slices back to 5G slices. However, such considerations are not detailed in this document because these are under the responsibility of the 3GPP orchestration domain.</t> </section> <section anchor="sec-firstslice"> <name>First 5G SliceversusVersus Subsequent Slices</name> <t>An operational 5G Network Slice incorporates both 5G control plane and user plane capabilities. For instance, in some deployments, in the case of a slice based onsplit-CUsplit CU in the RAN, both CU-UP andCentralized Unit Control Plane (CU-CP)CU-CP may need to be deployed along with the associated interfaces E1, F1-c, F1-u, N2, andN3N3, which are conveyed in the TN. In this regard, the creation of the "first slice" can be subject to a specific logic that does not apply to subsequent slices. Let us consider the example depicted in <xref target="_figure-7"/> to illustrate this deployment. In this example, the first 5G slice relies on the deployment of NF-CP and NF-UP functions together with two TN slices for the control and user planes (TNS-CP and TNS-UP1). Next, in many cases, the deployment of a second slice relies solely on the instantiation of a UPF (NF-UP2) together with a dedicateduser planeTN slice for the user plane (TNS-UP2). The control plane of the first 5G slice is also updated to integrate the secondslice:slice; the TN slice (TNS-CP) and Network Functions (NF-CP) are shared.</t><ul empty="true"> <li><t>The model described here, in which the control plane is shared among multiple slices, is likely to be common; it is not mandatory, though. Deployment models with a separate control plane for each slice are also possible.</t></li> </ul><t>Section 6.1.2 of <xref target="NG.113"/> specifies that the eMBB slice (SST-1 and no Slice Differentiator (SD)) should be supported globally. This 5G slice would be the first slice in any 5G deployment.</t> <figure anchor="_figure-7"> <name>First and Subsequent Slice Deployment</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="768" width="528" viewBox="0 0 528 768" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,64 L 8,240" fill="none" stroke="black"/> <path d="M 8,352 L 8,544" fill="none" stroke="black"/> <path d="M 8,608 L 8,752" fill="none" stroke="black"/> <path d="M 56,128 L 56,160" fill="none" stroke="black"/> <path d="M 56,192 L 56,224" fill="none" stroke="black"/> <path d="M 56,416 L 56,448" fill="none" stroke="black"/> <path d="M 56,496 L 56,528" fill="none" stroke="black"/> <path d="M 56,640 L 56,672" fill="none" stroke="black"/> <path d="M 104,128 L 104,160" fill="none" stroke="black"/> <path d="M 104,192 L 104,224" fill="none" stroke="black"/> <path d="M 104,416 L 104,448" fill="none" stroke="black"/> <path d="M 104,496 L 104,528" fill="none" stroke="black"/> <path d="M 112,640 L 112,672" fill="none" stroke="black"/> <path d="M 144,112 L 144,136" fill="none" stroke="black"/> <path d="M 144,152 L 144,200" fill="none" stroke="black"/> <path d="M 144,216 L 144,288" fill="none" stroke="black"/> <path d="M 144,400 L 144,424" fill="none" stroke="black"/> <path d="M 144,440 L 144,504" fill="none" stroke="black"/> <path d="M 144,520 L 144,648" fill="none" stroke="black"/> <path d="M 144,664 L 144,704" fill="none" stroke="black"/> <path d="M 160,128 L 160,160" fill="none" stroke="black"/> <path d="M 160,192 L 160,224" fill="none" stroke="black"/> <path d="M 160,416 L 160,448" fill="none" stroke="black"/> <path d="M 160,496 L 160,528" fill="none" stroke="black"/> <path d="M 160,640 L 160,672" fill="none" stroke="black"/> <path d="M 376,128 L 376,160" fill="none" stroke="black"/> <path d="M 376,192 L 376,224" fill="none" stroke="black"/> <path d="M 376,416 L 376,448" fill="none" stroke="black"/> <path d="M 376,496 L 376,528" fill="none" stroke="black"/> <path d="M 376,640 L 376,672" fill="none" stroke="black"/> <path d="M 392,112 L 392,136" fill="none" stroke="black"/> <path d="M 392,152 L 392,200" fill="none" stroke="black"/> <path d="M 392,216 L 392,288" fill="none" stroke="black"/> <path d="M 392,400 L 392,424" fill="none" stroke="black"/> <path d="M 392,440 L 392,504" fill="none" stroke="black"/> <path d="M 392,520 L 392,648" fill="none" stroke="black"/> <path d="M 392,664 L 392,704" fill="none" stroke="black"/> <path d="M 424,640 L 424,672" fill="none" stroke="black"/> <path d="M 432,128 L 432,160" fill="none" stroke="black"/> <path d="M 432,192 L 432,224" fill="none" stroke="black"/> <path d="M 432,416 L 432,448" fill="none" stroke="black"/> <path d="M 432,496 L 432,528" fill="none" stroke="black"/> <path d="M 480,128 L 480,160" fill="none" stroke="black"/> <path d="M 480,192 L 480,224" fill="none" stroke="black"/> <path d="M 480,416 L 480,448" fill="none" stroke="black"/> <path d="M 480,496 L 480,528" fill="none" stroke="black"/> <path d="M 480,640 L 480,672" fill="none" stroke="black"/> <path d="M 520,64 L 520,240" fill="none" stroke="black"/> <path d="M 520,352 L 520,544" fill="none" stroke="black"/> <path d="M 520,608 L 520,752" fill="none" stroke="black"/> <path d="M 8,64 L 520,64" fill="none" stroke="black"/> <path d="M 144,112 L 392,112" fill="none" stroke="black"/> <path d="M 56,128 L 104,128" fill="none" stroke="black"/> <path d="M 160,128 L 376,128" fill="none" stroke="black"/> <path d="M 432,128 L 480,128" fill="none" stroke="black"/> <path d="M 104,144 L 160,144" fill="none" stroke="black"/> <path d="M 376,144 L 432,144" fill="none" stroke="black"/> <path d="M 56,160 L 104,160" fill="none" stroke="black"/> <path d="M 160,160 L 376,160" fill="none" stroke="black"/> <path d="M 432,160 L 480,160" fill="none" stroke="black"/> <path d="M 56,192 L 104,192" fill="none" stroke="black"/> <path d="M 160,192 L 376,192" fill="none" stroke="black"/> <path d="M 432,192 L 480,192" fill="none" stroke="black"/> <path d="M 104,208 L 160,208" fill="none" stroke="black"/> <path d="M 376,208 L 432,208" fill="none" stroke="black"/> <path d="M 56,224 L 104,224" fill="none" stroke="black"/> <path d="M 160,224 L 376,224" fill="none" stroke="black"/> <path d="M 432,224 L 480,224" fill="none" stroke="black"/> <path d="M 8,240 L 136,240" fill="none" stroke="black"/> <path d="M 152,240 L 384,240" fill="none" stroke="black"/> <path d="M 400,240 L 520,240" fill="none" stroke="black"/> <path d="M 144,288 L 392,288" fill="none" stroke="black"/> <path d="M 8,352 L 520,352" fill="none" stroke="black"/> <path d="M 144,400 L 392,400" fill="none" stroke="black"/> <path d="M 56,416 L 104,416" fill="none" stroke="black"/> <path d="M 160,416 L 376,416" fill="none" stroke="black"/> <path d="M 432,416 L 480,416" fill="none" stroke="black"/> <path d="M 104,432 L 160,432" fill="none" stroke="black"/> <path d="M 376,432 L 432,432" fill="none" stroke="black"/> <path d="M 56,448 L 104,448" fill="none" stroke="black"/> <path d="M 160,448 L 376,448" fill="none" stroke="black"/> <path d="M 432,448 L 480,448" fill="none" stroke="black"/> <path d="M 56,496 L 104,496" fill="none" stroke="black"/> <path d="M 160,496 L 376,496" fill="none" stroke="black"/> <path d="M 432,496 L 480,496" fill="none" stroke="black"/> <path d="M 104,512 L 160,512" fill="none" stroke="black"/> <path d="M 376,512 L 432,512" fill="none" stroke="black"/> <path d="M 56,528 L 104,528" fill="none" stroke="black"/> <path d="M 160,528 L 376,528" fill="none" stroke="black"/> <path d="M 432,528 L 480,528" fill="none" stroke="black"/> <path d="M 8,544 L 136,544" fill="none" stroke="black"/> <path d="M 152,544 L 384,544" fill="none" stroke="black"/> <path d="M 400,544 L 520,544" fill="none" stroke="black"/> <path d="M 8,608 L 136,608" fill="none" stroke="black"/> <path d="M 152,608 L 384,608" fill="none" stroke="black"/> <path d="M 400,608 L 520,608" fill="none" stroke="black"/> <path d="M 56,640 L 112,640" fill="none" stroke="black"/> <path d="M 160,640 L 376,640" fill="none" stroke="black"/> <path d="M 424,640 L 480,640" fill="none" stroke="black"/> <path d="M 112,656 L 160,656" fill="none" stroke="black"/> <path d="M 376,656 L 424,656" fill="none" stroke="black"/> <path d="M 56,672 L 112,672" fill="none" stroke="black"/> <path d="M 160,672 L 376,672" fill="none" stroke="black"/> <path d="M 424,672 L 480,672" fill="none" stroke="black"/> <path d="M 144,704 L 392,704" fill="none" stroke="black"/> <path d="M 8,752 L 520,752" fill="none" stroke="black"/> <g class="text"> <text x="16" y="36">(1)</text> <text x="76" y="36">Deployment</text> <text x="132" y="36">of</text> <text x="168"y="36">first</text>y="36">First</text> <text x="204" y="36">5G</text> <text x="240"y="36">slice</text>y="36">Slice</text> <text x="232" y="84">First</text> <text x="268" y="84">5G</text> <text x="304" y="84">Slice</text> <text x="80" y="148">NF-CP</text> <text x="196" y="148">CP</text> <text x="220" y="148">TN</text> <text x="256" y="148">Slice</text> <text x="316" y="148">(TNS-CP)</text> <text x="456" y="148">NF-CP</text> <text x="80" y="212">NF-UP</text> <text x="188" y="212">UP</text> <text x="212" y="212">TN</text> <text x="248" y="212">Slice</text> <text x="312" y="212">(TNS-UP1)</text> <text x="456" y="212">NF-UP</text> <text x="232" y="276">Transport</text> <text x="304" y="276">Network</text> <text x="16" y="324">(2)</text> <text x="76" y="324">Deployment</text> <text x="132" y="324">of</text> <text x="188"y="324">additional</text>y="324">Additional</text> <text x="244" y="324">5G</text> <text x="280"y="324">slice</text>y="324">Slice</text> <text x="324" y="324">with</text> <text x="372"y="324">shared</text>y="324">Shared</text> <text x="432" y="324">Control</text> <text x="488" y="324">Plane</text> <text x="232" y="372">First</text> <text x="268" y="372">5G</text> <text x="304" y="372">Slice</text> <text x="80" y="436">NF-CP</text> <text x="196" y="436">CP</text> <text x="220" y="436">TN</text> <text x="256" y="436">Slice</text> <text x="316" y="436">(TNS-CP)</text> <text x="456" y="436">NF-CP</text> <text x="84" y="468">SHARED</text> <text x="268" y="468">(SHARED)</text> <text x="460" y="468">SHARED</text> <text x="80" y="516">NF-UP</text> <text x="188" y="516">UP</text> <text x="212" y="516">TN</text> <text x="248" y="516">Slice</text> <text x="312" y="516">(TNS-UP1)</text> <text x="456" y="516">NF-UP</text> <text x="232" y="580">Transport</text> <text x="304" y="580">Network</text> <text x="84" y="660">NF-UP2</text> <text x="188" y="660">UP</text> <text x="212" y="660">TN</text> <text x="248" y="660">Slice</text> <text x="312" y="660">(TNS-UP2)</text> <text x="452" y="660">NF-UP2</text> <text x="236" y="740">Second</text> <text x="276" y="740">5G</text> <text x="312" y="740">Slice</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ (1) Deployment of first 5G slice +---------------------------------------------------------------+ | First 5G Slice | | | | +------------------------------+ | | +-----+ | +--------------------------+ | +-----+ | | |NF-CP+------+ CP TN Slice (TNS-CP) +------+NF-CP| | | +-----+ | +--------------------------+ | +-----+ | | | | | | +-----+ | +--------------------------+ | +-----+ | | |NF-UP+------+ UP TN Slice (TNS-UP1) +------+NF-UP| | | +-----+ | +--------------------------+ | +-----+ | +----------------|------------------------------|---------------+ | | | Transport Network | +------------------------------+ (2) Deployment of additional 5G slice with sharedControl Planecontrol plane +---------------------------------------------------------------+ | First 5G Slice | | | | +------------------------------+ | | +-----+ | +--------------------------+ | +-----+ | | |NF-CP+------+ CP TN Slice (TNS-CP) +------+NF-CP| | | +-----+ | +--------------------------+ | +-----+ | | SHARED | (SHARED) | SHARED | | | | | | +-----+ | +--------------------------+ | +-----+ | | |NF-UP+------+ UP TN Slice (TNS-UP1) +------+NF-UP| | | +-----+ | +--------------------------+ | +-----+ | +----------------|------------------------------|---------------+ | | | Transport Network | | | +----------------|------------------------------|---------------+ | | | | | +------+ | +--------------------------+ | +------+ | | |NF-UP2+-----+ UP TN Slice (TNS-UP2) +-----+NF-UP2| | | +------+ | +--------------------------+ | +------+ | | | | | | +------------------------------+ | | | | Second 5G Slice | +---------------------------------------------------------------+ ]]></artwork> </artset> </figure> <!-- [rfced] Is "to instruct" the correct word choice here? Or would "to determine" or something else be an improvement? Original: TN slice mapping policies can be enforced by an operator (e.g., provided to a TN Orchestration or 5G NSO) to instruct whether existing TN slices can be reused for handling a new slice service creation request. Perhaps: TN slice mapping policies can be enforced by an operator (e.g., provided to a TN Orchestration or 5G NSO) to determine whether existing TN slices can be reused for handling a new slice service creation request. --> <t>TN slice mapping policies can be enforced by an operator (e.g., provided to a TN Orchestration or 5G NSO) to instruct whether existing TN slices can be reused for handling a new slice service creation request. Providing such a policy is meant to better automate the realization of 5G slices and minimize the realization delay that might be induced by extra cycles to seek for operator validation.</t> </section> <section anchor="sec-over-rea-model"> <name>Overview of the Transport Network Realization Model</name> <t>The realization model described in this document is depicted in <xref target="_figure-high-level-qos"/>. The following building blocks are used:</t> <ul spacing="normal"> <li> <t>L2VPN <xref target="RFC4664"/> and/or L3VPN <xref target="RFC4364"/> service instances for logical separation: </t><t> This<t>This realization model of transport for 5G slices assumes Layer 3 delivery for midhaul and backhaul transportconnections,connections and a Layer 2 or Layer 3 delivery for fronthaul connections. Enhanced Common Public Radio Interface (eCPRI) <xref target="ECPRI"/> supports both delivery models. L2VPN/L3VPN service instances might be used as a basic form of logical slice separation. Furthermore, using service instances results in an additional outer header (as packets are encapsulated/decapsulated at the nodes hosting serviceinstances)instances), providing clean discrimination between 5G QoS and TN QoS, as explained in <xref target="sec-qos-map"/>. </t><t> Note<t>Note that a variety of L2VPN mechanisms can be considered for slice realization. A non-comprehensive list is providedbelow: </t>below:</t> <ul spacing="normal"> <li> <t>Virtual Private LAN Service (VPLS) <xref target="RFC4761"/> <xref target="RFC4762"/></t> </li> <li> <t>Virtual Private Wire Service (VPWS) (<xref section="3.1.1" sectionFormat="of" target="RFC4664"/>)</t> </li> <li> <t>Various flavors ofEVPNs: </t>EVPNs:</t> <ul spacing="normal"> <li> <t>VPWS EVPN <xref target="RFC8214"/>,</t> </li> <li> <t>Provider Backbone BridgingCombinedcombined withEthernet VPNs (PBB-EVPNs)EVPN (PBB-EVPN) <xref target="RFC7623"/>,</t> </li> <li> <t>EVPN over MPLS <xref target="RFC7432"/>, and</t> </li> <li> <t>EVPN over Virtual Extensible LAN (VXLAN) <xref target="RFC8365"/>.</t> </li> </ul> </li> </ul><t> The<t>The use of VPNs for realizing Network Slices is briefly described inAppendix A.4 of<xref section="A.4" target="RFC9543"/>.</t> </li> <li> <t>Fine-grained resource control at the PE: </t><t> This<t>This is sometimes called'admission control'"admission control" or'traffic conditioning'."traffic conditioning". The main purpose is the enforcement of the bandwidth contract for the slice right at the edge of the provider network where the traffic ishanded-offhanded off between the customer site and the provider network. </t><t> The<t>The method used here is granular ingress policing (rate limiting) to enforce contracted bandwidths per slice and, potentially, per traffic class within the slice. Traffic above the enforced rate might be immediatelydropped,dropped or marked as high drop-probability traffic, which is more likely to be dropped somewhere inside the provider network if congestion occurs. In the egress direction at the PE node, hierarchical schedulers/shapers can be deployed, providing guaranteed rates per slice, as well as guarantees per traffic class within each slice. </t><t> For<t>For managed CEs, edge admission control can be distributed between CEs and PEs, whereapart of the admission control is implemented on the CE and the other partof the admission control is implementedon the PE.</t> </li> <li> <t>Coarse-grained resource control at the transit links (non-attachment circuits)linksin the provider network, using a single NRP (called "base NRP" in <xref target="_figure-high-level-qos"/>), spanning the entire provider network. Transit nodes in the provider network do not maintain any state of individual slices. Instead, only a flat (non-hierarchical) QoS model is used on transit links in the provider network, with up to 8 traffic classes. At the PE,traffic-flowstraffic flows from multiple slice services are mapped to the limited number of traffic classes used onprovider networktransitlinks.</t>links in the provider network.</t> </li> <li> <t>Capacity planning/management for efficient usage of provider networkresources: </t> <t>resources:</t> <!-- [rfced] This sentence may be difficult for readers to follow because of the many "to.." phrases. How may we update? Original: The methods used here can range from careful network planning, to ensure a more or less equal traffic distribution (i.e., equal cost load balancing), to advanced TE techniques, with or without bandwidth reservations, to force more consistent load distribution even in non-ECMP friendly network topologies. Perhaps: The methods used here can range from careful network planning that ensures a more or less equal traffic distribution (i.e., equal-cost load balancing) to advanced TE techniques, with or without bandwidth reservations, that force more consistent load distribution, even in non-ECMP-friendly network topologies. --> <t>The role of capacity planning/management is to ensure the provider network capacity can be utilized without causing any bottlenecks. The methods used here can range from careful network planning, to ensure a more or less equal traffic distribution (i.e.,equal costequal-cost load balancing), to advanced TE techniques, with or without bandwidth reservations, to force more consistent loaddistributiondistribution, even innon-ECMP friendlynon-ECMP-friendly network topologies. See also <xref section="8" sectionFormat="of" target="RFC9522"/>.</t> </li> </ul> <figure anchor="_figure-high-level-qos"> <name>Resource Allocation Slicing Model with a Single NRP</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="416" width="584" viewBox="0 0 584 416" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 56,64 L 56,288" fill="none" stroke="black"/> <path d="M 96,112 L 96,240" fill="none" stroke="black"/> <path d="M 144,64 L 144,288" fill="none" stroke="black"/> <path d="M 208,128 L 208,224" fill="none" stroke="black"/> <path d="M 256,128 L 256,224" fill="none" stroke="black"/> <path d="M 328,128 L 328,224" fill="none" stroke="black"/> <path d="M 376,128 L 376,224" fill="none" stroke="black"/> <path d="M 440,64 L 440,288" fill="none" stroke="black"/> <path d="M 488,112 L 488,240" fill="none" stroke="black"/> <path d="M 528,64 L 528,288" fill="none" stroke="black"/> <path d="M 56,64 L 96,64" fill="none" stroke="black"/> <path d="M 112,64 L 144,64" fill="none" stroke="black"/> <path d="M 440,64 L 472,64" fill="none" stroke="black"/> <path d="M 488,64 L 528,64" fill="none" stroke="black"/> <path d="M 64,112 L 96,112" fill="none" stroke="black"/> <path d="M 488,112 L 520,112" fill="none" stroke="black"/> <path d="M 208,128 L 256,128" fill="none" stroke="black"/> <path d="M 328,128 L 376,128" fill="none" stroke="black"/> <path d="M 64,144 L 96,144" fill="none" stroke="black"/> <path d="M 488,144 L 520,144" fill="none" stroke="black"/> <path d="M 96,176 L 136,176" fill="none" stroke="black"/> <path d="M 152,176 L 200,176" fill="none" stroke="black"/> <path d="M 216,176 L 248,176" fill="none" stroke="black"/> <path d="M 264,176 L 320,176" fill="none" stroke="black"/> <path d="M 336,176 L 368,176" fill="none" stroke="black"/> <path d="M 384,176 L 432,176" fill="none" stroke="black"/> <path d="M 448,176 L 488,176" fill="none" stroke="black"/> <path d="M 64,208 L 96,208" fill="none" stroke="black"/> <path d="M 488,208 L 520,208" fill="none" stroke="black"/> <path d="M 208,224 L 256,224" fill="none" stroke="black"/> <path d="M 328,224 L 376,224" fill="none" stroke="black"/> <path d="M 64,240 L 96,240" fill="none" stroke="black"/> <path d="M 488,240 L 520,240" fill="none" stroke="black"/> <path d="M 56,288 L 96,288" fill="none" stroke="black"/> <path d="M 112,288 L 144,288" fill="none" stroke="black"/> <path d="M 440,288 L 472,288" fill="none" stroke="black"/> <path d="M 488,288 L 528,288" fill="none" stroke="black"/> <polygon class="arrowhead" points="524,240 512,234.4 512,245.6" fill="black" transform="rotate(0,516,240)"/> <polygon class="arrowhead" points="524,208 512,202.4 512,213.6" fill="black" transform="rotate(0,516,208)"/> <polygon class="arrowhead" points="524,144 512,138.4 512,149.6" fill="black" transform="rotate(0,516,144)"/> <polygon class="arrowhead" points="524,112 512,106.4 512,117.6" fill="black" transform="rotate(0,516,112)"/> <polygon class="arrowhead" points="460,176 448,170.4 448,181.6" fill="black" transform="rotate(180,452,176)"/> <polygon class="arrowhead" points="436,176 424,170.4 424,181.6" fill="black" transform="rotate(0,428,176)"/> <polygon class="arrowhead" points="396,176 384,170.4 384,181.6" fill="black" transform="rotate(180,388,176)"/> <polygon class="arrowhead" points="372,176 360,170.4 360,181.6" fill="black" transform="rotate(0,364,176)"/> <polygon class="arrowhead" points="348,176 336,170.4 336,181.6" fill="black" transform="rotate(180,340,176)"/> <polygon class="arrowhead" points="324,176 312,170.4 312,181.6" fill="black" transform="rotate(0,316,176)"/> <polygon class="arrowhead" points="276,176 264,170.4 264,181.6" fill="black" transform="rotate(180,268,176)"/> <polygon class="arrowhead" points="252,176 240,170.4 240,181.6" fill="black" transform="rotate(0,244,176)"/> <polygon class="arrowhead" points="228,176 216,170.4 216,181.6" fill="black" transform="rotate(180,220,176)"/> <polygon class="arrowhead" points="204,176 192,170.4 192,181.6" fill="black" transform="rotate(0,196,176)"/> <polygon class="arrowhead" points="164,176 152,170.4 152,181.6" fill="black" transform="rotate(180,156,176)"/> <polygon class="arrowhead" points="140,176 128,170.4 128,181.6" fill="black" transform="rotate(0,132,176)"/> <polygon class="arrowhead" points="76,240 64,234.4 64,245.6" fill="black" transform="rotate(180,68,240)"/> <polygon class="arrowhead" points="76,208 64,202.4 64,213.6" fill="black" transform="rotate(180,68,208)"/> <polygon class="arrowhead" points="76,144 64,138.4 64,149.6" fill="black" transform="rotate(180,68,144)"/> <polygon class="arrowhead" points="76,112 64,106.4 64,117.6" fill="black" transform="rotate(180,68,112)"/> <circle cx="40" cy="352" r="6" class="closeddot" fill="black"/> <circle cx="40" cy="368" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="56" cy="112" r="6" class="closeddot" fill="black"/> <circle cx="56" cy="144" r="6" class="closeddot" fill="black"/> <circle cx="56" cy="208" r="6" class="closeddot" fill="black"/> <circle cx="56" cy="240" r="6" class="closeddot" fill="black"/> <circle cx="144" cy="176" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="208" cy="176" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="256" cy="176" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="328" cy="176" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="376" cy="176" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="440" cy="176" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="528" cy="112" r="6" class="closeddot" fill="black"/> <circle cx="528" cy="144" r="6" class="closeddot" fill="black"/> <circle cx="528" cy="208" r="6" class="closeddot" fill="black"/> <circle cx="528" cy="240" r="6" class="closeddot" fill="black"/> <g class="text"> <text x="292" y="36">..............................................</text> <text x="104" y="52">:</text> <text x="276" y="52">Base</text> <text x="312" y="52">NRP</text> <text x="480" y="52">:</text> <text x="104" y="68">:</text> <text x="480" y="68">:</text> <text x="76" y="84">PE</text> <text x="104" y="84">:</text> <text x="480" y="84">:</text> <text x="508" y="84">PE</text> <text x="12" y="100">--</text> <text x="36" y="100">--</text> <text x="64" y="100">-</text> <text x="84" y="100">--</text> <text x="108" y="100">--</text> <text x="132" y="100">--</text> <text x="160" y="100">-</text> <text x="180" y="100">--</text> <text x="204" y="100">--</text> <text x="228" y="100">--</text> <text x="252" y="100">--</text> <text x="276" y="100">--</text> <text x="300" y="100">--</text> <text x="324" y="100">--</text> <text x="348" y="100">--</text> <text x="372" y="100">--</text> <text x="396" y="100">--</text> <text x="420" y="100">--</text> <text x="460" y="100">--</text> <text x="484" y="100">--</text> <text x="508" y="100">--</text> <text x="16" y="116">N</text> <text x="16" y="132">S</text> <text x="16" y="148">#</text> <text x="232" y="148">P</text> <text x="352" y="148">P</text> <text x="16" y="164">1</text> <text x="12" y="180">==</text> <text x="36" y="180">==</text> <text x="16" y="196">N</text> <text x="16" y="212">S</text> <text x="16" y="228">#</text> <text x="16" y="244">2</text> <text x="12" y="260">--</text> <text x="36" y="260">--</text> <text x="64" y="260">-</text> <text x="84" y="260">--</text> <text x="108" y="260">--</text> <text x="132" y="260">--</text> <text x="156" y="260">--</text> <text x="180" y="260">--</text> <text x="204" y="260">--</text> <text x="228" y="260">--</text> <text x="252" y="260">--</text> <text x="276" y="260">--</text> <text x="300" y="260">--</text> <text x="324" y="260">--</text> <text x="348" y="260">--</text> <text x="372" y="260">--</text> <text x="396" y="260">--</text> <text x="420" y="260">--</text> <text x="460" y="260">--</text> <text x="484" y="260">--</text> <text x="508" y="260">--</text> <text x="104" y="276">:</text> <text x="480" y="276">:</text> <text x="104" y="292">:</text> <text x="480" y="292">:</text> <text x="104" y="308">:</text> <text x="480" y="308">:</text> <text x="292" y="324">'..............................................'</text> <text x="68" y="356">SDP,</text> <text x="108" y="356">with</text> <text x="180" y="356">fine-grained</text> <text x="248" y="356">QoS</text> <text x="308" y="356">(dedicated</text> <text x="392" y="356">resources</text> <text x="448" y="356">per</text> <text x="496" y="356">Network</text> <text x="556" y="356">Slice)</text> <text x="108" y="372">Coarse-grained</text> <text x="188" y="372">QoS,</text> <text x="228" y="372">with</text> <text x="288" y="372">resources</text> <text x="356" y="372">shared</text> <text x="396" y="372">by</text> <text x="424" y="372">all</text> <text x="472" y="372">Network</text> <text x="532" y="372">Slices</text> <text x="32" y="388">...</text> <text x="68" y="388">Base</text> <text x="104" y="388">NRP</text> <text x="12" y="404">--</text> <text x="36" y="404">--</text> <text x="80" y="404">Network</text> <text x="136" y="404">Slice</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ .............................................. : Base NRP : +-----:----+ +----:-----+ | PE : | | : PE | -- -- |- -- -- --| - -- -- -- -- -- -- -- -- -- -- -- | -- -- -- | N *<---+ | | +--->* S | | | +-----+ +-----+ | | | # *<---+ | | P | | P | | +--->* 1 | | | | | | | | | | == == | +---->o<----->o<--->o<------>o<--->o<----->o<----+ | N | | | | | | | | | | S *<---+ | | | | | | +--->* # | | | +-----+ +-----+ | | | 2 *<---+ | | +--->* -- -- |- -- -- --|-- -- -- -- -- -- -- -- -- -- -- -- | -- -- -- | | : | | : | +-----:----+ +----:-----+ : : '..............................................' * SDP, with fine-grained QoS (dedicated resources per Network Slice) o Coarse-grained QoS, with resources shared by all Network Slices ... Base NRP -- -- Network Slice ]]></artwork> </artset> </figure><t>P<t>The P nodes shown in <xref target="_figure-high-level-qos"/> are routers that do not interface with customer devices. See <xref section="5.3.1" sectionFormat="of" target="RFC4026"/>.</t> <t>This document does not describe in detail how to manage an L2VPN or L3VPN, as this is already well-documented. For example, the reader may refer to <xref target="RFC4176"/> and <xref target="RFC6136"/> for such details.</t> </section> </section> <section anchor="sec-handoff-domains"><name>Hand-off<name>Handoff Between Domains</name> <t>The 5G control plane relies upon 32-bit S-NSSAIs for slice identification. The S-NSSAI is not visible to the transport domain. So instead, 5G network functions can expose the 5G slices to the transport domain by mapping to explicit Layer 2 or Layer 3 identifiers, such as VLAN-IDs, IP addresses, or Differentiated Services Code Point (DSCP) values. The followingsectionssubsections list a fewhand-offhandoff methods for slice mapping between customer sites and provider networks.</t> <t>More details about the mapping between 3GPP and RFC 9543 Network Slices is provided in <xref target="I-D.ietf-teas-5g-network-slice-application"/>.</t><t><!---<!--- That document includes additional methods for mapping 5G slices to TN slices (e.g., source UDP port number), but these methods are not discussed here because of the shortcomings of these methods (e.g., load balancing, NAT). --></t><section anchor="sec-vlan-handoff"> <name>VLANHand-off</name>Handoff</name> <t>In this option, the RFC 9543 Network Slice, fulfilling connectivity requirements between NFs that belong to a 5G slice, is represented at an SDP by a VLAN ID (or double VLAN IDs, commonly known as QinQ), as depicted in <xref target="_figure-vlan-hand-off"/>.</t> <figure anchor="_figure-vlan-hand-off"> <name>Example of 5G Slice with VLANHand-offHandoff Providing End-to-End Connectivity</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="288" width="616" viewBox="0 0 616 288" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,96 L 8,192" fill="none" stroke="black"/> <path d="M 16,256 L 16,272" fill="none" stroke="black"/> <path d="M 64,96 L 64,192" fill="none" stroke="black"/> <path d="M 96,64 L 96,120" fill="none" stroke="black"/> <path d="M 128,96 L 128,192" fill="none" stroke="black"/> <path d="M 144,64 L 144,96" fill="none" stroke="black"/> <path d="M 144,192 L 144,224" fill="none" stroke="black"/> <path d="M 176,96 L 176,192" fill="none" stroke="black"/> <path d="M 264,96 L 264,192" fill="none" stroke="black"/> <path d="M 296,64 L 296,96" fill="none" stroke="black"/> <path d="M 296,192 L 296,224" fill="none" stroke="black"/> <path d="M 312,96 L 312,192" fill="none" stroke="black"/> <path d="M 344,64 L 344,120" fill="none" stroke="black"/> <path d="M 376,96 L 376,192" fill="none" stroke="black"/> <path d="M 424,96 L 424,192" fill="none" stroke="black"/> <path d="M 456,64 L 456,120" fill="none" stroke="black"/> <path d="M 488,96 L 488,192" fill="none" stroke="black"/> <path d="M 544,96 L 544,192" fill="none" stroke="black"/> <path d="M 144,64 L 296,64" fill="none" stroke="black"/> <path d="M 8,96 L 64,96" fill="none" stroke="black"/> <path d="M 128,96 L 176,96" fill="none" stroke="black"/> <path d="M 264,96 L 312,96" fill="none" stroke="black"/> <path d="M 376,96 L 424,96" fill="none" stroke="black"/> <path d="M 488,96 L 544,96" fill="none" stroke="black"/> <path d="M 64,128 L 120,128" fill="none" stroke="black"/> <path d="M 320,128 L 376,128" fill="none" stroke="black"/> <path d="M 64,144 L 120,144" fill="none" stroke="black"/> <path d="M 320,144 L 376,144" fill="none" stroke="black"/> <path d="M 64,160 L 120,160" fill="none" stroke="black"/> <path d="M 320,160 L 376,160" fill="none" stroke="black"/> <path d="M 8,192 L 64,192" fill="none" stroke="black"/> <path d="M 128,192 L 176,192" fill="none" stroke="black"/> <path d="M 264,192 L 312,192" fill="none" stroke="black"/> <path d="M 376,192 L 424,192" fill="none" stroke="black"/> <path d="M 488,192 L 544,192" fill="none" stroke="black"/> <path d="M 144,224 L 296,224" fill="none" stroke="black"/> <polygon class="arrowhead" points="464,120 452,114.4 452,125.6" fill="black" transform="rotate(90,456,120)"/> <polygon class="arrowhead" points="352,120 340,114.4 340,125.6" fill="black" transform="rotate(90,344,120)"/> <polygon class="arrowhead" points="104,120 92,114.4 92,125.6" fill="black" transform="rotate(90,96,120)"/> <circle cx="16" cy="272" r="6" class="closeddot" fill="black"/> <circle cx="136" cy="128" r="6" class="closeddot" fill="black"/> <circle cx="136" cy="144" r="6" class="closeddot" fill="black"/> <circle cx="136" cy="160" r="6" class="closeddot" fill="black"/> <circle cx="304" cy="128" r="6" class="closeddot" fill="black"/> <circle cx="304" cy="144" r="6" class="closeddot" fill="black"/> <circle cx="304" cy="160" r="6" class="closeddot" fill="black"/> <g class="text"> <text x="24" y="36">VLANs</text> <text x="100" y="36">representing</text> <text x="180" y="36">slices</text> <text x="312" y="36">VLANs</text> <text x="388" y="36">representing</text> <text x="468" y="36">slices</text> <text x="220" y="100">Provider</text> <text x="456" y="132">.......</text> <text x="28" y="148">NF</text> <text x="156" y="148">PE</text> <text x="284" y="148">PE</text> <text x="400" y="148">L2/L3</text> <text x="456" y="148">.......</text> <text x="524" y="148">NF</text> <text x="456" y="164">.......</text> <text x="100" y="196">AC</text> <text x="224" y="196">Network</text> <text x="348" y="196">AC</text> <text x="56" y="260">Logical</text> <text x="128" y="260">interface</text> <text x="216" y="260">represented</text> <text x="276" y="260">by</text> <text x="296" y="260">a</text> <text x="324" y="260">VLAN</text> <text x="356" y="260">on</text> <text x="376" y="260">a</text> <text x="420" y="260">physical</text> <text x="496" y="260">interface</text> <text x="40" y="276">SDP</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ VLANs representing slices VLANs representing slices | +------------------+ | | | | | | | +------+ | +-+---+ Provider +---+-+ | +-----+ | +------+ | | v | | | | v | | v | | | +-------+* | | *+-------+ +.......+ | | NF +-------+* PE | | PE *+-------+L2/L3+.......+ NF | | +-------+* | | *+-------+ +.......+ | | | | | | | | | | | +------+ AC +-+---+ Network +---+-+ AC +-----+ +------+ | | +------------------+ + Logical interface represented by a VLAN on a physical interface * SDP ]]></artwork> </artset> </figure> <!-- [rfced] We do not see "F2" used elsewhere in the document. Will readers understand what this refers to? Original: Since the 5G interfaces are IP-based interfaces (with an exception of the F2 fronthaul-interface, where eCPRI with Ethernet encapsulation is used), this VLAN is typically not transported across the provider network. --> <t>Each VLAN represents a distinct logical interface on theACs;ACs and henceitprovides the possibility to place these logical interfaces in distinct Layer 2 or Layer 3 service instances and implement separation between slices via service instances. Since the 5G interfaces are IP-based interfaces (withanthe exception of the F2fronthaul-interface,fronthaul interface, where eCPRI with Ethernet encapsulation is used), this VLAN is typically not transported across the provider network. Typically, it has only local significance at a particular SDP. For simplification, a deployment may rely on the same VLAN identifier for all ACs. However, that may not be always possible. As such, SDPs forathe same slice at different locations may use different VLAN values. Therefore, aVLANtable mapping VLANs to RFC 9543 NetworkSlice mapping tableSlices is maintained for each AC, and the VLAN allocation is coordinated between customer orchestration and provider orchestration.</t> <t>While VLANhand-offhandoff is simple for NFs, it adds complexity at the provider network because of the requirement of maintaining mapping tables for each SDP and performing a configuration task for new VLANs and IP subnet for every slice on every AC.</t> </section> <section anchor="sec-ip-hof"> <name>IPHand-off</name>Handoff</name> <t>In this option, an explicit mapping between source/destination IP addresses and a slice's specific S-NSSAI is used. The mapping can have either local (e.g., pertaining to a single NF attachment) or global TN significance. The mapping can be realized in multiple ways, including (but not limited to):</t> <ul spacing="normal"> <li> <t>S-NSSAI to a dedicated IP address for each NF</t> </li> <li> <t>S-NSSAI to a pool of IP addresses for global TN deployment</t> </li> <li> <t>S-NSSAI to a subset of bits of an IP address</t> </li> <li> <t>S-NSSAI to a DSCP value</t> </li> <li> <t>S-NSSAI to SRv6 Locators or Segment Identifiers (SIDs) <xref target="RFC8986"/></t> </li> <li> <t>Use of a deterministic algorithm to mapS-NSAAIS-NSSAI to an IP subnet, prefix, or pools. For example, adaptations to the algorithm defined in <xref target="RFC7422"/> may be considered.</t> </li> </ul> <t>Mapping S-NSSAIs to IP addresses makes IP addresses an identifier for slice-related policy enforcement in the Transport Network (e.g.,Differentiated Services,differentiated services, traffic steering, bandwidth allocation, security policies,orand monitoring).</t> <t>One example of the IPhand-offhandoff realization is thearrangement, wherearrangement in which the slices in the TN domain are instantiated using IP tunnels (e.g., IPsec or GTP-U tunnels) established between NFs, as depicted in <xref target="_figure-ip-hand-off"/>. The transport for a single 5G slice might be constructed with multiple such tunnels, since a typical 5G slice contains manyNFs -NFs, especially DUs and CUs. If a shared NF (i.e., an NF that serves multiple slices,for example,such as a shared DU) is deployed, multiple tunnels from the shared NF are established, each tunnel representing a single slice.</t> <figure anchor="_figure-ip-hand-off"> <name>Example of 5G Slice with IPHand-offHandoff Providing End-to-End Connectivity</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="272" width="552" viewBox="0 0 552 272" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,80 L 8,176" fill="none" stroke="black"/> <path d="M 64,80 L 64,96" fill="none" stroke="black"/> <path d="M 64,160 L 64,176" fill="none" stroke="black"/> <path d="M 128,80 L 128,96" fill="none" stroke="black"/> <path d="M 128,160 L 128,176" fill="none" stroke="black"/> <path d="M 144,48 L 144,80" fill="none" stroke="black"/> <path d="M 144,176 L 144,208" fill="none" stroke="black"/> <path d="M 176,80 L 176,96" fill="none" stroke="black"/> <path d="M 176,160 L 176,176" fill="none" stroke="black"/> <path d="M 264,80 L 264,96" fill="none" stroke="black"/> <path d="M 264,160 L 264,176" fill="none" stroke="black"/> <path d="M 296,48 L 296,80" fill="none" stroke="black"/> <path d="M 296,176 L 296,208" fill="none" stroke="black"/> <path d="M 312,80 L 312,96" fill="none" stroke="black"/> <path d="M 312,160 L 312,176" fill="none" stroke="black"/> <path d="M 376,80 L 376,96" fill="none" stroke="black"/> <path d="M 376,160 L 376,176" fill="none" stroke="black"/> <path d="M 424,80 L 424,96" fill="none" stroke="black"/> <path d="M 424,160 L 424,176" fill="none" stroke="black"/> <path d="M 456,48 L 456,96" fill="none" stroke="black"/> <path d="M 488,80 L 488,96" fill="none" stroke="black"/> <path d="M 488,160 L 488,176" fill="none" stroke="black"/> <path d="M 544,80 L 544,176" fill="none" stroke="black"/> <path d="M 144,48 L 296,48" fill="none" stroke="black"/> <path d="M 8,80 L 64,80" fill="none" stroke="black"/> <path d="M 128,80 L 176,80" fill="none" stroke="black"/> <path d="M 264,80 L 312,80" fill="none" stroke="black"/> <path d="M 376,80 L 424,80" fill="none" stroke="black"/> <path d="M 488,80 L 544,80" fill="none" stroke="black"/> <path d="M 56,110 L 144,110" fill="none" stroke="black"/> <path d="M 56,114 L 144,114" fill="none" stroke="black"/> <path d="M 160,110 L 280,110" fill="none" stroke="black"/> <path d="M 160,114 L 280,114" fill="none" stroke="black"/> <path d="M 296,110 L 496,110" fill="none" stroke="black"/> <path d="M 296,114 L 496,114" fill="none" stroke="black"/> <path d="M 64,128 L 128,128" fill="none" stroke="black"/> <path d="M 312,128 L 376,128" fill="none" stroke="black"/> <path d="M 56,142 L 144,142" fill="none" stroke="black"/> <path d="M 56,146 L 144,146" fill="none" stroke="black"/> <path d="M 160,142 L 280,142" fill="none" stroke="black"/> <path d="M 160,146 L 280,146" fill="none" stroke="black"/> <path d="M 296,142 L 496,142" fill="none" stroke="black"/> <path d="M 296,146 L 496,146" fill="none" stroke="black"/> <path d="M 8,176 L 64,176" fill="none" stroke="black"/> <path d="M 128,176 L 176,176" fill="none" stroke="black"/> <path d="M 264,176 L 312,176" fill="none" stroke="black"/> <path d="M 376,176 L 424,176" fill="none" stroke="black"/> <path d="M 488,176 L 544,176" fill="none" stroke="black"/> <path d="M 144,208 L 296,208" fill="none" stroke="black"/> <polygon class="arrowhead" points="464,96 452,90.4 452,101.6" fill="black" transform="rotate(90,456,96)"/> <circle cx="8" cy="240" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="8" cy="256" r="6" class="closeddot" fill="black"/> <circle cx="48" cy="112" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="48" cy="144" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="152" cy="112" r="6" class="closeddot" fill="black"/> <circle cx="152" cy="144" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="112" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="144" r="6" class="closeddot" fill="black"/> <circle cx="504" cy="112" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="504" cy="144" r="6" class="opendot" fill="white" stroke="black"/> <g class="text"> <text x="352" y="36">Tunnels</text> <text x="436" y="36">representing</text> <text x="516" y="36">slices</text> <text x="220" y="84">Provider</text> <text x="28" y="132">NF</text> <text x="148" y="132">PE</text> <text x="176" y="132">|</text> <text x="264" y="132">|</text> <text x="284" y="132">PE</text> <text x="436" y="132">L2/L3+.......+</text> <text x="524" y="132">NF</text> <text x="92" y="180">AC</text> <text x="224" y="180">Network</text> <text x="340" y="180">AC</text> <text x="44" y="244">Tunnel</text> <text x="104" y="244">(IPsec,</text> <text x="164" y="244">GTP-U,</text> <text x="216" y="244">etc.)</text> <text x="288" y="244">termination</text> <text x="360" y="244">point</text> <text x="32" y="260">SDP</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ Tunnels representing slices +------------------+ | | | | +------+ +-+---+ Provider +---+-+ +-----+ | +------+ | | | | | | | | v | | | o============*================*==========================o | | NF +-------+ PE | | PE +-------+L2/L3+.......+ NF | | o============*================*==========================o | | | | | | | | | | | +------+ AC +-+---+ Network +---+-+ AC +-----+ +------+ | | +------------------+ o Tunnel (IPsec, GTP-U, etc.) termination point * SDP ]]></artwork> </artset> </figure> <t>As opposed to the VLANhand-offhandoff case (<xref target="sec-vlan-handoff"/>), there is no logical interface representing a slice on thePE, hencePE; hence, all slices are handled within a single service instance. The IP and VLANhand-offshandoffs are not mutuallyexclusive,exclusive but instead could be used concurrently. Since the TN doesn't recognize S-NSSAIs, a mapping table similar to the VLANHand-offhandoff solution is needed (<xref target="sec-vlan-handoff"/>).</t> <t>The mapping table can be simplified if, for example, IPv6 addressing is used to address NFs. An IPv6 address is a 128-bitlongfield, while the S-NSSAI is a 32-bit field: The Slice/Service Type(SST):(SST) is 8 bits, and the Slice Differentiator(SD):(SD) is 24 bits.32 bits, outOut of the 128 bits of the IPv6 address, 32 bits may be used to encode the S-NSSAI, which makes anIP to SliceIP-to-slice mapping table unnecessary.</t> <t>The S-NSSAI/IPv6 mapping is a local IPv6 address allocation method to NFs not disclosed to on-path nodes. IP forwarding is not altered by this method and is still achieved following BCP 198 <xref target="RFC7608"/>. Intermediary TN nodes are not required to associate any additional semantic with the IPv6 address.</t> <t>However, operators using such mapping methods should be aware of the implications of any change of S-NSSAI on the IPv6 addressing plans. For example, modifications of the S-NSSAIsin-usein use will require updating the IP addresses used by NFs involved in the associated slices.</t> <t>AnExampleexample of a local IPv6 addressing plan for NFs is provided in <xreftarget="sec-v6-ex"/></t>target="sec-v6-ex"/>.</t> </section> <section anchor="sec-mpls-ho"> <name>MPLS LabelHand-off</name>Handoff</name> <t>In this option, the service instances representing different slices are created directly on the NF, or within the customer site hosting the NF, and attached to the provider network. Therefore, the packet is encapsulated outside the provider network with MPLS encapsulation or MPLS-in-UDP encapsulation <xref target="RFC7510"/>, depending on the capability of the customer site, with the service label depicting the slice.</t> <t>There are three major methods (based upon <xref section="10" sectionFormat="of" target="RFC4364"/>) for interconnecting MPLS services over multiple service domains:</t> <dl> <dt>Option A (<xref target="sec-10a"/>):</dt> <dd> <t>VRF-to-VRF connections.</t> </dd> <dt>Option B (<xref target="sec-10b"/>):</dt> <dd><t>redistribution<t>Redistribution of labeled VPN routes with next-hop change at domain boundaries.</t> </dd> <dt>Option C (<xref target="sec-10c"/>):</dt> <dd><t>redistribution<t>Redistribution of labeled VPN routes without next-hop change and redistribution of labeled transport routes with next-hop change at domain boundaries.</t> </dd> </dl> <t><xref target="_figure-51"/> illustrates the use of service-aware CE (<xref target="sec-ce"/>) for the deployment discussed in Sections <xref format="counter" target="sec-10b"/> and <xref format="counter" target="sec-10c"/>.</t> <figure anchor="_figure-51"> <name>Example ofMPLS-basedMPLS-Based Attachment Circuit</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="224" width="440" viewBox="0 0 440 224" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,208" fill="none" stroke="black"/> <path d="M 80,176 L 80,208" fill="none" stroke="black"/> <path d="M 104,128 L 104,176" fill="none" stroke="black"/> <path d="M 128,32 L 128,128" fill="none" stroke="black"/> <path d="M 144,128 L 144,176" fill="none" stroke="black"/> <path d="M 168,176 L 168,208" fill="none" stroke="black"/> <path d="M 296,128 L 296,192" fill="none" stroke="black"/> <path d="M 312,32 L 312,128" fill="none" stroke="black"/> <path d="M 312,192 L 312,208" fill="none" stroke="black"/> <path d="M 336,128 L 336,192" fill="none" stroke="black"/> <path d="M 432,32 L 432,208" fill="none" stroke="black"/> <path d="M 8,32 L 128,32" fill="none" stroke="black"/> <path d="M 312,32 L 432,32" fill="none" stroke="black"/> <path d="M 152,112 L 200,112" fill="none" stroke="black"/> <path d="M 256,112 L 296,112" fill="none" stroke="black"/> <path d="M 104,128 L 144,128" fill="none" stroke="black"/> <path d="M 296,128 L 336,128" fill="none" stroke="black"/> <path d="M 144,160 L 296,160" fill="none" stroke="black"/> <path d="M 80,176 L 168,176" fill="none" stroke="black"/> <path d="M 296,192 L 336,192" fill="none" stroke="black"/> <path d="M 8,208 L 168,208" fill="none" stroke="black"/> <path d="M 312,208 L 432,208" fill="none" stroke="black"/> <polygon class="arrowhead" points="304,112 292,106.4 292,117.6" fill="black" transform="rotate(0,296,112)"/> <polygon class="arrowhead" points="160,112 148,106.4 148,117.6" fill="black" transform="rotate(180,152,112)"/> <g class="text"> <text x="68" y="52">Customer</text> <text x="372" y="52">Provider</text> <text x="68" y="68">Site</text> <text x="376" y="68">Network</text> <text x="228" y="116">MP-BGP</text> <text x="212" y="148">MPLS-based</text> <text x="268" y="148">AC</text> <text x="124" y="164">CE</text> <text x="316" y="164">PE</text> <text x="104" y="196">VRF</text> <text x="136" y="196">foo</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +--------------+ +--------------+ | Customer | | Provider | | Site | | Network | | | | | | | | | | | <------MP-BGP-----> | | | +--+-+ +-+--+ | | | | MPLS-based AC | | | | | CE +------------------+ PE | | | +--+----+--+ | | | | | VRF foo | +-+--+ | +--------+----------+ +--------------+ ]]></artwork> </artset> </figure> <section anchor="sec-10a"> <name>Option A</name> <t>This option isnotbased onMPLS label hand-off, butthe VLANhand-off,handoff, described in <xreftarget="sec-vlan-handoff"/>.</t>target="sec-vlan-handoff"/>; it is not based on the MPLS label handoff.</t> </section> <section anchor="sec-10b"> <name>Option B</name> <!-- [rfced] Please confirm that "compute" (noun) is the correct word choice here. Original: These L3VPN service instances are instantiated in the customer site which could be, for example, either on the compute that hosts mobile NFs (Figure 15, left-hand side) or within the DC/ cloud infrastructure itself (e.g., on the top of the rack or leaf switch within cloud IP fabric (Figure 15, right-hand side)). --> <t>In this option, L3VPN service instances are instantiated outside the provider network. These L3VPN service instances are instantiated in the customersitesite, which could be, for example, either on the compute that hosts mobile NFs (<xref target="_figure-mpls-10b-hand-off"/>, left-hand side) or within the DC/cloud infrastructure itself (e.g., on the top of the rack or leaf switch within cloud IP fabric (<xref target="_figure-mpls-10b-hand-off"/>, right-hand side)). On the AC connected to a PE, packets are already MPLS encapsulated (or MPLS-in-UDP/MPLS-in-IP encapsulated, if cloud or compute infrastructure don't support MPLS encapsulation). Therefore, the PE uses neither a VLAN nor an IP address for slice identification at theSDP,SDP but instead uses the MPLS label.</t> <figure anchor="_figure-mpls-10b-hand-off"> <name>Example of MPLSHand-offHandoff with Option B</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="416" width="568" viewBox="0 0 568 416" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,208 L 8,336" fill="none" stroke="black"/> <path d="M 24,240 L 24,304" fill="none" stroke="black"/> <path d="M 40,208 L 40,240" fill="none" stroke="black"/> <path d="M 48,304 L 48,336" fill="none" stroke="black"/> <path d="M 64,192 L 64,240" fill="none" stroke="black"/> <path d="M 80,240 L 80,304" fill="none" stroke="black"/> <path d="M 136,240 L 136,304" fill="none" stroke="black"/> <path d="M 152,208 L 152,240" fill="none" stroke="black"/> <path d="M 152,304 L 152,336" fill="none" stroke="black"/> <path d="M 184,240 L 184,304" fill="none" stroke="black"/> <path d="M 248,240 L 248,304" fill="none" stroke="black"/> <path d="M 272,208 L 272,240" fill="none" stroke="black"/> <path d="M 280,304 L 280,336" fill="none" stroke="black"/> <path d="M 296,240 L 296,304" fill="none" stroke="black"/> <path d="M 352,240 L 352,304" fill="none" stroke="black"/> <path d="M 368,208 L 368,240" fill="none" stroke="black"/> <path d="M 368,304 L 368,336" fill="none" stroke="black"/> <path d="M 384,192 L 384,240" fill="none" stroke="black"/> <path d="M 456,192 L 456,248" fill="none" stroke="black"/> <path d="M 528,240 L 528,304" fill="none" stroke="black"/> <path d="M 544,208 L 544,336" fill="none" stroke="black"/> <path d="M 48,32 L 96,32" fill="none" stroke="black"/> <path d="M 168,32 L 216,32" fill="none" stroke="black"/> <path d="M 288,32 L 336,32" fill="none" stroke="black"/> <path d="M 48,112 L 392,112" fill="none" stroke="black"/> <path d="M 8,208 L 40,208" fill="none" stroke="black"/> <path d="M 152,208 L 272,208" fill="none" stroke="black"/> <path d="M 392,208 L 448,208" fill="none" stroke="black"/> <path d="M 464,208 L 544,208" fill="none" stroke="black"/> <path d="M 24,240 L 56,240" fill="none" stroke="black"/> <path d="M 136,240 L 184,240" fill="none" stroke="black"/> <path d="M 248,240 L 296,240" fill="none" stroke="black"/> <path d="M 352,240 L 376,240" fill="none" stroke="black"/> <path d="M 392,240 L 424,240" fill="none" stroke="black"/> <path d="M 480,240 L 528,240" fill="none" stroke="black"/> <path d="M 80,272 L 128,272" fill="none" stroke="black"/> <path d="M 304,272 L 352,272" fill="none" stroke="black"/> <path d="M 24,304 L 80,304" fill="none" stroke="black"/> <path d="M 136,304 L 184,304" fill="none" stroke="black"/> <path d="M 248,304 L 296,304" fill="none" stroke="black"/> <path d="M 352,304 L 424,304" fill="none" stroke="black"/> <path d="M 480,304 L 528,304" fill="none" stroke="black"/> <path d="M 8,336 L 48,336" fill="none" stroke="black"/> <path d="M 152,336 L 280,336" fill="none" stroke="black"/> <path d="M 368,336 L 544,336" fill="none" stroke="black"/> <polygon class="arrowhead" points="464,248 452,242.4 452,253.6" fill="black" transform="rotate(90,456,248)"/> <polygon class="arrowhead" points="400,112 388,106.4 388,117.6" fill="black" transform="rotate(0,392,112)"/> <polygon class="arrowhead" points="392,240 380,234.4 380,245.6" fill="black" transform="rotate(90,384,240)"/> <polygon class="arrowhead" points="296,32 284,26.4 284,37.6" fill="black" transform="rotate(180,288,32)"/> <polygon class="arrowhead" points="288,112 276,106.4 276,117.6" fill="black" transform="rotate(180,280,112)"/> <polygon class="arrowhead" points="280,112 268,106.4 268,117.6" fill="black" transform="rotate(0,272,112)"/> <polygon class="arrowhead" points="176,112 164,106.4 164,117.6" fill="black" transform="rotate(180,168,112)"/> <polygon class="arrowhead" points="176,32 164,26.4 164,37.6" fill="black" transform="rotate(180,168,32)"/> <polygon class="arrowhead" points="168,112 156,106.4 156,117.6" fill="black" transform="rotate(0,160,112)"/> <polygon class="arrowhead" points="72,240 60,234.4 60,245.6" fill="black" transform="rotate(90,64,240)"/> <polygon class="arrowhead" points="56,112 44,106.4 44,117.6" fill="black" transform="rotate(180,48,112)"/> <polygon class="arrowhead" points="56,32 44,26.4 44,37.6" fill="black" transform="rotate(180,48,32)"/> <circle cx="24" cy="400" r="6" class="closeddot" fill="black"/> <circle cx="144" cy="256" r="6" class="closeddot" fill="black"/> <circle cx="144" cy="272" r="6" class="closeddot" fill="black"/> <circle cx="144" cy="288" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="256" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="272" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="288" r="6" class="closeddot" fill="black"/> <g class="text"> <text x="56" y="52">BGP</text> <text x="88" y="52">VPN</text> <text x="176" y="52">BGP</text> <text x="208" y="52">VPN</text> <text x="296" y="52">BGP</text> <text x="328" y="52">VPN</text> <text x="84" y="68">COM=1,</text> <text x="132" y="68">L=A"</text> <text x="204" y="68">COM=1,</text> <text x="252" y="68">L=A'</text> <text x="324" y="68">COM=1,</text> <text x="368" y="68">L=A</text> <text x="84" y="84">COM=2,</text> <text x="132" y="84">L=B"</text> <text x="204" y="84">COM=2,</text> <text x="252" y="84">L=B'</text> <text x="324" y="84">COM=2,</text> <text x="368" y="84">L=B</text> <text x="84" y="100">COM=3,</text> <text x="132" y="100">L=C"</text> <text x="204" y="100">COM=3,</text> <text x="252" y="100">L=C'</text> <text x="324" y="100">COM=3,</text> <text x="368" y="100">L=C</text> <text x="136" y="132">nhs</text> <text x="176" y="132">nhs</text> <text x="248" y="132">nhs</text> <text x="288" y="132">nhs</text> <text x="472" y="148">VLANs</text> <text x="32" y="164">service</text> <text x="104" y="164">instances</text> <text x="296" y="164">service</text> <text x="368" y="164">instances</text> <text x="468" y="164">representing</text> <text x="52" y="180">representing</text> <text x="132" y="180">slices</text> <text x="316" y="180">representing</text> <text x="396" y="180">slices</text> <text x="476" y="180">slices</text> <text x="376" y="212">-</text> <text x="228" y="228">Provider</text> <text x="72" y="244">-</text> <text x="64" y="260">#</text> <text x="432" y="260">#<><>x......x</text> <text x="44" y="276">NF</text> <text x="64" y="276">#</text> <text x="164" y="276">PE</text> <text x="268" y="276">PE</text> <text x="432" y="276">#<><>x......x</text> <text x="508" y="276">NF</text> <text x="64" y="292">#</text> <text x="116" y="292">AC</text> <text x="332" y="292">AC</text> <text x="432" y="292">#<><>x......x</text> <text x="32" y="324">CS1</text> <text x="216" y="324">Network</text> <text x="400" y="324">L2/L3</text> <text x="464" y="324">CS2</text> <text x="24" y="372">x</text> <text x="64" y="372">Logical</text> <text x="136" y="372">interface</text> <text x="224" y="372">represented</text> <text x="284" y="372">by</text> <text x="304" y="372">a</text> <text x="332" y="372">VLAN</text> <text x="364" y="372">on</text> <text x="384" y="372">a</text> <text x="428" y="372">physical</text> <text x="504" y="372">interface</text> <text x="24" y="388">#</text> <text x="64" y="388">Service</text> <text x="136" y="388">instances</text> <text x="200" y="388">(with</text> <text x="252" y="388">unique</text> <text x="300" y="388">MPLS</text> <text x="352" y="388">labels)</text> <text x="48" y="404">SDP</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ <------ <------ <------ BGP VPN BGP VPN BGP VPN COM=1, L=A" COM=1, L=A' COM=1, L=A COM=2, L=B" COM=2, L=B' COM=2, L=B COM=3, L=C" COM=3, L=C' COM=3, L=C <-------------><------------><-------------> nhs nhs nhs nhs VLANs service instances service instances representing representing slices representing slices slices | | | +---+ | +--------------+ +-|--------|----------+ | | | | Provider | | | | | | +-+--v-+ +-+---+ +--+--+ +-+-v----+ v +-----+ | | | # | |* | | *| | #<><>x......x | | | | NF # +------+* PE | | PE *+------+ #<><>x......x NF | | | | # | AC |* | | *| AC | #<><>x......x | | | +--+---+ +-+---+ +---+-+ +-+------+ +-----+ | | CS1| | Network | | L2/L3 CS2 | +----+ +---------------+ +---------------------+ x Logical interface represented by a VLAN on a physical interface # Service instances (with unique MPLS labels) * SDP ]]></artwork> </artset> </figure> <!-- [rfced] Should "COM-1" here be updated to "COM=1" to match the usage in Figure 15? Original: For example, in Figure 15, for the slice identified with COM-1, the PE advertises a dynamically allocated label A". Perhaps: For example, in Figure 15, for the slice identified with COM=1, the PE advertises a dynamically allocated label A". --> <t>MPLS labels are allocated dynamically in Option B deployments,wherewhere, at the domainboundariesboundaries, service prefixes are reflected with next-hopself,self (nhs), and a new label is dynamically allocated, asvisibleshown in <xref target="_figure-mpls-10b-hand-off"/> (e.g., labels A, A', and A" for the first depicted slice). Therefore, for any slice-specific per-hop behavior at the provider network edge, the PE needs to determine which label represents which slice. In the BGP control plane, when exchanging service prefixes over an AC, each slice might be represented by a unique BGP community, so tracking label assignment to the slice might be possible. For example, in <xref target="_figure-mpls-10b-hand-off"/>, for the slice identified with COM-1, the PE advertises a dynamically allocated label A". Since, based on the community, thelabel to slicelabel-to-slice association is known, the PE can use this dynamically allocated label A" to identify incoming packets as belonging to "slice 1" and execute appropriate edge per-hop behavior.</t> <t>It is worth noting that slice identification in the BGP control plane might be with per-prefix granularity. In the extreme case, each prefix can have a different community representing a different slice. Depending on the business requirements, each slice could be represented by a different service instance as outlined in <xref target="_figure-mpls-10b-hand-off"/>. In that case, the route target extended community (<xref section="4" sectionFormat="of" target="RFC4360"/>) might be used as a slice differentiator. In other deployments, all prefixes (representing different slices) might be handled by a single'mobile'"mobile" service instance, and some other BGP attribute (e.g., a standard community <xref target="RFC1997"/>) might be used for slice differentiation. There couldbealso be a deployment option that groups multiple slices together into a single service instance, resulting in a handful of service instances. In any case, fine-grained per-hop behavior at the edge of provider network is possible.</t> </section> <section anchor="sec-10c"> <name>Option C</name> <t>Option B relies upon exchanging service prefixes between customer sites and the provider network. This may lead to scaling challenges inlarge scalelarge-scale 5G deployments as the PE node needs to carry all service prefixes. To alleviate this scaling challenge, in Option C, service prefixes are exchanged between customer sites only. In doing so, the provider network is offloaded from carrying, propagating, andprogramingprogramming appropriate forwarding entries for service prefixes.</t> <t>Option C relies upon exchanging service prefixes via multi-hop BGP sessions between customer sites, without changing the NEXT_HOP BGP attribute. Additionally, IPv4/IPv6 labeled unicast (SAFI-4) host routes, used as NEXT_HOP for service prefixes, are exchanged via direct single-hop BGP sessions between adjacent nodes in a customer site and a provider network, as depicted in <xref target="_figure-mpls-10c-hand-off"/>. As a result, a node in a customer site performs hierarchical next-hop resolution.</t> <figure anchor="_figure-mpls-10c-hand-off"><name>MPLS Hand-off<name>Example of MPLS Handoff with Option C</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="496" width="552" viewBox="0 0 552 496" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,288 L 8,416" fill="none" stroke="black"/> <path d="M 24,320 L 24,384" fill="none" stroke="black"/> <path d="M 40,288 L 40,320" fill="none" stroke="black"/> <path d="M 48,384 L 48,416" fill="none" stroke="black"/> <path d="M 56,272 L 56,320" fill="none" stroke="black"/> <path d="M 72,320 L 72,384" fill="none" stroke="black"/> <path d="M 136,320 L 136,384" fill="none" stroke="black"/> <path d="M 152,288 L 152,320" fill="none" stroke="black"/> <path d="M 152,384 L 152,416" fill="none" stroke="black"/> <path d="M 184,320 L 184,384" fill="none" stroke="black"/> <path d="M 248,320 L 248,384" fill="none" stroke="black"/> <path d="M 272,288 L 272,320" fill="none" stroke="black"/> <path d="M 280,384 L 280,416" fill="none" stroke="black"/> <path d="M 296,320 L 296,384" fill="none" stroke="black"/> <path d="M 352,320 L 352,384" fill="none" stroke="black"/> <path d="M 368,288 L 368,320" fill="none" stroke="black"/> <path d="M 368,384 L 368,416" fill="none" stroke="black"/> <path d="M 384,272 L 384,320" fill="none" stroke="black"/> <path d="M 456,272 L 456,328" fill="none" stroke="black"/> <path d="M 528,320 L 528,384" fill="none" stroke="black"/> <path d="M 544,288 L 544,416" fill="none" stroke="black"/> <path d="M 48,32 L 392,32" fill="none" stroke="black"/> <path d="M 48,112 L 392,112" fill="none" stroke="black"/> <path d="M 56,144 L 104,144" fill="none" stroke="black"/> <path d="M 176,144 L 224,144" fill="none" stroke="black"/> <path d="M 296,144 L 344,144" fill="none" stroke="black"/> <path d="M 48,192 L 392,192" fill="none" stroke="black"/> <path d="M 8,288 L 40,288" fill="none" stroke="black"/> <path d="M 152,288 L 272,288" fill="none" stroke="black"/> <path d="M 392,288 L 448,288" fill="none" stroke="black"/> <path d="M 464,288 L 544,288" fill="none" stroke="black"/> <path d="M 24,320 L 48,320" fill="none" stroke="black"/> <path d="M 136,320 L 184,320" fill="none" stroke="black"/> <path d="M 248,320 L 296,320" fill="none" stroke="black"/> <path d="M 352,320 L 376,320" fill="none" stroke="black"/> <path d="M 392,320 L 424,320" fill="none" stroke="black"/> <path d="M 480,320 L 528,320" fill="none" stroke="black"/> <path d="M 72,352 L 128,352" fill="none" stroke="black"/> <path d="M 304,352 L 352,352" fill="none" stroke="black"/> <path d="M 24,384 L 72,384" fill="none" stroke="black"/> <path d="M 136,384 L 184,384" fill="none" stroke="black"/> <path d="M 248,384 L 296,384" fill="none" stroke="black"/> <path d="M 352,384 L 424,384" fill="none" stroke="black"/> <path d="M 480,384 L 528,384" fill="none" stroke="black"/> <path d="M 8,416 L 48,416" fill="none" stroke="black"/> <path d="M 152,416 L 280,416" fill="none" stroke="black"/> <path d="M 368,416 L 544,416" fill="none" stroke="black"/> <polygon class="arrowhead" points="464,328 452,322.4 452,333.6" fill="black" transform="rotate(90,456,328)"/> <polygon class="arrowhead" points="400,192 388,186.4 388,197.6" fill="black" transform="rotate(0,392,192)"/> <polygon class="arrowhead" points="400,112 388,106.4 388,117.6" fill="black" transform="rotate(0,392,112)"/> <polygon class="arrowhead" points="392,320 380,314.4 380,325.6" fill="black" transform="rotate(90,384,320)"/> <polygon class="arrowhead" points="304,144 292,138.4 292,149.6" fill="black" transform="rotate(180,296,144)"/> <polygon class="arrowhead" points="288,192 276,186.4 276,197.6" fill="black" transform="rotate(180,280,192)"/> <polygon class="arrowhead" points="280,192 268,186.4 268,197.6" fill="black" transform="rotate(0,272,192)"/> <polygon class="arrowhead" points="184,144 172,138.4 172,149.6" fill="black" transform="rotate(180,176,144)"/> <polygon class="arrowhead" points="176,192 164,186.4 164,197.6" fill="black" transform="rotate(180,168,192)"/> <polygon class="arrowhead" points="168,192 156,186.4 156,197.6" fill="black" transform="rotate(0,160,192)"/> <polygon class="arrowhead" points="64,320 52,314.4 52,325.6" fill="black" transform="rotate(90,56,320)"/> <polygon class="arrowhead" points="64,144 52,138.4 52,149.6" fill="black" transform="rotate(180,56,144)"/> <polygon class="arrowhead" points="56,192 44,186.4 44,197.6" fill="black" transform="rotate(180,48,192)"/> <polygon class="arrowhead" points="56,112 44,106.4 44,117.6" fill="black" transform="rotate(180,48,112)"/> <polygon class="arrowhead" points="56,32 44,26.4 44,37.6" fill="black" transform="rotate(180,48,32)"/> <circle cx="32" cy="480" r="6" class="closeddot" fill="black"/> <circle cx="144" cy="336" r="6" class="closeddot" fill="black"/> <circle cx="144" cy="352" r="6" class="closeddot" fill="black"/> <circle cx="144" cy="368" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="336" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="352" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="368" r="6" class="closeddot" fill="black"/> <g class="text"> <text x="120" y="52">BGP</text> <text x="152" y="52">VPN</text> <text x="148" y="68">COM=1,</text> <text x="196" y="68">L=A,</text> <text x="268" y="68">NEXT_HOP=CS2</text> <text x="148" y="84">COM=2,</text> <text x="196" y="84">L=B,</text> <text x="268" y="84">NEXT_HOP=CS2</text> <text x="148" y="100">COM=3,</text> <text x="196" y="100">L=C,</text> <text x="268" y="100">NEXT_HOP=CS2</text> <text x="64" y="164">BGP</text> <text x="92" y="164">LU</text> <text x="184" y="164">BGP</text> <text x="212" y="164">LU</text> <text x="304" y="164">BGP</text> <text x="332" y="164">LU</text> <text x="84" y="180">CS2,</text> <text x="124" y="180">L=X"</text> <text x="204" y="180">CS2,</text> <text x="244" y="180">L=X'</text> <text x="324" y="180">CS2,</text> <text x="360" y="180">L=X</text> <text x="144" y="212">nhs</text> <text x="184" y="212">nhs</text> <text x="256" y="212">nhs</text> <text x="296" y="212">nhs</text> <text x="472" y="228">VLANs</text> <text x="32" y="244">service</text> <text x="104" y="244">instances</text> <text x="296" y="244">service</text> <text x="368" y="244">instances</text> <text x="468" y="244">representing</text> <text x="52" y="260">representing</text> <text x="132" y="260">slices</text> <text x="316" y="260">representing</text> <text x="396" y="260">slices</text> <text x="476" y="260">slices</text> <text x="376" y="292">-</text> <text x="228" y="308">Provider</text> <text x="64" y="324">-</text> <text x="56" y="340">#</text> <text x="432" y="340">#<><>x......x</text> <text x="36" y="356">NF</text> <text x="56" y="356">#</text> <text x="164" y="356">PE</text> <text x="268" y="356">PE</text> <text x="432" y="356">#<><>x......x</text> <text x="508" y="356">NF</text> <text x="56" y="372">#</text> <text x="108" y="372">AC</text> <text x="332" y="372">AC</text> <text x="432" y="372">#<><>x......x</text> <text x="32" y="404">CS1</text> <text x="232" y="404">Network</text> <text x="400" y="404">L2/L3</text> <text x="464" y="404">CS2</text> <text x="32" y="452">x</text> <text x="72" y="452">Logical</text> <text x="144" y="452">interface</text> <text x="232" y="452">represented</text> <text x="292" y="452">by</text> <text x="312" y="452">a</text> <text x="340" y="452">VLAN</text> <text x="372" y="452">on</text> <text x="392" y="452">a</text> <text x="436" y="452">physical</text> <text x="512" y="452">interface</text> <text x="32" y="468">#</text> <text x="72" y="468">Service</text> <text x="144" y="468">instances</text> <text x="208" y="468">(with</text> <text x="260" y="468">unique</text> <text x="308" y="468">MPLS</text> <text x="356" y="468">label)</text> <text x="56" y="484">SDP</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ <------------------------------------------- BGP VPN COM=1, L=A, NEXT_HOP=CS2 COM=2, L=B, NEXT_HOP=CS2 COM=3, L=C, NEXT_HOP=CS2 <------------------------------------------> <------ <------ <------ BGP LU BGP LU BGP LU CS2, L=X" CS2, L=X' CS2, L=X <-------------><------------><-------------> nhs nhs nhs nhs VLANs service instances service instances representing representing slices representing slices slices | | | +---+ | +--------------+ +-|--------|----------+ | | | | Provider | | | | | | +-+-v-+ +-+---+ +--+--+ +-+-v----+ v +-----+ | | | # | |* | | *| | #<><>x......x | | | |NF # +-------+* PE | | PE *+------+ #<><>x......x NF | | | | # | AC |* | | *| AC | #<><>x......x | | | +--+--+ +-+---+ +---+-+ +-+------+ +-----+ | | CS1| | Network | | L2/L3 CS2 | +----+ +---------------+ +---------------------+ x Logical interface represented by a VLAN on a physical interface # Service instances (with unique MPLS label) * SDP ]]></artwork> </artset> </figure> <!--[rfced] Please clarify "label swap forwarding entries" in this sentence. Original: Appropriate label swap forwarding entries for IPv4/IPv6 labeled unicast labels are programmed in the data plane. Perhaps: Appropriate label swaps of forwarding entries for IPv4/IPv6 labeled unicast labels are programmed in the data plane. Or: Appropriate forwarding entries for label swaps for IPv4/IPv6 labeled unicast labels are programmed in the data plane. --> <t>This architecture requires an end-to-end Label Switched Path (LSP) leading from a packet's ingress node inside one customer site to its egress inside another customer site, through a provider network. Hence, at the domain (customersite,site and provider network)boundariesboundaries, the NEXT_HOP attribute for IPv4/IPv6 labeled unicast needs to be modified to"next-hop self"next-hop self (nhs), which results in a new IPv4/IPv6 labeled unicast label allocation. Appropriate label swap forwarding entries for IPv4/IPv6 labeled unicast labels are programmed in the data plane. There is no additional'labeled transport'"labeled transport" protocol on the AC (e.g., no LDP, RSVP, or SR).</t> <!-- [rfced] How does the text starting with "used as NEXT_HOP..." connect to the rest of the sentence? Original: This significantly lowers the scaling pressure on PEs, as PEs need to program forwarding entries only for IPv4/IPv6 labeled unicast host routes, used as NEXT_HOP for service prefixes. Perhaps: This significantly lowers the scaling pressure on PEs, as PEs need to program forwarding entries only for IPv4/IPv6 labeled unicast host routes, which are used as NEXT_HOP for service prefixes. --> <t>Packets are transmitted over the AC with the IPv4/IPv6 labeled unicast as the top label, with the service label deeper in the label stack. In Option C, the service label is not used for forwarding lookup on the PE. This significantly lowers the scaling pressure on PEs, as PEs need to program forwarding entries only for IPv4/IPv6 labeled unicast host routes, used as NEXT_HOP for service prefixes. Also, since one IPv4/IPv6 labeled unicast host routerepresentrepresents one customer site, regardless of the number of slices in the customer site, the number of forwarding entries on a PE is considerably reduced.</t> <t>For any slice-specific per-hop behavior at the provider network edge, as described indetailsdetail in <xref target="sec-over-rea-model"/>, the PE needs to determine which label in the packet represents which slice. This can be achieved, for example, by allocating non-overlapping service label ranges for eachslice,slice anduse theseusing those ranges for slice identification purposes on the PE.</t> </section> </section> </section> <section anchor="sec-qos-map"> <name>QoS Mapping Realization Models</name> <section anchor="sec-qos-layers"> <name>QoS Layers</name> <t>The resources are managed via various QoS policies deployed in the network. QoS mapping models to support 5G slicing connectivity implemented over a packet switched provider networkusesuse two layers ofQoS thatQoS, which are discussed in<xref target="sec-qos-layers"/>.</t>the following subsections.</t> <section anchor="g-qos-layer"> <name>5G QoS Layer</name> <t>QoS treatment is indicated in the 5G QoS layer by the 5G QoS Indicator (5QI), as defined in <xref target="TS-23.501"/>.AThe 5QI is an identifier that is used as a reference to 5G QoS characteristics (e.g., scheduling weights, admission thresholds, queue management thresholds, andlink layerlink-layer protocol configuration) in the RAN domain. Given that 5QI applies to the RAN domain, it is not visible to the provider network. Therefore, if 5QI-aware treatment is desired in the providernetwork as well,network, 5G network functions might set DSCP with a value representing 5QI so that differentiated treatment can be implemented in the provider network as well. Based on these DSCP values, very granular QoS enforcement might be implemented at the SDP of each provider network segment used to construct transport for given 5Gslice, very granular QoS enforcement might be implemented.</t>slice.</t> <t>The exact mapping between 5QI and DSCP is out of scope for this document. Mapping recommendations are documented, e.g., in <xref target="I-D.cbs-teas-5qi-to-dscp-mapping"/>.</t> <t>Each slice service might have flows with multiple 5QIs. 5QIs (or, more precisely, corresponding DSCP values) are visible to the provider network at SDPs (i.e., at the edge of the provider network).</t> <t>In this document, this layer of QoS is referred to as'5G"5G QoSClass' ('5G QoS'Class" ("5G QoS" in short) or'5G DSCP'.</t>"5G DSCP".</t> </section> <section anchor="transport-network-tn-qos-layer"> <name>Transport Network (TN) QoS Layer</name> <t>Control of the TN resourceson provider network transit links, as well asand traffic scheduling/prioritization on provider network transitlinks, islinks are based on a flat (non-hierarchical) QoS model in this Network Slice realization. That is, RFC 9543 Network Slices are assigned dedicated resources (e.g., QoS queues) at the edge of the provider network (at SDPs), while all RFC 9543 Network Slices are sharing resources (sharing QoS queues) on the transit links of the provider network. Typical router hardware can support up to 8 traffic queues perport, therefore theport; therefore, this document assumes support for 8 traffic queues per portsupportin general.</t> <t>At this layer, QoS treatment is indicated by a QoS indicator specific to the encapsulation used in the provider network. Such an indicator may be a DSCP or MPLS Traffic Class (TC). This layer of QoS is referred to as'TN"TN QoSClass', or 'TN QoS'Class" ("TN QoS" forshort,short) in this document.</t> </section> </section> <section anchor="qos-realization-models"> <name>QoS Realization Models</name> <t>While 5QI might be exposed to the provider network via the DSCP value (corresponding to a specific 5QI value) set in the IP packet generated by NFs, some 5G deployments might use 5QI in the RAN domain only, without requesting per-5QI differentiated treatment from the provider network. This might be due to an NF limitation (e.g., no capability to set DSCP), or it might simply depend on the overall slicing deployment model. The O-RAN Alliance, for example, defines a phased approach to the slicing, with initial phases utilizing only per-slice, but not per-5QI, differentiated treatment in the TN domain(Annex(see Annex F of <xref target="O-RAN.WG9.XPSAAS"/>).</t> <t>Therefore, from a QoS perspective, the 5G slicing connectivity realization defines two high-level realization models for slicing in the TN domain: a 5QI-unaware model and a5QI- aware5QI-aware model. Both slicing models in the TN domain could be used concurrently within the same 5G slice. For example, the TN segment for 5G midhaul (F1-U interface) might be 5QI-aware, while at the sametimetime, the TN segment for 5G backhaul (N3 interface) might follow the 5QI-unaware model.</t> <t>These models are further elaborated in the following two subsections.</t> <section anchor="sec-5QI-unaware"><name>5QI-unaware<name>5QI-Unaware Model</name> <t>In the 5QI-unawaremode,model, the DSCP values in the packets received from NF at SDP are ignored. In the provider network, there is no QoS differentiation at the 5G QoS Class level. The entire RFC 9543 Network Slice is mapped to a single TN QoSClass, and, therefore,Class and therefore to a single QoS queue on the routers in the provider network. With afewlow number of deployed 5G slices (for example, only two 5G slices: eMBB and MIoT), it is possible to dedicate a separate QoS queue for each slice on transit routers in the provider network. However, with the introduction of private/enterprises slices, as the number of 5G slices (and thus the corresponding RFC 9543 Network Slices) increases, a single QoS queue on transit links in the provider network serves multiple slices with similar characteristics. QoS enforcement on transit links is fully coarse-grained (single NRP, sharing resources among all RFC 9543 Network Slices), as displayed in <xref target="_figure-QoS-5QI-unaware"/>.</t> <figure anchor="_figure-QoS-5QI-unaware"><name>Slice<name>Mapping of Slice to TN QoSMapping (5QI-unaware(5QI-Unaware Model)</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="624" width="560" viewBox="0 0 560 624" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,560" fill="none" stroke="black"/> <path d="M 24,80 L 24,144" fill="none" stroke="black"/> <path d="M 24,176 L 24,240" fill="none" stroke="black"/> <path d="M 24,272 L 24,336" fill="none" stroke="black"/> <path d="M 24,368 L 24,432" fill="none" stroke="black"/> <path d="M 24,464 L 24,528" fill="none" stroke="black"/> <path d="M 48,96 L 48,128" fill="none" stroke="black"/> <path d="M 48,192 L 48,224" fill="none" stroke="black"/> <path d="M 48,288 L 48,320" fill="none" stroke="black"/> <path d="M 48,384 L 48,416" fill="none" stroke="black"/> <path d="M 48,480 L 48,512" fill="none" stroke="black"/> <path d="M 136,96 L 136,128" fill="none" stroke="black"/> <path d="M 136,192 L 136,224" fill="none" stroke="black"/> <path d="M 136,288 L 136,320" fill="none" stroke="black"/> <path d="M 136,384 L 136,416" fill="none" stroke="black"/> <path d="M 136,480 L 136,512" fill="none" stroke="black"/> <path d="M 152,64 L 152,104" fill="none" stroke="black"/> <path d="M 152,160 L 152,200" fill="none" stroke="black"/> <path d="M 152,256 L 152,296" fill="none" stroke="black"/> <path d="M 152,352 L 152,392" fill="none" stroke="black"/> <path d="M 152,448 L 152,488" fill="none" stroke="black"/> <path d="M 168,48 L 168,104" fill="none" stroke="black"/> <path d="M 168,120 L 168,200" fill="none" stroke="black"/> <path d="M 168,216 L 168,296" fill="none" stroke="black"/> <path d="M 168,312 L 168,392" fill="none" stroke="black"/> <path d="M 168,408 L 168,488" fill="none" stroke="black"/> <path d="M 168,504 L 168,544" fill="none" stroke="black"/> <path d="M 216,208 L 216,272" fill="none" stroke="black"/> <path d="M 216,320 L 216,496" fill="none" stroke="black"/> <path d="M 248,112 L 248,264" fill="none" stroke="black"/> <path d="M 248,280 L 248,304" fill="none" stroke="black"/> <path d="M 280,80 L 280,120" fill="none" stroke="black"/> <path d="M 280,136 L 280,264" fill="none" stroke="black"/> <path d="M 280,280 L 280,312" fill="none" stroke="black"/> <path d="M 280,328 L 280,512" fill="none" stroke="black"/> <path d="M 528,32 L 528,560" fill="none" stroke="black"/> <path d="M 8,32 L 528,32" fill="none" stroke="black"/> <path d="M 8,48 L 168,48" fill="none" stroke="black"/> <path d="M 40,64 L 152,64" fill="none" stroke="black"/> <path d="M 280,80 L 528,80" fill="none" stroke="black"/> <path d="M 48,96 L 136,96" fill="none" stroke="black"/> <path d="M 136,112 L 248,112" fill="none" stroke="black"/> <path d="M 312,112 L 496,112" fill="none" stroke="black"/> <path d="M 48,128 L 136,128" fill="none" stroke="black"/> <path d="M 248,128 L 288,128" fill="none" stroke="black"/> <path d="M 304,128 L 320,128" fill="none" stroke="black"/> <path d="M 24,144 L 136,144" fill="none" stroke="black"/> <path d="M 312,144 L 496,144" fill="none" stroke="black"/> <path d="M 40,160 L 152,160" fill="none" stroke="black"/> <path d="M 312,160 L 496,160" fill="none" stroke="black"/> <path d="M 48,192 L 136,192" fill="none" stroke="black"/> <path d="M 312,192 L 496,192" fill="none" stroke="black"/> <path d="M 136,208 L 216,208" fill="none" stroke="black"/> <path d="M 312,208 L 496,208" fill="none" stroke="black"/> <path d="M 48,224 L 136,224" fill="none" stroke="black"/> <path d="M 24,240 L 136,240" fill="none" stroke="black"/> <path d="M 312,240 L 496,240" fill="none" stroke="black"/> <path d="M 40,256 L 152,256" fill="none" stroke="black"/> <path d="M 312,256 L 496,256" fill="none" stroke="black"/> <path d="M 216,272 L 288,272" fill="none" stroke="black"/> <path d="M 304,272 L 320,272" fill="none" stroke="black"/> <path d="M 48,288 L 136,288" fill="none" stroke="black"/> <path d="M 312,288 L 496,288" fill="none" stroke="black"/> <path d="M 136,304 L 248,304" fill="none" stroke="black"/> <path d="M 312,304 L 496,304" fill="none" stroke="black"/> <path d="M 48,320 L 136,320" fill="none" stroke="black"/> <path d="M 216,320 L 288,320" fill="none" stroke="black"/> <path d="M 304,320 L 320,320" fill="none" stroke="black"/> <path d="M 24,336 L 136,336" fill="none" stroke="black"/> <path d="M 312,336 L 496,336" fill="none" stroke="black"/> <path d="M 40,352 L 152,352" fill="none" stroke="black"/> <path d="M 312,352 L 496,352" fill="none" stroke="black"/> <path d="M 48,384 L 136,384" fill="none" stroke="black"/> <path d="M 312,384 L 496,384" fill="none" stroke="black"/> <path d="M 136,400 L 216,400" fill="none" stroke="black"/> <path d="M 312,400 L 496,400" fill="none" stroke="black"/> <path d="M 48,416 L 136,416" fill="none" stroke="black"/> <path d="M 24,432 L 136,432" fill="none" stroke="black"/> <path d="M 312,432 L 496,432" fill="none" stroke="black"/> <path d="M 40,448 L 152,448" fill="none" stroke="black"/> <path d="M 312,448 L 496,448" fill="none" stroke="black"/> <path d="M 48,480 L 136,480" fill="none" stroke="black"/> <path d="M 312,480 L 496,480" fill="none" stroke="black"/> <path d="M 136,496 L 216,496" fill="none" stroke="black"/> <path d="M 48,512 L 136,512" fill="none" stroke="black"/> <path d="M 280,512 L 528,512" fill="none" stroke="black"/> <path d="M 24,528 L 136,528" fill="none" stroke="black"/> <path d="M 8,544 L 168,544" fill="none" stroke="black"/> <path d="M 8,560 L 528,560" fill="none" stroke="black"/> <path d="M 40,64 C 31.16936,64 24,71.16936 24,80" fill="none" stroke="black"/> <path d="M 312,112 C 303.16936,112 296,119.16936 296,128" fill="none" stroke="black"/> <path d="M 496,112 C 504.83064,112 512,119.16936 512,128" fill="none" stroke="black"/> <path d="M 136,144 C 144.83064,144 152,136.83064 152,128" fill="none" stroke="black"/> <path d="M 312,144 C 303.16936,144 296,136.83064 296,128" fill="none" stroke="black"/> <path d="M 496,144 C 504.83064,144 512,136.83064 512,128" fill="none" stroke="black"/> <path d="M 40,160 C 31.16936,160 24,167.16936 24,176" fill="none" stroke="black"/> <path d="M 312,160 C 303.16936,160 296,167.16936 296,176" fill="none" stroke="black"/> <path d="M 496,160 C 504.83064,160 512,167.16936 512,176" fill="none" stroke="black"/> <path d="M 312,192 C 303.16936,192 296,184.83064 296,176" fill="none" stroke="black"/> <path d="M 496,192 C 504.83064,192 512,184.83064 512,176" fill="none" stroke="black"/> <path d="M 312,208 C 303.16936,208 296,215.16936 296,224" fill="none" stroke="black"/> <path d="M 496,208 C 504.83064,208 512,215.16936 512,224" fill="none" stroke="black"/> <path d="M 136,240 C 144.83064,240 152,232.83064 152,224" fill="none" stroke="black"/> <path d="M 312,240 C 303.16936,240 296,232.83064 296,224" fill="none" stroke="black"/> <path d="M 496,240 C 504.83064,240 512,232.83064 512,224" fill="none" stroke="black"/> <path d="M 40,256 C 31.16936,256 24,263.16936 24,272" fill="none" stroke="black"/> <path d="M 312,256 C 303.16936,256 296,263.16936 296,272" fill="none" stroke="black"/> <path d="M 496,256 C 504.83064,256 512,263.16936 512,272" fill="none" stroke="black"/> <path d="M 312,288 C 303.16936,288 296,280.83064 296,272" fill="none" stroke="black"/> <path d="M 496,288 C 504.83064,288 512,280.83064 512,272" fill="none" stroke="black"/> <path d="M 312,304 C 303.16936,304 296,311.16936 296,320" fill="none" stroke="black"/> <path d="M 496,304 C 504.83064,304 512,311.16936 512,320" fill="none" stroke="black"/> <path d="M 136,336 C 144.83064,336 152,328.83064 152,320" fill="none" stroke="black"/> <path d="M 312,336 C 303.16936,336 296,328.83064 296,320" fill="none" stroke="black"/> <path d="M 496,336 C 504.83064,336 512,328.83064 512,320" fill="none" stroke="black"/> <path d="M 40,352 C 31.16936,352 24,359.16936 24,368" fill="none" stroke="black"/> <path d="M 312,352 C 303.16936,352 296,359.16936 296,368" fill="none" stroke="black"/> <path d="M 496,352 C 504.83064,352 512,359.16936 512,368" fill="none" stroke="black"/> <path d="M 312,384 C 303.16936,384 296,376.83064 296,368" fill="none" stroke="black"/> <path d="M 496,384 C 504.83064,384 512,376.83064 512,368" fill="none" stroke="black"/> <path d="M 312,400 C 303.16936,400 296,407.16936 296,416" fill="none" stroke="black"/> <path d="M 496,400 C 504.83064,400 512,407.16936 512,416" fill="none" stroke="black"/> <path d="M 136,432 C 144.83064,432 152,424.83064 152,416" fill="none" stroke="black"/> <path d="M 312,432 C 303.16936,432 296,424.83064 296,416" fill="none" stroke="black"/> <path d="M 496,432 C 504.83064,432 512,424.83064 512,416" fill="none" stroke="black"/> <path d="M 40,448 C 31.16936,448 24,455.16936 24,464" fill="none" stroke="black"/> <path d="M 312,448 C 303.16936,448 296,455.16936 296,464" fill="none" stroke="black"/> <path d="M 496,448 C 504.83064,448 512,455.16936 512,464" fill="none" stroke="black"/> <path d="M 312,480 C 303.16936,480 296,472.83064 296,464" fill="none" stroke="black"/> <path d="M 496,480 C 504.83064,480 512,472.83064 512,464" fill="none" stroke="black"/> <path d="M 136,528 C 144.83064,528 152,520.83064 152,512" fill="none" stroke="black"/> <polygon class="arrowhead" points="328,320 316,314.4 316,325.6" fill="black" transform="rotate(0,320,320)"/> <polygon class="arrowhead" points="328,272 316,266.4 316,277.6" fill="black" transform="rotate(0,320,272)"/> <polygon class="arrowhead" points="328,128 316,122.4 316,133.6" fill="black" transform="rotate(0,320,128)"/> <path class="jump" d="M 248,280 C 254,280 254,264 248,264" fill="none" stroke="black"/> <g class="text"> <text x="252" y="52">PE</text> <text x="56" y="84">SDP</text> <text x="376" y="100">Transit</text> <text x="428" y="100">link</text> <text x="100" y="116">NS</text> <text x="120" y="116">1</text> <text x="364" y="132">TN</text> <text x="392" y="132">QoS</text> <text x="432" y="132">Class</text> <text x="464" y="132">1</text> <text x="56" y="180">SDP</text> <text x="348" y="180">TN</text> <text x="376" y="180">QoS</text> <text x="416" y="180">Class</text> <text x="448" y="180">2</text> <text x="100" y="212">NS</text> <text x="120" y="212">2</text> <text x="348" y="228">TN</text> <text x="376" y="228">QoS</text> <text x="416" y="228">Class</text> <text x="448" y="228">3</text> <text x="56" y="276">SDP</text> <text x="348" y="276">TN</text> <text x="376" y="276">QoS</text> <text x="416" y="276">Class</text> <text x="448" y="276">4</text> <text x="100" y="308">NS</text> <text x="120" y="308">3</text> <text x="348" y="324">TN</text> <text x="376" y="324">QoS</text> <text x="416" y="324">Class</text> <text x="448" y="324">5</text> <text x="56" y="372">SDP</text> <text x="348" y="372">TN</text> <text x="376" y="372">QoS</text> <text x="416" y="372">Class</text> <text x="448" y="372">6</text> <text x="100" y="404">NS</text> <text x="120" y="404">4</text> <text x="348" y="420">TN</text> <text x="376" y="420">QoS</text> <text x="416" y="420">Class</text> <text x="448" y="420">7</text> <text x="56" y="468">SDP</text> <text x="348" y="468">TN</text> <text x="376" y="468">QoS</text> <text x="416" y="468">Class</text> <text x="448" y="468">8</text> <text x="100" y="500">NS</text> <text x="120" y="500">5</text> <text x="344" y="500">Max</text> <text x="368" y="500">8</text> <text x="388" y="500">TN</text> <text x="432" y="500">Classes</text> <text x="52" y="580">Fine-grained</text> <text x="120" y="580">QoS</text> <text x="184" y="580">enforcement</text> <text x="308" y="580">Coarse-grained</text> <text x="384" y="580">QoS</text> <text x="448" y="580">enforcement</text> <text x="60" y="596">(dedicated</text> <text x="144" y="596">resources</text> <text x="200" y="596">per</text> <text x="292" y="596">(resources</text> <text x="364" y="596">shared</text> <text x="404" y="596">by</text> <text x="452" y="596">multiple</text> <text x="40" y="612">RFC</text> <text x="76" y="612">9543</text> <text x="128" y="612">Network</text> <text x="188" y="612">Slice)</text> <text x="280" y="612">RFC</text> <text x="316" y="612">9543</text> <text x="368" y="612">Network</text> <text x="432" y="612">Slices)</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +----------------------------------------------------------------+ +-------------------. PE | | .--------------+ | | | | SDP | | .------------------------------+ | | +----------+ | | | Transit link | | | | NS 1 +-------------+ | .------------------------. | | | +----------+ | | +-----|--> TN QoS Class 1 | | | '--------------' | | | '------------------------' | | .--------------+ | | | .------------------------. | | | SDP | | | | | TN QoS Class 2 | | | | +----------+ | | | | '------------------------' | | | | NS 2 +---------+ | | .------------------------. | | | +----------+ | | | | | | TN QoS Class 3 | | | '--------------' | | | | '------------------------' | | .--------------+ | | | | .------------------------. | | | SDP | | +---)-----|--> TN QoS Class 4 | | | | +----------+ | | | | '------------------------' | | | | NS 3 +-------------+ | .------------------------. | | | +----------+ | | +---------|--> TN QoS Class 5 | | | '--------------' | | | '------------------------' | | .--------------+ | | | .------------------------. | | | SDP | | | | | TN QoS Class 6 | | | | +----------+ | | | | '------------------------' | | | | NS 4 +---------+ | .------------------------. | | | +----------+ | | | | | TN QoS Class 7 | | | '--------------' | | | '------------------------' | | .--------------+ | | | .------------------------. | | | SDP | | | | | TN QoS Class 8 | | | | +----------+ | | | | '------------------------' | | | | NS 5 +---------+ | Max 8 TN Classes | | | +----------+ | | '------------------------------+ | '--------------' | | +-------------------' | +----------------------------------------------------------------+ Fine-grained QoS enforcement Coarse-grained QoS enforcement (dedicated resources per (resources shared by multiple RFC 9543 Network Slice) RFC 9543 Network Slices) ]]></artwork> </artset> </figure> <t>When the IP traffic is handed over at the SDP from the AC to the provider network, the PE encapsulates the traffic into MPLS (if MPLS transport is used in the providernetwork),network) orIPv6 -IPv6, optionally with some additional headers (if SRv6 transport is used in the provider network), and sends out the packets on the provider network transit link.</t> <!-- [rfced] The sentence below uses "SRv6 encapsulation" while the title of Figure 19 uses "IPv6 Encapsulation". Should these be consistent? If so, which form should be used? Original: This model is outlined in Figure 18 for MPLS encapsulation, and in Figure 19 for SRv6 encapsulation. ... Figure 19: QoS with IPv6 Encapsulation --> <t>The original IP header retains theDCSPDSCP marking (which is ignored in the 5QI-unaware model), while the new header (MPLS or IPv6) carries the QoS marking (MPLS Traffic Class bits for MPLSencapsulation,encapsulation or DSCP for SRv6/IPv6 encapsulation) related to the TN Class of Service (CoS). Based on the TN CoS marking, per-hop behavior for all RFC 9543 Network Slices is executed on provider network transit links. Provider network transit routers do not evaluate the original IP header for QoS-related decisions. This model is outlined in <xref target="_figure-15"/> for MPLSencapsulation,encapsulation and in <xref target="_figure-16"/> for SRv6 encapsulation.</t> <figure anchor="_figure-15"> <name>QoS with MPLS Encapsulation</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="336" width="400" viewBox="0 0 400 336" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,96 L 8,320" fill="none" stroke="black"/> <path d="M 64,128 L 64,160" fill="none" stroke="black"/> <path d="M 128,96 L 128,320" fill="none" stroke="black"/> <path d="M 208,104 L 208,144" fill="none" stroke="black"/> <path d="M 208,272 L 208,312" fill="none" stroke="black"/> <path d="M 272,32 L 272,320" fill="none" stroke="black"/> <path d="M 320,64 L 320,96" fill="none" stroke="black"/> <path d="M 328,128 L 328,160" fill="none" stroke="black"/> <path d="M 368,64 L 368,96" fill="none" stroke="black"/> <path d="M 392,32 L 392,320" fill="none" stroke="black"/> <path d="M 272,32 L 392,32" fill="none" stroke="black"/> <path d="M 272,64 L 368,64" fill="none" stroke="black"/> <path d="M 8,96 L 128,96" fill="none" stroke="black"/> <path d="M 272,96 L 392,96" fill="none" stroke="black"/> <path d="M 64,128 L 128,128" fill="none" stroke="black"/> <path d="M 328,128 L 392,128" fill="none" stroke="black"/> <path d="M 136,144 L 208,144" fill="none" stroke="black"/> <path d="M 8,160 L 128,160" fill="none" stroke="black"/> <path d="M 272,160 L 392,160" fill="none" stroke="black"/> <path d="M 136,272 L 208,272" fill="none" stroke="black"/> <path d="M 8,320 L 128,320" fill="none" stroke="black"/> <path d="M 272,320 L 392,320" fill="none" stroke="black"/> <path d="M 212,104 L 256,192" fill="none" stroke="black"/> <path d="M 212,312 L 256,224" fill="none" stroke="black"/> <g class="text"> <text x="300" y="52">MPLS</text> <text x="348" y="52">Header</text> <text x="296" y="84">Label</text> <text x="332" y="84">TN</text> <text x="356" y="84">TC</text> <text x="144" y="100">-</text> <text x="160" y="100">-</text> <text x="176" y="100">-</text> <text x="192" y="100">-</text> <text x="208" y="100">-</text> <text x="224" y="100">-</text> <text x="240" y="100">-</text> <text x="256" y="100">-</text> <text x="36" y="116">IP</text> <text x="76" y="116">Header</text> <text x="300" y="116">IP</text> <text x="340" y="116">Header</text> <text x="76" y="148">5G</text> <text x="108" y="148">DSCP</text> <text x="340" y="148">5G</text> <text x="372" y="148">DSCP</text> <text x="64" y="228">Payload</text> <text x="328" y="228">Payload</text> <text x="64" y="244">(GTP-U/IPsec)</text> <text x="328" y="244">(GTP-U/IPsec)</text> <text x="144" y="324">-</text> <text x="160" y="324">-</text> <text x="176" y="324">-</text> <text x="192" y="324">-</text> <text x="208" y="324">-</text> <text x="224" y="324">-</text> <text x="240" y="324">-</text> <text x="256" y="324">-</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +--------------+ | MPLS Header | +-----+-----+ | |Label|TN TC| | +--------------+ - - - - - - - - +-----+-----+--+ | IP Header | |\ | IP Header | | +-------+ | \ | +-------+ | |5G DSCP|---------+ \ | |5G DSCP| +------+-------+ \ +------+-------+ | | \ | | | | \ | | | | | | | Payload | / | Payload | |(GTP-U/IPsec) | / |(GTP-U/IPsec) | | | / | | | |---------+ / | | | | | / | | | | |/ | | +--------------+ - - - - - - - - +--------------+ ]]></artwork> </artset> </figure> <figure anchor="_figure-16"> <name>QoS with IPv6 Encapsulation</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="400" width="400" viewBox="0 0 400 400" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,160 L 8,384" fill="none" stroke="black"/> <path d="M 64,192 L 64,224" fill="none" stroke="black"/> <path d="M 128,160 L 128,384" fill="none" stroke="black"/> <path d="M 208,168 L 208,208" fill="none" stroke="black"/> <path d="M 208,336 L 208,376" fill="none" stroke="black"/> <path d="M 272,32 L 272,96" fill="none" stroke="black"/> <path d="M 272,160 L 272,384" fill="none" stroke="black"/> <path d="M 328,64 L 328,96" fill="none" stroke="black"/> <path d="M 328,192 L 328,224" fill="none" stroke="black"/> <path d="M 392,32 L 392,96" fill="none" stroke="black"/> <path d="M 392,160 L 392,384" fill="none" stroke="black"/> <path d="M 272,32 L 392,32" fill="none" stroke="black"/> <path d="M 328,64 L 392,64" fill="none" stroke="black"/> <path d="M 272,96 L 392,96" fill="none" stroke="black"/> <path d="M 8,160 L 128,160" fill="none" stroke="black"/> <path d="M 272,160 L 392,160" fill="none" stroke="black"/> <path d="M 64,192 L 128,192" fill="none" stroke="black"/> <path d="M 328,192 L 392,192" fill="none" stroke="black"/> <path d="M 136,208 L 208,208" fill="none" stroke="black"/> <path d="M 8,224 L 128,224" fill="none" stroke="black"/> <path d="M 272,224 L 392,224" fill="none" stroke="black"/> <path d="M 136,336 L 208,336" fill="none" stroke="black"/> <path d="M 8,384 L 128,384" fill="none" stroke="black"/> <path d="M 272,384 L 392,384" fill="none" stroke="black"/> <path d="M 212,168 L 256,256" fill="none" stroke="black"/> <path d="M 212,376 L 256,288" fill="none" stroke="black"/> <g class="text"> <text x="300" y="52">IPv6</text> <text x="348" y="52">Header</text> <text x="340" y="84">TN</text> <text x="372" y="84">DSCP</text> <text x="272" y="116">:</text> <text x="332" y="116">Optional</text> <text x="392" y="116">:</text> <text x="272" y="132">:</text> <text x="332" y="132">IPv6</text> <text x="392" y="132">:</text> <text x="272" y="148">:</text> <text x="336" y="148">Headers</text> <text x="392" y="148">:</text> <text x="144" y="164">-</text> <text x="160" y="164">-</text> <text x="176" y="164">-</text> <text x="192" y="164">-</text> <text x="208" y="164">-</text> <text x="224" y="164">-</text> <text x="240" y="164">-</text> <text x="256" y="164">-</text> <text x="36" y="180">IP</text> <text x="76" y="180">Header</text> <text x="300" y="180">IP</text> <text x="340" y="180">Header</text> <text x="76" y="212">5G</text> <text x="108" y="212">DSCP</text> <text x="340" y="212">5G</text> <text x="372" y="212">DSCP</text> <text x="64" y="292">Payload</text> <text x="328" y="292">Payload</text> <text x="64" y="308">(GTP-U/IPsec)</text> <text x="328" y="308">(GTP-U/IPsec)</text> <text x="144" y="388">-</text> <text x="160" y="388">-</text> <text x="176" y="388">-</text> <text x="192" y="388">-</text> <text x="208" y="388">-</text> <text x="224" y="388">-</text> <text x="240" y="388">-</text> <text x="256" y="388">-</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +--------------+ | IPv6 Header | | +-------+ | |TN DSCP| +------+-------+ : Optional : : IPv6 : : Headers : +--------------+ - - - - - - - - +-----+-----+--+ | IP Header | |\ | IP Header | | +-------+ | \ | +-------+ | |5G DSCP|---------+ \ | |5G DSCP| +------+-------+ \ +------+-------+ | | \ | | | | \ | | | | | | | Payload | / | Payload | |(GTP-U/IPsec) | / |(GTP-U/IPsec) | | | / | | | |---------+ / | | | | | / | | | | |/ | | +--------------+ - - - - - - - - +--------------+ ]]></artwork> </artset> </figure> <t>From a QoS perspective, both options are similar. However, there is one difference between the two options. The MPLS TC is only 3 bits (8 possible combinations), while DSCP is 6 bits (64 possible combinations). Hence, SRv6 provides more flexibility for TN CoS design, especially in combination with soft policing within-profile/ out-profilein-profile and out-of-profile traffic, as discussed in <xref target="sec-inbound-edge-resource-control"/>.</t> <t>Provider network edge resources are controlled in agranular,fine-grained manner, with dedicated resource allocation for each RFC 9543 Network Slice.The resource control/enforcementResource control and enforcement happens at each SDP in two directions: inbound and outbound.</t> <section anchor="sec-inbound-edge-resource-control"> <name>Inbound Edge Resource Control</name> <t>The main aspect of inbound provider network edge resource control is per-slice traffic volume enforcement. This kind of enforcement is often called'admission control'"admission control" or'traffic conditioning'."traffic conditioning". The goal of this inbound enforcement is to ensure that the traffic above the contracted rate is dropped or deprioritized, depending on the business rules, right at the edge of provider network. This, combined with appropriate network capacity planning/management (<xreftarget="sec-capacity-planning"/>)target="sec-capacity-planning"/>), is required to ensure proper isolation between slices in a scalable manner. As a result, traffic of one slice has no influence on the traffic of other slices, even if the slice is misbehaving (e.g., Distributed Denial-of-Service (DDoS) attacks or node/link failures) and generates traffic volumes above the contracted rates.</t> <!-- [rfced] Is the citation [I-D.ietf-teas-ietf-network-slice-nbi-yang] correct here? We ask because we do not see "slice rate", "CIR", or "PIR" in that document. Link to document: https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slice-nbi-yang/ Original: The slice rates can be characterized with following parameters [I-D.ietf-teas-ietf-network-slice-nbi-yang]: * CIR: Committed Information Rate (i.e., guaranteed bandwidth) * PIR: Peak Information Rate (i.e., maximum bandwidth) --> <t>The slice rates can be characterized with the following parameters <xref target="I-D.ietf-teas-ietf-network-slice-nbi-yang"/>:</t> <ul spacing="normal"> <li><t>CIR:CIR: Committed Information Rate (i.e., guaranteedbandwidth)</t> </li>bandwidth)</li> <li><t>PIR:PIR: Peak Information Rate (i.e., maximumbandwidth)</t> </li>bandwidth)</li> </ul> <t>These parameters define the traffic characteristics of the slice and are part of the SLO parameter set provided by the 5G NSO to an NSC. Based on these parameters, the provider network's inbound policy can be implemented using one of following options:</t> <ul spacing="normal"> <li> <t>1r2c (single-rate two-color) rate limiter </t> <!-- [rfced] Please confirm that Section 2.3 of [RFC2475] is correct here. We do not see "1r2c", "color", or "single rate" in [RFC2475]. Original: * 1r2c (single-rate two-color) rate limiter This is the most basic rate limiter, described in Section 2.3 of [RFC2475]. --> <t> This is the most basic rate limiter, described in <xref section="2.3" sectionFormat="of" target="RFC2475"/>.It meters atAt theSDPSDP, it meters a traffic stream of a given slice and marks its packets as in-profile (below CIR being enforced) or out-of-profile (above CIR being enforced). In-profile packets are accepted and forwarded.Out-of profileOut-of-profile packets are either dropped right at the SDP (hard ratelimiting),limiting) orremarkedre-marked (with different MPLS TC or DSCP TN markings) to signify'this"this packet should be dropped in the first place, if there isa congestion'congestion" (soft rate limiting), depending on the business policy of the provider network. In thesecondlatter case, while packets above CIR are forwarded at the SDP, they are subject to being dropped during any congestion event at any place in the provider network.</t> </li> <li> <t>2r3c (two-rate three-color) rate limiter </t> <t> This was initially defined in <xref target="RFC2698"/>, anditsan improved version is defined in <xref target="RFC4115"/>. In essence, the traffic is assigned to one of the these three categories: </t> <ul spacing="normal"> <li> <t>Green, for traffic under CIR</t> </li> <li> <t>Yellow, for traffic between CIR and PIR</t> </li> <li> <t>Red, for traffic above PIR</t> </li> </ul> <t> An inbound 2r3c meter implemented with <xref target="RFC4115"/>, compared to <xref target="RFC2698"/>, is more'customer friendly'"customer friendly" as it doesn't impose outbound peak-rate shaping requirements oncustomer edge (CE)CE devices. In general, 2r3c metersin generalgive greater flexibility for provider network edge enforcement regarding accepting the traffic (green),de-prioritizingdeprioritizing and potentially dropping the traffic on transit during congestion (yellow), orhard droppinghard-dropping the traffic (red).</t> </li> </ul><t>Inbound<!-- [rfced] We updated "provider" to "provider network" in the parenthetical in this sentence. Let us know if this is incorrect. Original: Inbound provider network edge enforcement model for 5QI-unaware model, where all packets belonging to the slice are treated the same way in the provider network (no 5Q QoS Class differentiation in the provider) is outlined in Figure 20. Perhaps: Inbound provider network edge enforcement for the 5QI-unaware model, where all packets belonging to the slice are treated the same way in the provider network (no 5Q QoS Class differentiation in the provider network), is outlined in Figure 20. --> <t>Inbound provider network edge enforcement for the 5QI-unaware model, where all packets belonging to the slice are treated the same way in the provider network (no 5Q QoS Class differentiation in the provider), is outlined in <xref target="_figure-17"/>.</t> <figure anchor="_figure-17"> <name>Ingress Slice Admission Control(5QI-unaware(5QI-Unaware Model)</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="576" width="280" viewBox="0 0 280 576" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 120,64 L 120,128" fill="none" stroke="black"/> <path d="M 160,64 L 160,208" fill="none" stroke="black"/> <path d="M 160,240 L 160,368" fill="none" stroke="black"/> <path d="M 160,400 L 160,544" fill="none" stroke="black"/> <path d="M 192,48 L 192,64" fill="none" stroke="black"/> <path d="M 192,544 L 192,560" fill="none" stroke="black"/> <path d="M 216,64 L 216,208" fill="none" stroke="black"/> <path d="M 216,240 L 216,368" fill="none" stroke="black"/> <path d="M 216,400 L 216,544" fill="none" stroke="black"/> <path d="M 272,48 L 272,560" fill="none" stroke="black"/> <path d="M 192,48 L 272,48" fill="none" stroke="black"/> <path d="M 160,64 L 184,64" fill="none" stroke="black"/> <path d="M 200,64 L 216,64" fill="none" stroke="black"/> <path d="M 8,144 L 104,144" fill="none" stroke="black"/> <path d="M 128,144 L 152,144" fill="none" stroke="black"/> <path d="M 168,144 L 184,144" fill="none" stroke="black"/> <path d="M 168,224 L 208,224" fill="none" stroke="black"/> <path d="M 8,304 L 104,304" fill="none" stroke="black"/> <path d="M 128,304 L 152,304" fill="none" stroke="black"/> <path d="M 168,304 L 184,304" fill="none" stroke="black"/> <path d="M 168,384 L 208,384" fill="none" stroke="black"/> <path d="M 8,464 L 104,464" fill="none" stroke="black"/> <path d="M 128,464 L 152,464" fill="none" stroke="black"/> <path d="M 168,464 L 184,464" fill="none" stroke="black"/> <path d="M 160,544 L 184,544" fill="none" stroke="black"/> <path d="M 200,544 L 216,544" fill="none" stroke="black"/> <path d="M 192,560 L 272,560" fill="none" stroke="black"/> <polygon class="arrowhead" points="192,464 180,458.4 180,469.6" fill="black" transform="rotate(0,184,464)"/> <polygon class="arrowhead" points="192,304 180,298.4 180,309.6" fill="black" transform="rotate(0,184,304)"/> <polygon class="arrowhead" points="192,144 180,138.4 180,149.6" fill="black" transform="rotate(0,184,144)"/> <polygon class="arrowhead" points="128,128 116,122.4 116,133.6" fill="black" transform="rotate(90,120,128)"/> <g class="text"> <text x="120" y="36">Slice</text> <text x="120" y="52">policer</text> <text x="200" y="100">S</text> <text x="200" y="116">l</text> <text x="200" y="132">i</text> <text x="116" y="148"><></text> <text x="200" y="148">c</text> <text x="200" y="164">e</text> <text x="240" y="164">A</text> <text x="240" y="180">t</text> <text x="200" y="196">1</text> <text x="240" y="196">t</text> <text x="240" y="212">a</text> <text x="240" y="228">c</text> <text x="240" y="244">h</text> <text x="200" y="260">S</text> <text x="240" y="260">m</text> <text x="200" y="276">l</text> <text x="240" y="276">e</text> <text x="200" y="292">i</text> <text x="240" y="292">n</text> <text x="116" y="308"><></text> <text x="200" y="308">c</text> <text x="240" y="308">t</text> <text x="200" y="324">e</text> <text x="240" y="340">C</text> <text x="200" y="356">2</text> <text x="240" y="356">i</text> <text x="240" y="372">r</text> <text x="240" y="388">c</text> <text x="240" y="404">u</text> <text x="200" y="420">S</text> <text x="240" y="420">i</text> <text x="200" y="436">l</text> <text x="240" y="436">t</text> <text x="200" y="452">i</text> <text x="116" y="468"><></text> <text x="200" y="468">c</text> <text x="200" y="484">e</text> <text x="200" y="516">3</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ Slice policer +---------+ | +---|--+ | | | | | | | S | | | | l | | v | i | | -------------<>----|--> c | | | e | A | | | t | | 1 | t | | | a | ------ c | | | h | | S | m | | l | e | | i | n | -------------<>----|--> c | t | | e | | | | C | | 2 | i | | | r | ------ c | | | u | | S | i | | l | t | | i | | -------------<>----|--> c | | | e | | | | | | 3 | | | | | +---|--+ | +---------+ ]]></artwork> </artset> </figure> </section> <section anchor="outbound-edge-resource-control"> <name>Outbound Edge Resource Control</name> <t>While inbound slice admission control at the provider network edge is mandatory in the architecture described in this document, outbound provider network edge resource control might not be required in all use cases. Use cases that specifically call for outbound provider network edge resource control are:</t> <ul spacing="normal"> <li> <t>Slices use both CIR and PIR parameters, and provider network edge links (ACs) are dimensioned to fulfill the aggregate of slice CIRs.IfIf, at any given time, some slices send the traffic above CIR, congestion in the outbound direction on the provider network edge link (AC) might happen. Therefore, fine-grained resource control to guarantee at least CIR for each slice is required.</t> </li> <li> <t>Any-to-Any (A2A) connectivity constructs are deployed, again resulting in potential congestion in the outbound direction on the provider network edge links, even if only slice CIR parameters are used. This again requires fine-grained resource control per slice in the outbound direction at the provider network edge links.</t> </li> </ul> <t>As opposed to inbound provider network edge resource control, typically implemented with rate-limiters/policers, outbound resource control is typically implemented with a weighted/priority queuing, potentially combined with optional shapers (per slice). A detailed analysis of different queuing mechanisms is out of scope for thisdocument,document but is provided in <xref target="RFC7806"/>.</t> <t><xref target="_figure-18"/> outlines the outbound provider network edge resource control model for 5QI-unaware slices. Each slice is assigned a single egress queue. The sum of slice CIRs, used as the weight in weighted queueing model, should not exceed the physical capacity of the AC. Slice requests above this limit should be rejected by the NSC, unless analready establishedalready-established slice with lower priority, if such exists, is preempted.</t> <figure anchor="_figure-18"> <name>Ingress Slice Admissioncontrol (5QI-unawareControl (5QI-Unaware Model) - Output</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="512" width="552" viewBox="0 0 552 512" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 32,32 L 32,480" fill="none" stroke="black"/> <path d="M 80,64 L 80,176" fill="none" stroke="black"/> <path d="M 80,208 L 80,304" fill="none" stroke="black"/> <path d="M 80,336 L 80,448" fill="none" stroke="black"/> <path d="M 112,32 L 112,56" fill="none" stroke="black"/> <path d="M 112,456 L 112,480" fill="none" stroke="black"/> <path d="M 144,64 L 144,144" fill="none" stroke="black"/> <path d="M 144,200 L 144,272" fill="none" stroke="black"/> <path d="M 144,328 L 144,400" fill="none" stroke="black"/> <path d="M 144,432 L 144,448" fill="none" stroke="black"/> <path d="M 384,72 L 384,184" fill="none" stroke="black"/> <path d="M 384,200 L 384,312" fill="none" stroke="black"/> <path d="M 384,328 L 384,440" fill="none" stroke="black"/> <path d="M 32,32 L 112,32" fill="none" stroke="black"/> <path d="M 80,64 L 144,64" fill="none" stroke="black"/> <path d="M 128,144 L 136,144" fill="none" stroke="black"/> <path d="M 152,144 L 352,144" fill="none" stroke="black"/> <path d="M 8,160 L 24,160" fill="none" stroke="black"/> <path d="M 88,160 L 104,160" fill="none" stroke="black"/> <path d="M 120,160 L 136,160" fill="none" stroke="black"/> <path d="M 128,176 L 136,176" fill="none" stroke="black"/> <path d="M 152,176 L 352,176" fill="none" stroke="black"/> <path d="M 88,192 L 128,192" fill="none" stroke="black"/> <path d="M 128,272 L 136,272" fill="none" stroke="black"/> <path d="M 152,272 L 352,272" fill="none" stroke="black"/> <path d="M 8,288 L 24,288" fill="none" stroke="black"/> <path d="M 40,288 L 72,288" fill="none" stroke="black"/> <path d="M 88,288 L 104,288" fill="none" stroke="black"/> <path d="M 120,288 L 136,288" fill="none" stroke="black"/> <path d="M 128,304 L 136,304" fill="none" stroke="black"/> <path d="M 152,304 L 352,304" fill="none" stroke="black"/> <path d="M 88,320 L 128,320" fill="none" stroke="black"/> <path d="M 128,400 L 136,400" fill="none" stroke="black"/> <path d="M 152,400 L 352,400" fill="none" stroke="black"/> <path d="M 8,416 L 24,416" fill="none" stroke="black"/> <path d="M 40,416 L 72,416" fill="none" stroke="black"/> <path d="M 88,416 L 104,416" fill="none" stroke="black"/> <path d="M 120,416 L 136,416" fill="none" stroke="black"/> <path d="M 128,432 L 136,432" fill="none" stroke="black"/> <path d="M 152,432 L 352,432" fill="none" stroke="black"/> <path d="M 80,448 L 144,448" fill="none" stroke="black"/> <path d="M 32,480 L 112,480" fill="none" stroke="black"/> <path d="M 128,144 C 119.16936,144 112,151.16936 112,160" fill="none" stroke="black"/> <path d="M 352,144 C 360.83064,144 368,151.16936 368,160" fill="none" stroke="black"/> <path d="M 128,176 C 119.16936,176 112,168.83064 112,160" fill="none" stroke="black"/> <path d="M 352,176 C 360.83064,176 368,168.83064 368,160" fill="none" stroke="black"/> <path d="M 128,272 C 119.16936,272 112,279.16936 112,288" fill="none" stroke="black"/> <path d="M 352,272 C 360.83064,272 368,279.16936 368,288" fill="none" stroke="black"/> <path d="M 128,304 C 119.16936,304 112,296.83064 112,288" fill="none" stroke="black"/> <path d="M 352,304 C 360.83064,304 368,296.83064 368,288" fill="none" stroke="black"/> <path d="M 128,400 C 119.16936,400 112,407.16936 112,416" fill="none" stroke="black"/> <path d="M 352,400 C 360.83064,400 368,407.16936 368,416" fill="none" stroke="black"/> <path d="M 128,432 C 119.16936,432 112,424.83064 112,416" fill="none" stroke="black"/> <path d="M 352,432 C 360.83064,432 368,424.83064 368,416" fill="none" stroke="black"/> <polygon class="arrowhead" points="144,416 132,410.4 132,421.6" fill="black" transform="rotate(0,136,416)"/> <polygon class="arrowhead" points="144,288 132,282.4 132,293.6" fill="black" transform="rotate(0,136,288)"/> <polygon class="arrowhead" points="144,160 132,154.4 132,165.6" fill="black" transform="rotate(0,136,160)"/> <g class="text"> <text x="192" y="36">QoS</text> <text x="236" y="36">output</text> <text x="292" y="36">queues</text> <text x="160" y="68">-</text> <text x="176" y="68">-</text> <text x="192" y="68">-</text> <text x="208" y="68">-</text> <text x="224" y="68">-</text> <text x="240" y="68">-</text> <text x="256" y="68">-</text> <text x="272" y="68">-</text> <text x="288" y="68">-</text> <text x="304" y="68">-</text> <text x="320" y="68">-</text> <text x="336" y="68">-</text> <text x="352" y="68">-</text> <text x="368" y="68">-</text> <text x="384" y="68">-</text> <text x="400" y="68">-</text> <text x="416" y="68">-</text> <text x="432" y="68">-</text> <text x="448" y="68">-</text> <text x="464" y="68">-</text> <text x="480" y="68">-</text> <text x="496" y="68">-</text> <text x="512" y="68">-</text> <text x="528" y="68">-</text> <text x="544" y="68">-</text> <text x="96" y="84">S</text> <text x="376" y="84">\</text> <text x="392" y="84">/</text> <text x="96" y="100">l</text> <text x="96" y="116">i</text> <text x="56" y="132">A</text> <text x="96" y="132">c</text> <text x="476" y="132">weight-Slice-1-CIR</text> <text x="56" y="148">t</text> <text x="96" y="148">e</text> <text x="472" y="148">shaping-Slice-1-PIR</text> <text x="56" y="164">--t--</text> <text x="56" y="180">a</text> <text x="96" y="180">1</text> <text x="144" y="180">|</text> <text x="376" y="180">/</text> <text x="392" y="180">\</text> <text x="56" y="196">c</text> <text x="144" y="196">-</text> <text x="160" y="196">-</text> <text x="176" y="196">-</text> <text x="192" y="196">-</text> <text x="208" y="196">-</text> <text x="224" y="196">-</text> <text x="240" y="196">-</text> <text x="256" y="196">-</text> <text x="272" y="196">-</text> <text x="288" y="196">-</text> <text x="304" y="196">-</text> <text x="320" y="196">-</text> <text x="336" y="196">-</text> <text x="352" y="196">-</text> <text x="368" y="196">-</text> <text x="384" y="196">-</text> <text x="400" y="196">-</text> <text x="416" y="196">-</text> <text x="432" y="196">-</text> <text x="448" y="196">-</text> <text x="464" y="196">-</text> <text x="480" y="196">-</text> <text x="496" y="196">-</text> <text x="512" y="196">-</text> <text x="528" y="196">-</text> <text x="544" y="196">-</text> <text x="56" y="212">h</text> <text x="96" y="212">S</text> <text x="376" y="212">\</text> <text x="392" y="212">/</text> <text x="56" y="228">m</text> <text x="96" y="228">l</text> <text x="56" y="244">e</text> <text x="96" y="244">i</text> <text x="56" y="260">n</text> <text x="96" y="260">c</text> <text x="476" y="260">weight-Slice-2-CIR</text> <text x="56" y="276">t</text> <text x="96" y="276">e</text> <text x="472" y="276">shaping-Slice-2-PIR</text> <text x="56" y="308">C</text> <text x="96" y="308">2</text> <text x="144" y="308">|</text> <text x="376" y="308">/</text> <text x="392" y="308">\</text> <text x="56" y="324">i</text> <text x="144" y="324">-</text> <text x="160" y="324">-</text> <text x="176" y="324">-</text> <text x="192" y="324">-</text> <text x="208" y="324">-</text> <text x="224" y="324">-</text> <text x="240" y="324">-</text> <text x="256" y="324">-</text> <text x="272" y="324">-</text> <text x="288" y="324">-</text> <text x="304" y="324">-</text> <text x="320" y="324">-</text> <text x="336" y="324">-</text> <text x="352" y="324">-</text> <text x="368" y="324">-</text> <text x="384" y="324">-</text> <text x="400" y="324">-</text> <text x="416" y="324">-</text> <text x="432" y="324">-</text> <text x="448" y="324">-</text> <text x="464" y="324">-</text> <text x="480" y="324">-</text> <text x="496" y="324">-</text> <text x="512" y="324">-</text> <text x="528" y="324">-</text> <text x="544" y="324">-</text> <text x="56" y="340">r</text> <text x="96" y="340">S</text> <text x="376" y="340">\</text> <text x="392" y="340">/</text> <text x="56" y="356">c</text> <text x="96" y="356">l</text> <text x="56" y="372">u</text> <text x="96" y="372">i</text> <text x="56" y="388">i</text> <text x="96" y="388">c</text> <text x="476" y="388">weight-Slice-3-CIR</text> <text x="56" y="404">t</text> <text x="96" y="404">e</text> <text x="472" y="404">shaping-Slice-3-PIR</text> <text x="96" y="436">3</text> <text x="376" y="436">/</text> <text x="392" y="436">\</text> <text x="160" y="452">-</text> <text x="176" y="452">-</text> <text x="192" y="452">-</text> <text x="208" y="452">-</text> <text x="224" y="452">-</text> <text x="240" y="452">-</text> <text x="256" y="452">-</text> <text x="272" y="452">-</text> <text x="288" y="452">-</text> <text x="304" y="452">-</text> <text x="320" y="452">-</text> <text x="336" y="452">-</text> <text x="352" y="452">-</text> <text x="368" y="452">-</text> <text x="384" y="452">-</text> <text x="400" y="452">-</text> <text x="416" y="452">-</text> <text x="432" y="452">-</text> <text x="448" y="452">-</text> <text x="464" y="452">-</text> <text x="480" y="452">-</text> <text x="496" y="452">-</text> <text x="512" y="452">-</text> <text x="528" y="452">-</text> <text x="544" y="452">-</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +---------+ QoS output queues | | | +-------+ - - - - - - - - - - - - - - - - - - - - - - - - - | | S | \|/ | | l | | | | i | | | A | c | | weight-Slice-1-CIR | t | e .--|--------------------------. | shaping-Slice-1-PIR ---|--t--|---|--> | | | a | 1 '--|--------------------------' /|\ | c ------ - - - - - - - - - - - - - - - - - - - - - - - - - - | h | S | \|/ | m | l | | | e | i | | | n | c | | weight-Slice-2-CIR | t | e .--|--------------------------. | shaping-Slice-2-PIR ---|-----|---|--> | | | C | 2 '--|--------------------------' /|\ | i ------ - - - - - - - - - - - - - - - - - - - - - - - - - - | r | S | \|/ | c | l | | | u | i | | | i | c | | weight-Slice-3-CIR | t | e .--|--------------------------. | shaping-Slice-3-PIR ---|-----|---|--> | | | | 3 '--|--------------------------' /|\ | +-------+ - - - - - - - - - - - - - - - - - - - - - - - - - | | +---------+ ]]></artwork> </artset> </figure> </section> </section> <section anchor="qi-aware-model"><name>5QI-aware<name>5QI-Aware Model</name> <t>In the 5QI-aware model,potentiallya potentially large number of 5G QoS Classes, represented via the DSCP set by NFs (the architecture scales to thousands of 5Gslices)slices), is mapped (multiplexed) to up to 8 TN QoS Classes used in a provider network transit equipment, as outlined in <xref target="_figure-QoS-5QI-aware"/>.</t> <figure anchor="_figure-QoS-5QI-aware"><name>Slice<name>Mapping of Slice 5Q QoS to TN QoSMapping (5QI-aware(5QI-Aware Model)</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="624" width="584" viewBox="0 0 584 624" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 24,32 L 24,560" fill="none" stroke="black"/> <path d="M 40,80 L 40,288" fill="none" stroke="black"/> <path d="M 40,320 L 40,528" fill="none" stroke="black"/> <path d="M 168,64 L 168,104" fill="none" stroke="black"/> <path d="M 168,120 L 168,152" fill="none" stroke="black"/> <path d="M 168,168 L 168,200" fill="none" stroke="black"/> <path d="M 168,216 L 168,248" fill="none" stroke="black"/> <path d="M 168,304 L 168,328" fill="none" stroke="black"/> <path d="M 168,344 L 168,376" fill="none" stroke="black"/> <path d="M 168,392 L 168,424" fill="none" stroke="black"/> <path d="M 168,440 L 168,472" fill="none" stroke="black"/> <path d="M 168,488 L 168,512" fill="none" stroke="black"/> <path d="M 184,48 L 184,104" fill="none" stroke="black"/> <path d="M 184,120 L 184,152" fill="none" stroke="black"/> <path d="M 184,168 L 184,200" fill="none" stroke="black"/> <path d="M 184,216 L 184,248" fill="none" stroke="black"/> <path d="M 184,264 L 184,328" fill="none" stroke="black"/> <path d="M 184,344 L 184,376" fill="none" stroke="black"/> <path d="M 184,392 L 184,424" fill="none" stroke="black"/> <path d="M 184,440 L 184,472" fill="none" stroke="black"/> <path d="M 184,488 L 184,544" fill="none" stroke="black"/> <path d="M 208,256 L 208,328" fill="none" stroke="black"/> <path d="M 208,344 L 208,376" fill="none" stroke="black"/> <path d="M 208,392 L 208,424" fill="none" stroke="black"/> <path d="M 208,440 L 208,480" fill="none" stroke="black"/> <path d="M 232,208 L 232,376" fill="none" stroke="black"/> <path d="M 232,392 L 232,432" fill="none" stroke="black"/> <path d="M 256,160 L 256,312" fill="none" stroke="black"/> <path d="M 256,328 L 256,384" fill="none" stroke="black"/> <path d="M 280,112 L 280,264" fill="none" stroke="black"/> <path d="M 280,280 L 280,336" fill="none" stroke="black"/> <path d="M 296,80 L 296,120" fill="none" stroke="black"/> <path d="M 296,136 L 296,264" fill="none" stroke="black"/> <path d="M 296,280 L 296,312" fill="none" stroke="black"/> <path d="M 296,328 L 296,456" fill="none" stroke="black"/> <path d="M 296,472 L 296,512" fill="none" stroke="black"/> <path d="M 536,32 L 536,560" fill="none" stroke="black"/> <path d="M 24,32 L 536,32" fill="none" stroke="black"/> <path d="M 24,48 L 184,48" fill="none" stroke="black"/> <path d="M 56,64 L 168,64" fill="none" stroke="black"/> <path d="M 296,80 L 536,80" fill="none" stroke="black"/> <path d="M 72,96 L 136,96" fill="none" stroke="black"/> <path d="M 152,112 L 280,112" fill="none" stroke="black"/> <path d="M 328,112 L 504,112" fill="none" stroke="black"/> <path d="M 72,128 L 136,128" fill="none" stroke="black"/> <path d="M 280,128 L 304,128" fill="none" stroke="black"/> <path d="M 320,128 L 336,128" fill="none" stroke="black"/> <path d="M 72,144 L 136,144" fill="none" stroke="black"/> <path d="M 328,144 L 504,144" fill="none" stroke="black"/> <path d="M 152,160 L 256,160" fill="none" stroke="black"/> <path d="M 328,160 L 504,160" fill="none" stroke="black"/> <path d="M 72,176 L 136,176" fill="none" stroke="black"/> <path d="M 72,192 L 136,192" fill="none" stroke="black"/> <path d="M 328,192 L 504,192" fill="none" stroke="black"/> <path d="M 152,208 L 232,208" fill="none" stroke="black"/> <path d="M 328,208 L 504,208" fill="none" stroke="black"/> <path d="M 72,224 L 136,224" fill="none" stroke="black"/> <path d="M 72,240 L 136,240" fill="none" stroke="black"/> <path d="M 328,240 L 504,240" fill="none" stroke="black"/> <path d="M 152,256 L 208,256" fill="none" stroke="black"/> <path d="M 328,256 L 504,256" fill="none" stroke="black"/> <path d="M 72,272 L 136,272" fill="none" stroke="black"/> <path d="M 256,272 L 304,272" fill="none" stroke="black"/> <path d="M 320,272 L 336,272" fill="none" stroke="black"/> <path d="M 40,288 L 152,288" fill="none" stroke="black"/> <path d="M 328,288 L 504,288" fill="none" stroke="black"/> <path d="M 56,304 L 168,304" fill="none" stroke="black"/> <path d="M 328,304 L 504,304" fill="none" stroke="black"/> <path d="M 72,320 L 136,320" fill="none" stroke="black"/> <path d="M 232,320 L 272,320" fill="none" stroke="black"/> <path d="M 288,320 L 304,320" fill="none" stroke="black"/> <path d="M 320,320 L 336,320" fill="none" stroke="black"/> <path d="M 152,336 L 224,336" fill="none" stroke="black"/> <path d="M 264,336 L 280,336" fill="none" stroke="black"/> <path d="M 328,336 L 504,336" fill="none" stroke="black"/> <path d="M 72,352 L 136,352" fill="none" stroke="black"/> <path d="M 328,352 L 504,352" fill="none" stroke="black"/> <path d="M 72,368 L 136,368" fill="none" stroke="black"/> <path d="M 152,384 L 256,384" fill="none" stroke="black"/> <path d="M 328,384 L 504,384" fill="none" stroke="black"/> <path d="M 72,400 L 136,400" fill="none" stroke="black"/> <path d="M 328,400 L 504,400" fill="none" stroke="black"/> <path d="M 72,416 L 136,416" fill="none" stroke="black"/> <path d="M 152,432 L 232,432" fill="none" stroke="black"/> <path d="M 328,432 L 504,432" fill="none" stroke="black"/> <path d="M 72,448 L 136,448" fill="none" stroke="black"/> <path d="M 328,448 L 504,448" fill="none" stroke="black"/> <path d="M 72,464 L 136,464" fill="none" stroke="black"/> <path d="M 208,464 L 304,464" fill="none" stroke="black"/> <path d="M 320,464 L 336,464" fill="none" stroke="black"/> <path d="M 152,480 L 208,480" fill="none" stroke="black"/> <path d="M 328,480 L 504,480" fill="none" stroke="black"/> <path d="M 72,496 L 136,496" fill="none" stroke="black"/> <path d="M 296,512 L 536,512" fill="none" stroke="black"/> <path d="M 40,528 L 152,528" fill="none" stroke="black"/> <path d="M 24,544 L 184,544" fill="none" stroke="black"/> <path d="M 24,560 L 536,560" fill="none" stroke="black"/> <path d="M 56,64 C 47.16936,64 40,71.16936 40,80" fill="none" stroke="black"/> <path d="M 72,96 C 63.16936,96 56,103.16936 56,112" fill="none" stroke="black"/> <path d="M 136,96 C 144.83064,96 152,103.16936 152,112" fill="none" stroke="black"/> <path d="M 328,112 C 319.16936,112 312,119.16936 312,128" fill="none" stroke="black"/> <path d="M 504,112 C 512.83064,112 520,119.16936 520,128" fill="none" stroke="black"/> <path d="M 72,128 C 63.16936,128 56,120.83064 56,112" fill="none" stroke="black"/> <path d="M 136,128 C 144.83064,128 152,120.83064 152,112" fill="none" stroke="black"/> <path d="M 72,144 C 63.16936,144 56,151.16936 56,160" fill="none" stroke="black"/> <path d="M 136,144 C 144.83064,144 152,151.16936 152,160" fill="none" stroke="black"/> <path d="M 328,144 C 319.16936,144 312,136.83064 312,128" fill="none" stroke="black"/> <path d="M 504,144 C 512.83064,144 520,136.83064 520,128" fill="none" stroke="black"/> <path d="M 328,160 C 319.16936,160 312,167.16936 312,176" fill="none" stroke="black"/> <path d="M 504,160 C 512.83064,160 520,167.16936 520,176" fill="none" stroke="black"/> <path d="M 72,176 C 63.16936,176 56,168.83064 56,160" fill="none" stroke="black"/> <path d="M 136,176 C 144.83064,176 152,168.83064 152,160" fill="none" stroke="black"/> <path d="M 72,192 C 63.16936,192 56,199.16936 56,208" fill="none" stroke="black"/> <path d="M 136,192 C 144.83064,192 152,199.16936 152,208" fill="none" stroke="black"/> <path d="M 328,192 C 319.16936,192 312,184.83064 312,176" fill="none" stroke="black"/> <path d="M 504,192 C 512.83064,192 520,184.83064 520,176" fill="none" stroke="black"/> <path d="M 328,208 C 319.16936,208 312,215.16936 312,224" fill="none" stroke="black"/> <path d="M 504,208 C 512.83064,208 520,215.16936 520,224" fill="none" stroke="black"/> <path d="M 72,224 C 63.16936,224 56,216.83064 56,208" fill="none" stroke="black"/> <path d="M 136,224 C 144.83064,224 152,216.83064 152,208" fill="none" stroke="black"/> <path d="M 72,240 C 63.16936,240 56,247.16936 56,256" fill="none" stroke="black"/> <path d="M 136,240 C 144.83064,240 152,247.16936 152,256" fill="none" stroke="black"/> <path d="M 328,240 C 319.16936,240 312,232.83064 312,224" fill="none" stroke="black"/> <path d="M 504,240 C 512.83064,240 520,232.83064 520,224" fill="none" stroke="black"/> <path d="M 328,256 C 319.16936,256 312,263.16936 312,272" fill="none" stroke="black"/> <path d="M 504,256 C 512.83064,256 520,263.16936 520,272" fill="none" stroke="black"/> <path d="M 72,272 C 63.16936,272 56,264.83064 56,256" fill="none" stroke="black"/> <path d="M 136,272 C 144.83064,272 152,264.83064 152,256" fill="none" stroke="black"/> <path d="M 152,288 C 160.83064,288 168,280.83064 168,272" fill="none" stroke="black"/> <path d="M 328,288 C 319.16936,288 312,280.83064 312,272" fill="none" stroke="black"/> <path d="M 504,288 C 512.83064,288 520,280.83064 520,272" fill="none" stroke="black"/> <path d="M 56,304 C 47.16936,304 40,311.16936 40,320" fill="none" stroke="black"/> <path d="M 328,304 C 319.16936,304 312,311.16936 312,320" fill="none" stroke="black"/> <path d="M 504,304 C 512.83064,304 520,311.16936 520,320" fill="none" stroke="black"/> <path d="M 72,320 C 63.16936,320 56,327.16936 56,336" fill="none" stroke="black"/> <path d="M 136,320 C 144.83064,320 152,327.16936 152,336" fill="none" stroke="black"/> <path d="M 328,336 C 319.16936,336 312,328.83064 312,320" fill="none" stroke="black"/> <path d="M 504,336 C 512.83064,336 520,328.83064 520,320" fill="none" stroke="black"/> <path d="M 72,352 C 63.16936,352 56,344.83064 56,336" fill="none" stroke="black"/> <path d="M 136,352 C 144.83064,352 152,344.83064 152,336" fill="none" stroke="black"/> <path d="M 328,352 C 319.16936,352 312,359.16936 312,368" fill="none" stroke="black"/> <path d="M 504,352 C 512.83064,352 520,359.16936 520,368" fill="none" stroke="black"/> <path d="M 72,368 C 63.16936,368 56,375.16936 56,384" fill="none" stroke="black"/> <path d="M 136,368 C 144.83064,368 152,375.16936 152,384" fill="none" stroke="black"/> <path d="M 328,384 C 319.16936,384 312,376.83064 312,368" fill="none" stroke="black"/> <path d="M 504,384 C 512.83064,384 520,376.83064 520,368" fill="none" stroke="black"/> <path d="M 72,400 C 63.16936,400 56,392.83064 56,384" fill="none" stroke="black"/> <path d="M 136,400 C 144.83064,400 152,392.83064 152,384" fill="none" stroke="black"/> <path d="M 328,400 C 319.16936,400 312,407.16936 312,416" fill="none" stroke="black"/> <path d="M 504,400 C 512.83064,400 520,407.16936 520,416" fill="none" stroke="black"/> <path d="M 72,416 C 63.16936,416 56,423.16936 56,432" fill="none" stroke="black"/> <path d="M 136,416 C 144.83064,416 152,423.16936 152,432" fill="none" stroke="black"/> <path d="M 328,432 C 319.16936,432 312,424.83064 312,416" fill="none" stroke="black"/> <path d="M 504,432 C 512.83064,432 520,424.83064 520,416" fill="none" stroke="black"/> <path d="M 72,448 C 63.16936,448 56,440.83064 56,432" fill="none" stroke="black"/> <path d="M 136,448 C 144.83064,448 152,440.83064 152,432" fill="none" stroke="black"/> <path d="M 328,448 C 319.16936,448 312,455.16936 312,464" fill="none" stroke="black"/> <path d="M 504,448 C 512.83064,448 520,455.16936 520,464" fill="none" stroke="black"/> <path d="M 72,464 C 63.16936,464 56,471.16936 56,480" fill="none" stroke="black"/> <path d="M 136,464 C 144.83064,464 152,471.16936 152,480" fill="none" stroke="black"/> <path d="M 328,480 C 319.16936,480 312,472.83064 312,464" fill="none" stroke="black"/> <path d="M 504,480 C 512.83064,480 520,472.83064 520,464" fill="none" stroke="black"/> <path d="M 72,496 C 63.16936,496 56,488.83064 56,480" fill="none" stroke="black"/> <path d="M 136,496 C 144.83064,496 152,488.83064 152,480" fill="none" stroke="black"/> <path d="M 152,528 C 160.83064,528 168,520.83064 168,512" fill="none" stroke="black"/> <polygon class="arrowhead" points="344,464 332,458.4 332,469.6" fill="black" transform="rotate(0,336,464)"/> <polygon class="arrowhead" points="344,320 332,314.4 332,325.6" fill="black" transform="rotate(0,336,320)"/> <polygon class="arrowhead" points="344,272 332,266.4 332,277.6" fill="black" transform="rotate(0,336,272)"/> <polygon class="arrowhead" points="344,128 332,122.4 332,133.6" fill="black" transform="rotate(0,336,128)"/> <path class="jump" d="M 280,280 C 286,280 286,264 280,264" fill="none" stroke="black"/> <path class="jump" d="M 256,328 C 262,328 262,312 256,312" fill="none" stroke="black"/> <path class="jump" d="M 232,392 C 238,392 238,376 232,376" fill="none" stroke="black"/> <path class="jump" d="M 208,440 C 214,440 214,424 208,424" fill="none" stroke="black"/> <path class="jump" d="M 208,392 C 214,392 214,376 208,376" fill="none" stroke="black"/> <path class="jump" d="M 208,344 C 214,344 214,328 208,328" fill="none" stroke="black"/> <g class="text"> <text x="260" y="52">PE</text> <text x="8" y="84">R</text> <text x="72" y="84">SDP</text> <text x="8" y="100">F</text> <text x="384" y="100">Transit</text> <text x="436" y="100">link</text> <text x="8" y="116">C</text> <text x="76" y="116">5G</text> <text x="108" y="116">DSCP</text> <text x="136" y="116">A</text> <text x="8" y="132">9</text> <text x="364" y="132">TN</text> <text x="392" y="132">QoS</text> <text x="432" y="132">Class</text> <text x="464" y="132">1</text> <text x="8" y="148">5</text> <text x="8" y="164">4</text> <text x="76" y="164">5G</text> <text x="108" y="164">DSCP</text> <text x="136" y="164">B</text> <text x="8" y="180">3</text> <text x="364" y="180">TN</text> <text x="392" y="180">QoS</text> <text x="432" y="180">Class</text> <text x="464" y="180">2</text> <text x="8" y="212">N</text> <text x="76" y="212">5G</text> <text x="108" y="212">DSCP</text> <text x="136" y="212">C</text> <text x="8" y="228">S</text> <text x="364" y="228">TN</text> <text x="392" y="228">QoS</text> <text x="432" y="228">Class</text> <text x="464" y="228">3</text> <text x="8" y="260">1</text> <text x="76" y="260">5G</text> <text x="108" y="260">DSCP</text> <text x="136" y="260">D</text> <text x="364" y="276">TN</text> <text x="392" y="276">QoS</text> <text x="432" y="276">Class</text> <text x="464" y="276">4</text> <text x="8" y="308">R</text> <text x="8" y="324">F</text> <text x="364" y="324">TN</text> <text x="392" y="324">QoS</text> <text x="432" y="324">Class</text> <text x="464" y="324">5</text> <text x="8" y="340">C</text> <text x="76" y="340">5G</text> <text x="108" y="340">DSCP</text> <text x="136" y="340">A</text> <text x="244" y="340">--</text> <text x="8" y="356">9</text> <text x="8" y="372">5</text> <text x="364" y="372">TN</text> <text x="392" y="372">QoS</text> <text x="432" y="372">Class</text> <text x="464" y="372">6</text> <text x="8" y="388">4</text> <text x="76" y="388">5G</text> <text x="108" y="388">DSCP</text> <text x="136" y="388">E</text> <text x="8" y="404">3</text> <text x="364" y="420">TN</text> <text x="392" y="420">QoS</text> <text x="432" y="420">Class</text> <text x="464" y="420">7</text> <text x="8" y="436">N</text> <text x="76" y="436">5G</text> <text x="108" y="436">DSCP</text> <text x="136" y="436">F</text> <text x="8" y="452">S</text> <text x="364" y="468">TN</text> <text x="392" y="468">QoS</text> <text x="432" y="468">Class</text> <text x="464" y="468">8</text> <text x="8" y="484">2</text> <text x="76" y="484">5G</text> <text x="108" y="484">DSCP</text> <text x="136" y="484">G</text> <text x="360" y="500">Max</text> <text x="384" y="500">8</text> <text x="404" y="500">TN</text> <text x="448" y="500">Classes</text> <text x="72" y="516">SDP</text> <text x="68" y="580">Fine-grained</text> <text x="136" y="580">QoS</text> <text x="200" y="580">enforcement</text> <text x="324" y="580">Coarse-grained</text> <text x="400" y="580">QoS</text> <text x="464" y="580">enforcement</text> <text x="76" y="596">(dedicated</text> <text x="160" y="596">resources</text> <text x="216" y="596">per</text> <text x="308" y="596">(resources</text> <text x="380" y="596">shared</text> <text x="420" y="596">by</text> <text x="468" y="596">multiple</text> <text x="56" y="612">RFC</text> <text x="92" y="612">9543</text> <text x="144" y="612">Network</text> <text x="204" y="612">Slice)</text> <text x="304" y="612">RFC</text> <text x="340" y="612">9543</text> <text x="392" y="612">Network</text> <text x="456" y="612">Slices)</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +---------------------------------------------------------------+ +-------------------+ PE | | .--------------+ | | R | | SDP | | +-----------------------------+ F | | .---------. | | | Transit link | C | | | 5G DSCP A +---------------+ | .-----------------------. | 9 | | '---------' | | +---|--> TN QoS Class 1 | | 5 | | .---------. | | | | '-----------------------' | 4 | | | 5G DSCP B +------------+ | | .-----------------------. | 3 | | '---------' | | | | | | TN QoS Class 2 | | | | .---------. | | | | | '-----------------------' | N | | | 5G DSCP C +---------+ | | | .-----------------------. | S | | '---------' | | | | | | | TN QoS Class 3 | | | | .---------. | | | | | | '-----------------------' | 1 | | | 5G DSCP D +------+ | | | | .-----------------------. | | | '---------' | | | | +--)---|--> TN QoS Class 4 | | | '--------------' | | | | | | '-----------------------' | R | .--------------+ | | | | | | .-----------------------. | F | | .---------. | | | +--)--|---|--> TN QoS Class 5 | | C | | | 5G DSCP A +------)--|--|--+ | '-----------------------' | 9 | | '---------' | | | | | | .-----------------------. | 5 | | .---------. | | | | | | | TN QoS Class 6 | | 4 | | | 5G DSCP E +------)--)--+ | '-----------------------' | 3 | | '---------' | | | | | .-----------------------. | | | .---------. | | | | | | TN QoS Class 7 | | N | | | 5G DSCP F +------)--+ | '-----------------------' | S | | '---------' | | | | .-----------------------. | | | .---------. | | +------------|--> TN QoS Class 8 | | 2 | | | 5G DSCP G +------+ | '-----------------------' | | | '---------' | | | Max 8 TN Classes | | | SDP | | +-----------------------------+ | '--------------' | | +-------------------+ | +---------------------------------------------------------------+ Fine-grained QoS enforcement Coarse-grained QoS enforcement (dedicated resources per (resources shared by multiple RFC 9543 Network Slice) RFC 9543 Network Slices) ]]></artwork> </artset> </figure> <t>Given that in deployments with a large number of 5G slices, the number of potential 5G QoS Classes is much higher than the number of TN QoS Classes, multiple 5G QoS Classes with similar characteristics--- potentially from different slices--- would be grouped with common operator-defined TN logic and mapped toathe same TN QoS Class when transported in the provider network. That is, commonPer-hopPer-Hop Behavior (PHB) <xref target="RFC2474"/> is executed on transit provider network routers for all packets grouped together. An example of this approach is outlined in <xref target="_figure-QoS-5QI-mapping-example"/>. A provider may decide to implement Diffserv-Intercon PHBs at the boundaries of its network domain <xref target="RFC8100"/>.</t><dl> <dt>Note:</dt> <dd> <t>The<aside> <t>Note: The numbers indicated in <xref target="_figure-QoS-5QI-mapping-example"/> (S-NSSAI, 5QI, DSCP, queue, etc.) are provided for illustration purposes only and should not be considered as deployment guidance.</t></dd> </dl></aside> <figure anchor="_figure-QoS-5QI-mapping-example"> <name>Example of 3GPP QoS Mapped to TN QoS</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="512" width="520" viewBox="0 0 520 512" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,48 L 8,80" fill="none" stroke="black"/> <path d="M 8,112 L 8,240" fill="none" stroke="black"/> <path d="M 8,272 L 8,464" fill="none" stroke="black"/> <path d="M 184,48 L 184,104" fill="none" stroke="black"/> <path d="M 184,120 L 184,152" fill="none" stroke="black"/> <path d="M 184,168 L 184,200" fill="none" stroke="black"/> <path d="M 184,216 L 184,240" fill="none" stroke="black"/> <path d="M 184,272 L 184,328" fill="none" stroke="black"/> <path d="M 184,344 L 184,376" fill="none" stroke="black"/> <path d="M 184,392 L 184,424" fill="none" stroke="black"/> <path d="M 184,440 L 184,464" fill="none" stroke="black"/> <path d="M 200,32 L 200,104" fill="none" stroke="black"/> <path d="M 200,120 L 200,152" fill="none" stroke="black"/> <path d="M 200,168 L 200,200" fill="none" stroke="black"/> <path d="M 200,216 L 200,328" fill="none" stroke="black"/> <path d="M 200,344 L 200,376" fill="none" stroke="black"/> <path d="M 200,392 L 200,424" fill="none" stroke="black"/> <path d="M 200,440 L 200,480" fill="none" stroke="black"/> <path d="M 216,80 L 216,104" fill="none" stroke="black"/> <path d="M 216,120 L 216,152" fill="none" stroke="black"/> <path d="M 216,168 L 216,200" fill="none" stroke="black"/> <path d="M 216,216 L 216,240" fill="none" stroke="black"/> <path d="M 216,304 L 216,328" fill="none" stroke="black"/> <path d="M 216,344 L 216,376" fill="none" stroke="black"/> <path d="M 216,392 L 216,424" fill="none" stroke="black"/> <path d="M 216,440 L 216,464" fill="none" stroke="black"/> <path d="M 312,64 L 312,104" fill="none" stroke="black"/> <path d="M 312,120 L 312,152" fill="none" stroke="black"/> <path d="M 312,168 L 312,200" fill="none" stroke="black"/> <path d="M 312,216 L 312,224" fill="none" stroke="black"/> <path d="M 312,288 L 312,328" fill="none" stroke="black"/> <path d="M 312,344 L 312,376" fill="none" stroke="black"/> <path d="M 312,392 L 312,424" fill="none" stroke="black"/> <path d="M 312,440 L 312,448" fill="none" stroke="black"/> <path d="M 336,112 L 336,200" fill="none" stroke="black"/> <path d="M 336,216 L 336,384" fill="none" stroke="black"/> <path d="M 352,208 L 352,232" fill="none" stroke="black"/> <path d="M 352,248 L 352,432" fill="none" stroke="black"/> <path d="M 496,224 L 496,240" fill="none" stroke="black"/> <path d="M 496,352 L 496,368" fill="none" stroke="black"/> <path d="M 512,32 L 512,480" fill="none" stroke="black"/> <path d="M 200,32 L 320,32" fill="none" stroke="black"/> <path d="M 376,32 L 512,32" fill="none" stroke="black"/> <path d="M 8,48 L 56,48" fill="none" stroke="black"/> <path d="M 112,48 L 184,48" fill="none" stroke="black"/> <path d="M 232,64 L 312,64" fill="none" stroke="black"/> <path d="M 40,96 L 88,96" fill="none" stroke="black"/> <path d="M 104,96 L 160,96" fill="none" stroke="black"/> <path d="M 232,96 L 288,96" fill="none" stroke="black"/> <path d="M 80,112 L 96,112" fill="none" stroke="black"/> <path d="M 176,112 L 232,112" fill="none" stroke="black"/> <path d="M 304,112 L 336,112" fill="none" stroke="black"/> <path d="M 40,128 L 88,128" fill="none" stroke="black"/> <path d="M 104,128 L 160,128" fill="none" stroke="black"/> <path d="M 232,128 L 288,128" fill="none" stroke="black"/> <path d="M 40,144 L 88,144" fill="none" stroke="black"/> <path d="M 104,144 L 160,144" fill="none" stroke="black"/> <path d="M 232,144 L 288,144" fill="none" stroke="black"/> <path d="M 80,160 L 96,160" fill="none" stroke="black"/> <path d="M 176,160 L 232,160" fill="none" stroke="black"/> <path d="M 304,160 L 336,160" fill="none" stroke="black"/> <path d="M 40,176 L 88,176" fill="none" stroke="black"/> <path d="M 104,176 L 160,176" fill="none" stroke="black"/> <path d="M 232,176 L 288,176" fill="none" stroke="black"/> <path d="M 40,192 L 88,192" fill="none" stroke="black"/> <path d="M 104,192 L 160,192" fill="none" stroke="black"/> <path d="M 232,192 L 288,192" fill="none" stroke="black"/> <path d="M 80,208 L 96,208" fill="none" stroke="black"/> <path d="M 176,208 L 232,208" fill="none" stroke="black"/> <path d="M 304,208 L 352,208" fill="none" stroke="black"/> <path d="M 392,208 L 480,208" fill="none" stroke="black"/> <path d="M 40,224 L 88,224" fill="none" stroke="black"/> <path d="M 104,224 L 160,224" fill="none" stroke="black"/> <path d="M 232,224 L 288,224" fill="none" stroke="black"/> <path d="M 8,240 L 184,240" fill="none" stroke="black"/> <path d="M 216,240 L 296,240" fill="none" stroke="black"/> <path d="M 336,240 L 376,240" fill="none" stroke="black"/> <path d="M 384,256 L 480,256" fill="none" stroke="black"/> <path d="M 8,272 L 64,272" fill="none" stroke="black"/> <path d="M 120,272 L 184,272" fill="none" stroke="black"/> <path d="M 232,288 L 312,288" fill="none" stroke="black"/> <path d="M 40,320 L 88,320" fill="none" stroke="black"/> <path d="M 104,320 L 160,320" fill="none" stroke="black"/> <path d="M 232,320 L 288,320" fill="none" stroke="black"/> <path d="M 80,336 L 96,336" fill="none" stroke="black"/> <path d="M 176,336 L 232,336" fill="none" stroke="black"/> <path d="M 304,336 L 336,336" fill="none" stroke="black"/> <path d="M 392,336 L 480,336" fill="none" stroke="black"/> <path d="M 40,352 L 88,352" fill="none" stroke="black"/> <path d="M 104,352 L 160,352" fill="none" stroke="black"/> <path d="M 232,352 L 288,352" fill="none" stroke="black"/> <path d="M 40,368 L 88,368" fill="none" stroke="black"/> <path d="M 104,368 L 160,368" fill="none" stroke="black"/> <path d="M 232,368 L 288,368" fill="none" stroke="black"/> <path d="M 352,368 L 376,368" fill="none" stroke="black"/> <path d="M 80,384 L 96,384" fill="none" stroke="black"/> <path d="M 176,384 L 232,384" fill="none" stroke="black"/> <path d="M 304,384 L 336,384" fill="none" stroke="black"/> <path d="M 384,384 L 480,384" fill="none" stroke="black"/> <path d="M 40,400 L 88,400" fill="none" stroke="black"/> <path d="M 104,400 L 160,400" fill="none" stroke="black"/> <path d="M 232,400 L 288,400" fill="none" stroke="black"/> <path d="M 40,416 L 88,416" fill="none" stroke="black"/> <path d="M 104,416 L 160,416" fill="none" stroke="black"/> <path d="M 232,416 L 288,416" fill="none" stroke="black"/> <path d="M 80,432 L 96,432" fill="none" stroke="black"/> <path d="M 176,432 L 232,432" fill="none" stroke="black"/> <path d="M 304,432 L 352,432" fill="none" stroke="black"/> <path d="M 40,448 L 88,448" fill="none" stroke="black"/> <path d="M 104,448 L 160,448" fill="none" stroke="black"/> <path d="M 232,448 L 288,448" fill="none" stroke="black"/> <path d="M 8,464 L 184,464" fill="none" stroke="black"/> <path d="M 216,464 L 296,464" fill="none" stroke="black"/> <path d="M 200,480 L 512,480" fill="none" stroke="black"/> <path d="M 232,64 C 223.16936,64 216,71.16936 216,80" fill="none" stroke="black"/> <path d="M 40,96 C 31.16936,96 24,103.16936 24,112" fill="none" stroke="black"/> <path d="M 160,96 C 168.83064,96 176,103.16936 176,112" fill="none" stroke="black"/> <path d="M 288,96 C 296.83064,96 304,103.16936 304,112" fill="none" stroke="black"/> <path d="M 40,128 C 31.16936,128 24,120.83064 24,112" fill="none" stroke="black"/> <path d="M 160,128 C 168.83064,128 176,120.83064 176,112" fill="none" stroke="black"/> <path d="M 288,128 C 296.83064,128 304,120.83064 304,112" fill="none" stroke="black"/> <path d="M 40,144 C 31.16936,144 24,151.16936 24,160" fill="none" stroke="black"/> <path d="M 160,144 C 168.83064,144 176,151.16936 176,160" fill="none" stroke="black"/> <path d="M 288,144 C 296.83064,144 304,151.16936 304,160" fill="none" stroke="black"/> <path d="M 40,176 C 31.16936,176 24,168.83064 24,160" fill="none" stroke="black"/> <path d="M 160,176 C 168.83064,176 176,168.83064 176,160" fill="none" stroke="black"/> <path d="M 288,176 C 296.83064,176 304,168.83064 304,160" fill="none" stroke="black"/> <path d="M 40,192 C 31.16936,192 24,199.16936 24,208" fill="none" stroke="black"/> <path d="M 160,192 C 168.83064,192 176,199.16936 176,208" fill="none" stroke="black"/> <path d="M 288,192 C 296.83064,192 304,199.16936 304,208" fill="none" stroke="black"/> <path d="M 392,208 C 383.16936,208 376,215.16936 376,224" fill="none" stroke="black"/> <path d="M 480,208 C 488.83064,208 496,215.16936 496,224" fill="none" stroke="black"/> <path d="M 40,224 C 31.16936,224 24,216.83064 24,208" fill="none" stroke="black"/> <path d="M 160,224 C 168.83064,224 176,216.83064 176,208" fill="none" stroke="black"/> <path d="M 288,224 C 296.83064,224 304,216.83064 304,208" fill="none" stroke="black"/> <path d="M 296,240 C 304.83064,240 312,232.83064 312,224" fill="none" stroke="black"/> <path d="M 480,256 C 488.83064,256 496,248.83064 496,240" fill="none" stroke="black"/> <path d="M 232,288 C 223.16936,288 216,295.16936 216,304" fill="none" stroke="black"/> <path d="M 40,320 C 31.16936,320 24,327.16936 24,336" fill="none" stroke="black"/> <path d="M 160,320 C 168.83064,320 176,327.16936 176,336" fill="none" stroke="black"/> <path d="M 288,320 C 296.83064,320 304,327.16936 304,336" fill="none" stroke="black"/> <path d="M 392,336 C 383.16936,336 376,343.16936 376,352" fill="none" stroke="black"/> <path d="M 480,336 C 488.83064,336 496,343.16936 496,352" fill="none" stroke="black"/> <path d="M 40,352 C 31.16936,352 24,344.83064 24,336" fill="none" stroke="black"/> <path d="M 160,352 C 168.83064,352 176,344.83064 176,336" fill="none" stroke="black"/> <path d="M 288,352 C 296.83064,352 304,344.83064 304,336" fill="none" stroke="black"/> <path d="M 40,368 C 31.16936,368 24,375.16936 24,384" fill="none" stroke="black"/> <path d="M 160,368 C 168.83064,368 176,375.16936 176,384" fill="none" stroke="black"/> <path d="M 288,368 C 296.83064,368 304,375.16936 304,384" fill="none" stroke="black"/> <path d="M 480,384 C 488.83064,384 496,376.83064 496,368" fill="none" stroke="black"/> <path d="M 40,400 C 31.16936,400 24,392.83064 24,384" fill="none" stroke="black"/> <path d="M 160,400 C 168.83064,400 176,392.83064 176,384" fill="none" stroke="black"/> <path d="M 288,400 C 296.83064,400 304,392.83064 304,384" fill="none" stroke="black"/> <path d="M 40,416 C 31.16936,416 24,423.16936 24,432" fill="none" stroke="black"/> <path d="M 160,416 C 168.83064,416 176,423.16936 176,432" fill="none" stroke="black"/> <path d="M 288,416 C 296.83064,416 304,423.16936 304,432" fill="none" stroke="black"/> <path d="M 40,448 C 31.16936,448 24,440.83064 24,432" fill="none" stroke="black"/> <path d="M 160,448 C 168.83064,448 176,440.83064 176,432" fill="none" stroke="black"/> <path d="M 288,448 C 296.83064,448 304,440.83064 304,432" fill="none" stroke="black"/> <path d="M 296,464 C 304.83064,464 312,456.83064 312,448" fill="none" stroke="black"/> <polygon class="arrowhead" points="384,368 372,362.4 372,373.6" fill="black" transform="rotate(0,376,368)"/> <polygon class="arrowhead" points="384,240 372,234.4 372,245.6" fill="black" transform="rotate(0,376,240)"/> <path class="jump" d="M 352,248 C 358,248 358,232 352,232" fill="none" stroke="black"/> <path class="jump" d="M 336,216 C 342,216 342,200 336,200" fill="none" stroke="black"/> <polygon class="arrowhead" points="240,432 228,426.4 228,437.6" fill="black" transform="rotate(0,232,432)"/> <polygon class="arrowhead" points="240,384 228,378.4 228,389.6" fill="black" transform="rotate(0,232,384)"/> <polygon class="arrowhead" points="240,336 228,330.4 228,341.6" fill="black" transform="rotate(0,232,336)"/> <polygon class="arrowhead" points="240,208 228,202.4 228,213.6" fill="black" transform="rotate(0,232,208)"/> <polygon class="arrowhead" points="240,160 228,154.4 228,165.6" fill="black" transform="rotate(0,232,160)"/> <polygon class="arrowhead" points="240,112 228,106.4 228,117.6" fill="black" transform="rotate(0,232,112)"/> <polygon class="arrowhead" points="104,432 92,426.4 92,437.6" fill="black" transform="rotate(0,96,432)"/> <polygon class="arrowhead" points="104,384 92,378.4 92,389.6" fill="black" transform="rotate(0,96,384)"/> <polygon class="arrowhead" points="104,336 92,330.4 92,341.6" fill="black" transform="rotate(0,96,336)"/> <polygon class="arrowhead" points="104,208 92,202.4 92,213.6" fill="black" transform="rotate(0,96,208)"/> <polygon class="arrowhead" points="104,160 92,154.4 92,165.6" fill="black" transform="rotate(0,96,160)"/> <polygon class="arrowhead" points="104,112 92,106.4 92,117.6" fill="black" transform="rotate(0,96,112)"/> <g class="text"> <text x="348" y="36">PE</text> <text x="84" y="52">NF-A</text> <text x="36" y="84">3GPP</text> <text x="88" y="84">S-NSSAI</text> <text x="136" y="84">100</text> <text x="256" y="84">SDP</text> <text x="16" y="100">|</text> <text x="48" y="116">5QI=1</text> <text x="128" y="116">DSCP=46</text> <text x="264" y="116">DSCP=46</text> <text x="52" y="164">5QI=65</text> <text x="128" y="164">DSCP=46</text> <text x="264" y="164">DSCP=46</text> <text x="48" y="212">5QI=7</text> <text x="128" y="212">DSCP=10</text> <text x="264" y="212">DSCP=10</text> <text x="388" y="228">TN</text> <text x="416" y="228">QoS</text> <text x="456" y="228">Class</text> <text x="488" y="228">5</text> <text x="424" y="244">Queue</text> <text x="456" y="244">5</text> <text x="92" y="276">NF-B</text> <text x="36" y="308">3GPP</text> <text x="88" y="308">S-NSSAI</text> <text x="136" y="308">200</text> <text x="256" y="308">SDP</text> <text x="48" y="340">5QI=1</text> <text x="128" y="340">DSCP=46</text> <text x="264" y="340">DSCP=46</text> <text x="388" y="356">TN</text> <text x="416" y="356">QoS</text> <text x="456" y="356">Class</text> <text x="488" y="356">1</text> <text x="424" y="372">Queue</text> <text x="456" y="372">1</text> <text x="52" y="388">5QI=65</text> <text x="128" y="388">DSCP=46</text> <text x="264" y="388">DSCP=46</text> <text x="48" y="436">5QI=7</text> <text x="128" y="436">DSCP=10</text> <text x="264" y="436">DSCP=10</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +--------------- PE -----------------+ +------ NF-A ---------+ | | | | | .----------+ | | 3GPP S-NSSAI 100 | | | SDP | | | .------. .-------. | | | .-------. | | | |5QI=1 +->DSCP=46 +------>DSCP=46 +---+ | | '------' '-------' | | | '-------' | | | | .------. .-------. | | | .-------. | | | | |5QI=65+->DSCP=46 +------>DSCP=46 +---+ | | '------' '-------' | | | '-------' | | | | .------. .-------. | | | .-------. | | | | |5QI=7 +->DSCP=10 +------>DSCP=10 +---)-+ .------------. | | '------' '-------' | | | '-------' | | | |TN QoS Class 5| | +---------------------+ | '----------' +-)--> Queue 5 | | | | | '------------' | +------- NF-B --------+ | | | | | | | .----------+ | | | | 3GPP S-NSSAI 200 | | | SDP | | | | | .------. .-------. | | | .-------. | | | | | |5QI=1 +->DSCP=46 +------>DSCP=46 +---+ | .------------. | | '------' '-------' | | | '-------' | | | |TN QoS Class 1| | | .------. .-------. | | | .-------. | | +--> Queue 1 | | | |5QI=65+->DSCP=46 +------>DSCP=46 +---+ | '------------' | | '------' '-------' | | | '-------' | | | | .------. .-------. | | | .-------. | | | | |5QI=7 +->DSCP=10 +------>DSCP=10 +-----+ | | '------' '-------' | | | '-------' | | +---------------------+ | '----------' | +--------------------------------------+ ]]></artwork> </artset> </figure> <t>In current SDO progress of 3GPP (Release 17) and O-RAN, the mapping of 5QI to DSCP is not expected to be in a per-slice fashion, where5QI to DSCP5QI-to-DSCP mapping may vary from 3GPP slice to 3GPPslice, henceslice; hence, the mapping of 5G QoS DSCP values to TN QoS Classes may be rather common.</t> <t>Like in the 5QI-unaware model, the original IP header retains theDCSPDSCP marking corresponding to 5QI (5G QoS Class), while the new header (MPLS or IPv6) carries the QoS marking related to TN QoS Class. Based on the TN QoS Class marking, per-hop behavior for all aggregated 5G QoS Classes from all RFC 9543 Network Slices is executed on the provider network transit links. Provider network transit routers do not evaluate the original IP header forQoS relatedQoS-related decisions. The original DSCP marking retained in the original IP header is used at the PE for fine-grained inbound/outbound enforcement per slice and per 5G QoS Classinbound/outbound enforcementon the AC.</t><t>In<!-- [rfced] Please clarify "most commonly up 4 or 8 traffic classes". (Also, we suggest removing "granular" as it's redundant with "fine-grained".) Original: In the 5QI-aware model, compared to the 5QI-unaware model, provider network edge resources are controlled in an even more granular,fine-grainedfine- grained manner, with dedicated resource allocation for each RFC 9543 Network Slice and dedicated resource allocation for number of traffic classes (most commonly up 4 or 8 traffic classes, depending on the Hardware capability of the equipment) within each RFC 9543 Network Slice. Perhaps: In the 5QI-aware model, compared to the 5QI-unaware model, provider network edge resources are controlled in an even more fine-grained manner, with dedicated resource allocation for each RFC 9543 Network Slice and for a number of traffic classes (most commonly, 4 or 8 traffic classes, depending on the hardware capability of the equipment) within each RFC 9543 Network Slice. Or: In the 5QI-aware model, compared to the 5QI-unaware model, provider network edge resources are controlled in an even more fine-grained manner, with dedicated resource allocation for each RFC 9543 Network Slice and for a number of traffic classes (most commonly, up to 4 or 8 traffic classes, depending on the hardware capability of the equipment) within each RFC 9543 Network Slice. --> <t>In the 5QI-aware model, compared to the 5QI-unaware model, provider network edge resources are controlled in an even more granular, fine-grained manner, with dedicated resource allocation for each RFC 9543 Network Slice and for a number of traffic classes (most commonly up 4 or 8 traffic classes, depending on the hardware capability of the equipment) within each RFC 9543 Network Slice.</t> <section anchor="inbound-edge-resource-control"> <name>Inbound Edge Resource Control</name> <t>Compared to the 5QI-unaware model, admission control (traffic conditioning) in the 5QI-aware model is more granular, as itenforcesnot onlyper sliceenforces per-slice capacity constraints, but mayas wellalso enforce the constraints per 5G QoS Class within each slice.</t> <t>A 5G slice using multiple 5QIs can potentially specify rates in one of the following ways:</t> <ul spacing="normal"> <li> <t>Rates per traffic class (CIR or CIR+PIR), no rate per slice (sum of rates per class gives the rate per slice).</t> </li> <li> <t>Rate per slice (CIR or CIR+PIR), and rates per prioritized (premium) traffic classes (CIR only).Best effortA best-effort traffic class uses the bandwidth (within slice CIR/PIR) not consumed by prioritized classes.</t> </li> </ul> <t>In the first option, the slice admission control is executed with traffic class granularity, as outlined in <xref target="_figure-20"/>. In this model, if a premium class doesn't consume all available class capacity, it cannot be reused by a non-premium (i.e.,Best Effort)best effort) class.</t> <figure anchor="_figure-20"> <name>Ingress Slice Admission Control(5QI-aware(5QI-Aware Model)</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="560" width="408" viewBox="0 0 408 560" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 296,48 L 296,192" fill="none" stroke="black"/> <path d="M 296,224 L 296,352" fill="none" stroke="black"/> <path d="M 296,384 L 296,528" fill="none" stroke="black"/> <path d="M 320,32 L 320,48" fill="none" stroke="black"/> <path d="M 320,528 L 320,544" fill="none" stroke="black"/> <path d="M 352,48 L 352,192" fill="none" stroke="black"/> <path d="M 352,224 L 352,352" fill="none" stroke="black"/> <path d="M 352,384 L 352,528" fill="none" stroke="black"/> <path d="M 400,32 L 400,544" fill="none" stroke="black"/> <path d="M 320,32 L 400,32" fill="none" stroke="black"/> <path d="M 296,48 L 312,48" fill="none" stroke="black"/> <path d="M 328,48 L 352,48" fill="none" stroke="black"/> <path d="M 144,80 L 184,80" fill="none" stroke="black"/> <path d="M 208,80 L 288,80" fill="none" stroke="black"/> <path d="M 304,80 L 320,80" fill="none" stroke="black"/> <path d="M 144,96 L 184,96" fill="none" stroke="black"/> <path d="M 208,96 L 288,96" fill="none" stroke="black"/> <path d="M 304,96 L 320,96" fill="none" stroke="black"/> <path d="M 144,112 L 184,112" fill="none" stroke="black"/> <path d="M 208,112 L 288,112" fill="none" stroke="black"/> <path d="M 304,112 L 320,112" fill="none" stroke="black"/> <path d="M 144,160 L 184,160" fill="none" stroke="black"/> <path d="M 208,160 L 288,160" fill="none" stroke="black"/> <path d="M 304,160 L 320,160" fill="none" stroke="black"/> <path d="M 304,208 L 344,208" fill="none" stroke="black"/> <path d="M 144,240 L 184,240" fill="none" stroke="black"/> <path d="M 208,240 L 288,240" fill="none" stroke="black"/> <path d="M 304,240 L 320,240" fill="none" stroke="black"/> <path d="M 144,256 L 184,256" fill="none" stroke="black"/> <path d="M 208,256 L 288,256" fill="none" stroke="black"/> <path d="M 304,256 L 320,256" fill="none" stroke="black"/> <path d="M 144,272 L 184,272" fill="none" stroke="black"/> <path d="M 208,272 L 288,272" fill="none" stroke="black"/> <path d="M 304,272 L 320,272" fill="none" stroke="black"/> <path d="M 144,320 L 184,320" fill="none" stroke="black"/> <path d="M 208,320 L 288,320" fill="none" stroke="black"/> <path d="M 304,320 L 320,320" fill="none" stroke="black"/> <path d="M 304,368 L 344,368" fill="none" stroke="black"/> <path d="M 144,400 L 184,400" fill="none" stroke="black"/> <path d="M 208,400 L 288,400" fill="none" stroke="black"/> <path d="M 304,400 L 320,400" fill="none" stroke="black"/> <path d="M 144,416 L 184,416" fill="none" stroke="black"/> <path d="M 208,416 L 288,416" fill="none" stroke="black"/> <path d="M 304,416 L 320,416" fill="none" stroke="black"/> <path d="M 144,432 L 184,432" fill="none" stroke="black"/> <path d="M 208,432 L 288,432" fill="none" stroke="black"/> <path d="M 304,432 L 320,432" fill="none" stroke="black"/> <path d="M 136,480 L 184,480" fill="none" stroke="black"/> <path d="M 208,480 L 288,480" fill="none" stroke="black"/> <path d="M 304,480 L 320,480" fill="none" stroke="black"/> <path d="M 296,528 L 312,528" fill="none" stroke="black"/> <path d="M 328,528 L 352,528" fill="none" stroke="black"/> <path d="M 320,544 L 400,544" fill="none" stroke="black"/> <polygon class="arrowhead" points="328,480 316,474.4 316,485.6" fill="black" transform="rotate(0,320,480)"/> <polygon class="arrowhead" points="328,432 316,426.4 316,437.6" fill="black" transform="rotate(0,320,432)"/> <polygon class="arrowhead" points="328,416 316,410.4 316,421.6" fill="black" transform="rotate(0,320,416)"/> <polygon class="arrowhead" points="328,400 316,394.4 316,405.6" fill="black" transform="rotate(0,320,400)"/> <polygon class="arrowhead" points="328,320 316,314.4 316,325.6" fill="black" transform="rotate(0,320,320)"/> <polygon class="arrowhead" points="328,272 316,266.4 316,277.6" fill="black" transform="rotate(0,320,272)"/> <polygon class="arrowhead" points="328,256 316,250.4 316,261.6" fill="black" transform="rotate(0,320,256)"/> <polygon class="arrowhead" points="328,240 316,234.4 316,245.6" fill="black" transform="rotate(0,320,240)"/> <polygon class="arrowhead" points="328,160 316,154.4 316,165.6" fill="black" transform="rotate(0,320,160)"/> <polygon class="arrowhead" points="328,112 316,106.4 316,117.6" fill="black" transform="rotate(0,320,112)"/> <polygon class="arrowhead" points="328,96 316,90.4 316,101.6" fill="black" transform="rotate(0,320,96)"/> <polygon class="arrowhead" points="328,80 316,74.4 316,85.6" fill="black" transform="rotate(0,320,80)"/> <g class="text"> <text x="192" y="36">Class</text> <text x="192" y="52">policer</text> <text x="40" y="84">5Q-QoS-A:</text> <text x="108" y="84">CIR-1A</text> <text x="196" y="84"><></text> <text x="336" y="84">S</text> <text x="40" y="100">5Q-QoS-B:</text> <text x="108" y="100">CIR-1B</text> <text x="196" y="100"><></text> <text x="336" y="100">l</text> <text x="40" y="116">5Q-QoS-C:</text> <text x="108" y="116">CIR-1C</text> <text x="196" y="116"><></text> <text x="336" y="116">i</text> <text x="336" y="132">c</text> <text x="336" y="148">e</text> <text x="36" y="164">BE</text> <text x="92" y="164">CIR/PIR-1D</text> <text x="196" y="164"><></text> <text x="376" y="164">A</text> <text x="336" y="180">1</text> <text x="376" y="180">t</text> <text x="376" y="196">t</text> <text x="376" y="212">a</text> <text x="376" y="228">c</text> <text x="40" y="244">5Q-QoS-A:</text> <text x="108" y="244">CIR-2A</text> <text x="196" y="244"><></text> <text x="336" y="244">S</text> <text x="376" y="244">h</text> <text x="40" y="260">5Q-QoS-B:</text> <text x="108" y="260">CIR-2B</text> <text x="196" y="260"><></text> <text x="336" y="260">l</text> <text x="376" y="260">m</text> <text x="40" y="276">5Q-QoS-C:</text> <text x="108" y="276">CIR-2C</text> <text x="196" y="276"><></text> <text x="336" y="276">i</text> <text x="376" y="276">e</text> <text x="336" y="292">c</text> <text x="376" y="292">n</text> <text x="336" y="308">e</text> <text x="376" y="308">t</text> <text x="36" y="324">BE</text> <text x="92" y="324">CIR/PIR-2D</text> <text x="196" y="324"><></text> <text x="336" y="340">2</text> <text x="376" y="340">C</text> <text x="376" y="356">i</text> <text x="376" y="372">r</text> <text x="376" y="388">c</text> <text x="40" y="404">5Q-QoS-A:</text> <text x="108" y="404">CIR-3A</text> <text x="196" y="404"><></text> <text x="336" y="404">S</text> <text x="376" y="404">u</text> <text x="40" y="420">5Q-QoS-B:</text> <text x="108" y="420">CIR-3B</text> <text x="196" y="420"><></text> <text x="336" y="420">l</text> <text x="376" y="420">i</text> <text x="40" y="436">5Q-QoS-C:</text> <text x="108" y="436">CIR-3C</text> <text x="196" y="436"><></text> <text x="336" y="436">i</text> <text x="376" y="436">t</text> <text x="336" y="452">c</text> <text x="336" y="468">e</text> <text x="36" y="484">BE</text> <text x="92" y="484">CIR/PIR-3D</text> <text x="196" y="484"><></text> <text x="336" y="500">3</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ Class +---------+ policer +--|---+ | | | | 5Q-QoS-A: CIR-1A ------<>-----------|--> S | | 5Q-QoS-B: CIR-1B ------<>-----------|--> l | | 5Q-QoS-C: CIR-1C ------<>-----------|--> i | | | c | | | e | | BE CIR/PIR-1D ------<>-----------|--> | A | | 1 | t | | | t | ------ a | | | c | 5Q-QoS-A: CIR-2A ------<>-----------|--> S | h | 5Q-QoS-B: CIR-2B ------<>-----------|--> l | m | 5Q-QoS-C: CIR-2C ------<>-----------|--> i | e | | c | n | | e | t | BE CIR/PIR-2D ------<>-----------|--> | | | 2 | C | | | i | ------ r | | | c | 5Q-QoS-A: CIR-3A ------<>-----------|--> S | u | 5Q-QoS-B: CIR-3B ------<>-----------|--> l | i | 5Q-QoS-C: CIR-3C ------<>-----------|--> i | t | | c | | | e | | BE CIR/PIR-3D-------<>-----------|--> | | | 3 | | | | | +--|---+ | +---------+ ]]></artwork> </artset> </figure> <t>The secondmodeloption combines the advantages of the 5QI-unaware model(per slice(per-slice admission control) withthe per traffic classper-traffic-class admission control, as outlined in <xref target="_figure-20"/>. Ingress admission control is at class granularity for premium classes (CIR only).Non-premiumA non-premium class (i.e.,Best Effort)best-effort class) has no separate class admission control policy, but it is allowed to use the entire slice capacity, which is available at any givenmoment. I.e.,moment (i.e., slice capacity, which is not consumed by premiumclasses.classes). It is a hierarchical model, as depicted in <xref target="_figure-21"/>.</t> <figure anchor="_figure-21"> <name>Ingress Slice Admission Control(5QI-aware)(5QI-Aware Model) - Hierarchical</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="576" width="408" viewBox="0 0 408 576" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 256,80 L 256,208" fill="none" stroke="black"/> <path d="M 256,240 L 256,368" fill="none" stroke="black"/> <path d="M 256,400 L 256,528" fill="none" stroke="black"/> <path d="M 272,80 L 272,208" fill="none" stroke="black"/> <path d="M 272,240 L 272,368" fill="none" stroke="black"/> <path d="M 272,400 L 272,528" fill="none" stroke="black"/> <path d="M 296,64 L 296,208" fill="none" stroke="black"/> <path d="M 296,240 L 296,368" fill="none" stroke="black"/> <path d="M 296,400 L 296,544" fill="none" stroke="black"/> <path d="M 320,48 L 320,64" fill="none" stroke="black"/> <path d="M 320,544 L 320,560" fill="none" stroke="black"/> <path d="M 352,64 L 352,208" fill="none" stroke="black"/> <path d="M 352,240 L 352,368" fill="none" stroke="black"/> <path d="M 352,400 L 352,544" fill="none" stroke="black"/> <path d="M 400,48 L 400,560" fill="none" stroke="black"/> <path d="M 320,48 L 400,48" fill="none" stroke="black"/> <path d="M 296,64 L 312,64" fill="none" stroke="black"/> <path d="M 328,64 L 352,64" fill="none" stroke="black"/> <path d="M 144,96 L 168,96" fill="none" stroke="black"/> <path d="M 192,96 L 248,96" fill="none" stroke="black"/> <path d="M 304,96 L 320,96" fill="none" stroke="black"/> <path d="M 144,112 L 168,112" fill="none" stroke="black"/> <path d="M 192,112 L 248,112" fill="none" stroke="black"/> <path d="M 304,112 L 320,112" fill="none" stroke="black"/> <path d="M 144,128 L 168,128" fill="none" stroke="black"/> <path d="M 192,128 L 248,128" fill="none" stroke="black"/> <path d="M 304,128 L 320,128" fill="none" stroke="black"/> <path d="M 144,176 L 248,176" fill="none" stroke="black"/> <path d="M 304,176 L 320,176" fill="none" stroke="black"/> <path d="M 304,224 L 344,224" fill="none" stroke="black"/> <path d="M 144,256 L 168,256" fill="none" stroke="black"/> <path d="M 192,256 L 248,256" fill="none" stroke="black"/> <path d="M 304,256 L 320,256" fill="none" stroke="black"/> <path d="M 144,272 L 168,272" fill="none" stroke="black"/> <path d="M 192,272 L 248,272" fill="none" stroke="black"/> <path d="M 304,272 L 320,272" fill="none" stroke="black"/> <path d="M 144,288 L 168,288" fill="none" stroke="black"/> <path d="M 192,288 L 248,288" fill="none" stroke="black"/> <path d="M 304,288 L 320,288" fill="none" stroke="black"/> <path d="M 144,336 L 248,336" fill="none" stroke="black"/> <path d="M 304,336 L 320,336" fill="none" stroke="black"/> <path d="M 304,384 L 344,384" fill="none" stroke="black"/> <path d="M 144,416 L 168,416" fill="none" stroke="black"/> <path d="M 192,416 L 248,416" fill="none" stroke="black"/> <path d="M 304,416 L 320,416" fill="none" stroke="black"/> <path d="M 144,432 L 168,432" fill="none" stroke="black"/> <path d="M 192,432 L 248,432" fill="none" stroke="black"/> <path d="M 304,432 L 320,432" fill="none" stroke="black"/> <path d="M 144,448 L 168,448" fill="none" stroke="black"/> <path d="M 192,448 L 216,448" fill="none" stroke="black"/> <path d="M 232,448 L 248,448" fill="none" stroke="black"/> <path d="M 304,448 L 320,448" fill="none" stroke="black"/> <path d="M 144,496 L 248,496" fill="none" stroke="black"/> <path d="M 304,496 L 320,496" fill="none" stroke="black"/> <path d="M 296,544 L 312,544" fill="none" stroke="black"/> <path d="M 328,544 L 352,544" fill="none" stroke="black"/> <path d="M 320,560 L 400,560" fill="none" stroke="black"/> <polygon class="arrowhead" points="328,496 316,490.4 316,501.6" fill="black" transform="rotate(0,320,496)"/> <polygon class="arrowhead" points="328,448 316,442.4 316,453.6" fill="black" transform="rotate(0,320,448)"/> <polygon class="arrowhead" points="328,432 316,426.4 316,437.6" fill="black" transform="rotate(0,320,432)"/> <polygon class="arrowhead" points="328,416 316,410.4 316,421.6" fill="black" transform="rotate(0,320,416)"/> <polygon class="arrowhead" points="328,336 316,330.4 316,341.6" fill="black" transform="rotate(0,320,336)"/> <polygon class="arrowhead" points="328,288 316,282.4 316,293.6" fill="black" transform="rotate(0,320,288)"/> <polygon class="arrowhead" points="328,272 316,266.4 316,277.6" fill="black" transform="rotate(0,320,272)"/> <polygon class="arrowhead" points="328,256 316,250.4 316,261.6" fill="black" transform="rotate(0,320,256)"/> <polygon class="arrowhead" points="328,176 316,170.4 316,181.6" fill="black" transform="rotate(0,320,176)"/> <polygon class="arrowhead" points="328,128 316,122.4 316,133.6" fill="black" transform="rotate(0,320,128)"/> <polygon class="arrowhead" points="328,112 316,106.4 316,117.6" fill="black" transform="rotate(0,320,112)"/> <polygon class="arrowhead" points="328,96 316,90.4 316,101.6" fill="black" transform="rotate(0,320,96)"/> <g class="text"> <text x="264" y="36">Slice</text> <text x="264" y="52">policer</text> <text x="176" y="68">Class</text> <text x="176" y="84">policer</text> <text x="264" y="84">-</text> <text x="40" y="100">5Q-QoS-A:</text> <text x="108" y="100">CIR-1A</text> <text x="180" y="100"><></text> <text x="264" y="100">-</text> <text x="284" y="100">--</text> <text x="336" y="100">S</text> <text x="40" y="116">5Q-QoS-B:</text> <text x="108" y="116">CIR-1B</text> <text x="180" y="116"><></text> <text x="264" y="116">-</text> <text x="284" y="116">--</text> <text x="336" y="116">l</text> <text x="40" y="132">5Q-QoS-C:</text> <text x="108" y="132">CIR-1C</text> <text x="180" y="132"><></text> <text x="264" y="132">-</text> <text x="284" y="132">--</text> <text x="336" y="132">i</text> <text x="336" y="148">c</text> <text x="336" y="164">e</text> <text x="36" y="180">BE</text> <text x="92" y="180">CIR/PIR-1D</text> <text x="264" y="180">-</text> <text x="284" y="180">--</text> <text x="376" y="180">A</text> <text x="336" y="196">1</text> <text x="376" y="196">t</text> <text x="264" y="212">-</text> <text x="376" y="212">t</text> <text x="376" y="228">a</text> <text x="264" y="244">-</text> <text x="376" y="244">c</text> <text x="40" y="260">5Q-QoS-A:</text> <text x="108" y="260">CIR-2A</text> <text x="180" y="260"><></text> <text x="264" y="260">-</text> <text x="284" y="260">--</text> <text x="336" y="260">S</text> <text x="376" y="260">h</text> <text x="40" y="276">5Q-QoS-B:</text> <text x="108" y="276">CIR-2B</text> <text x="180" y="276"><></text> <text x="264" y="276">-</text> <text x="284" y="276">--</text> <text x="336" y="276">l</text> <text x="376" y="276">m</text> <text x="40" y="292">5Q-QoS-C:</text> <text x="108" y="292">CIR-2C</text> <text x="180" y="292"><></text> <text x="264" y="292">-</text> <text x="284" y="292">--</text> <text x="336" y="292">i</text> <text x="376" y="292">e</text> <text x="336" y="308">c</text> <text x="376" y="308">n</text> <text x="336" y="324">e</text> <text x="376" y="324">t</text> <text x="36" y="340">BE</text> <text x="92" y="340">CIR/PIR-2D</text> <text x="264" y="340">-</text> <text x="284" y="340">--</text> <text x="336" y="356">2</text> <text x="376" y="356">C</text> <text x="264" y="372">-</text> <text x="376" y="372">i</text> <text x="376" y="388">r</text> <text x="264" y="404">-</text> <text x="376" y="404">c</text> <text x="40" y="420">5Q-QoS-A:</text> <text x="108" y="420">CIR-3A</text> <text x="180" y="420"><></text> <text x="264" y="420">-</text> <text x="284" y="420">--</text> <text x="336" y="420">S</text> <text x="376" y="420">u</text> <text x="40" y="436">5Q-QoS-B:</text> <text x="108" y="436">CIR-3B</text> <text x="180" y="436"><></text> <text x="264" y="436">-</text> <text x="284" y="436">--</text> <text x="336" y="436">l</text> <text x="376" y="436">i</text> <text x="40" y="452">5Q-QoS-C:</text> <text x="108" y="452">CIR-3C</text> <text x="180" y="452"><></text> <text x="264" y="452">-</text> <text x="284" y="452">--</text> <text x="336" y="452">i</text> <text x="376" y="452">t</text> <text x="336" y="468">c</text> <text x="336" y="484">e</text> <text x="36" y="500">BE</text> <text x="92" y="500">CIR/PIR-3D</text> <text x="264" y="500">-</text> <text x="284" y="500">--</text> <text x="336" y="516">3</text> <text x="264" y="532">-</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ Slice policer +---------+ Class +--|---+ | policer .-. | | | 5Q-QoS-A: CIR-1A ----<>--------|-|--|--> S | | 5Q-QoS-B: CIR-1B ----<>--------|-|--|--> l | | 5Q-QoS-C: CIR-1C ----<>--------|-|--|--> i | | | | | c | | | | | e | | BE CIR/PIR-1D --------------|-|--|--> | A | | | | 1 | t | '-' | | t | ------ a | .-. | | c | 5Q-QoS-A: CIR-2A ----<>--------|-|--|--> S | h | 5Q-QoS-B: CIR-2B ----<>--------|-|--|--> l | m | 5Q-QoS-C: CIR-2C ----<>--------|-|--|--> i | e | | | | c | n | | | | e | t | BE CIR/PIR-2D --------------|-|--|--> | | | | | 2 | C | '-' | | i | ------ r | .-. | | c | 5Q-QoS-A: CIR-3A ----<>--------|-|--|--> S | u | 5Q-QoS-B: CIR-3B ----<>--------|-|--|--> l | i | 5Q-QoS-C: CIR-3C ----<>---- ---|-|--|--> i | t | | | | c | | | | | e | | BE CIR/PIR-3D --------------|-|--|--> | | | | | 3 | | '-' | | | +--|---+ | +---------+ ]]></artwork> </artset> </figure> </section> <section anchor="outbound-edge-resource-control-1"> <name>Outbound Edge Resource Control</name> <t><xref target="_figure-22"/> outlines the outbound edge resource control model at the transport network layer for 5QI-aware slices. Each slice is assigned multiple egress queues. The sum of queue weights, which are 5Q QoS queue CIRs within the slice, should not exceed the CIR of the slice itself. And,similarlysimilar to the 5QI-aware model, the sum of slice CIRs should not exceed the physical capacity of the AC.</t> <figure anchor="_figure-22"> <name>Egress Slice Admission Control(5QI-aware)</name>(5QI-Aware Model)</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="656" width="552" viewBox="0 0 552 656" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 32,32 L 32,640" fill="none" stroke="black"/> <path d="M 80,48 L 80,624" fill="none" stroke="black"/> <path d="M 112,32 L 112,48" fill="none" stroke="black"/> <path d="M 112,624 L 112,640" fill="none" stroke="black"/> <path d="M 144,48 L 144,64" fill="none" stroke="black"/> <path d="M 144,240 L 144,272" fill="none" stroke="black"/> <path d="M 144,312 L 144,376" fill="none" stroke="black"/> <path d="M 144,432 L 144,456" fill="none" stroke="black"/> <path d="M 144,504 L 144,568" fill="none" stroke="black"/> <path d="M 384,56 L 384,248" fill="none" stroke="black"/> <path d="M 384,264 L 384,320" fill="none" stroke="black"/> <path d="M 384,352 L 384,424" fill="none" stroke="black"/> <path d="M 384,440 L 384,592" fill="none" stroke="black"/> <path d="M 32,32 L 112,32" fill="none" stroke="black"/> <path d="M 80,48 L 104,48" fill="none" stroke="black"/> <path d="M 120,48 L 144,48" fill="none" stroke="black"/> <path d="M 128,64 L 136,64" fill="none" stroke="black"/> <path d="M 152,64 L 352,64" fill="none" stroke="black"/> <path d="M 8,80 L 24,80" fill="none" stroke="black"/> <path d="M 40,80 L 72,80" fill="none" stroke="black"/> <path d="M 88,80 L 104,80" fill="none" stroke="black"/> <path d="M 120,80 L 136,80" fill="none" stroke="black"/> <path d="M 128,96 L 352,96" fill="none" stroke="black"/> <path d="M 128,112 L 352,112" fill="none" stroke="black"/> <path d="M 8,128 L 24,128" fill="none" stroke="black"/> <path d="M 40,128 L 72,128" fill="none" stroke="black"/> <path d="M 120,128 L 136,128" fill="none" stroke="black"/> <path d="M 128,144 L 352,144" fill="none" stroke="black"/> <path d="M 128,160 L 352,160" fill="none" stroke="black"/> <path d="M 8,176 L 24,176" fill="none" stroke="black"/> <path d="M 40,176 L 72,176" fill="none" stroke="black"/> <path d="M 88,176 L 104,176" fill="none" stroke="black"/> <path d="M 120,176 L 136,176" fill="none" stroke="black"/> <path d="M 128,192 L 352,192" fill="none" stroke="black"/> <path d="M 128,208 L 352,208" fill="none" stroke="black"/> <path d="M 8,224 L 24,224" fill="none" stroke="black"/> <path d="M 40,224 L 72,224" fill="none" stroke="black"/> <path d="M 88,224 L 104,224" fill="none" stroke="black"/> <path d="M 120,224 L 136,224" fill="none" stroke="black"/> <path d="M 128,240 L 136,240" fill="none" stroke="black"/> <path d="M 152,240 L 352,240" fill="none" stroke="black"/> <path d="M 80,256 L 144,256" fill="none" stroke="black"/> <path d="M 128,272 L 136,272" fill="none" stroke="black"/> <path d="M 152,272 L 352,272" fill="none" stroke="black"/> <path d="M 128,304 L 352,304" fill="none" stroke="black"/> <path d="M 128,384 L 352,384" fill="none" stroke="black"/> <path d="M 128,416 L 352,416" fill="none" stroke="black"/> <path d="M 80,432 L 144,432" fill="none" stroke="black"/> <path d="M 128,464 L 352,464" fill="none" stroke="black"/> <path d="M 128,496 L 352,496" fill="none" stroke="black"/> <path d="M 128,576 L 352,576" fill="none" stroke="black"/> <path d="M 128,608 L 352,608" fill="none" stroke="black"/> <path d="M 80,624 L 104,624" fill="none" stroke="black"/> <path d="M 120,624 L 144,624" fill="none" stroke="black"/> <path d="M 32,640 L 112,640" fill="none" stroke="black"/> <path d="M 128,64 C 119.16936,64 112,71.16936 112,80" fill="none" stroke="black"/> <path d="M 352,64 C 360.83064,64 368,71.16936 368,80" fill="none" stroke="black"/> <path d="M 128,96 C 119.16936,96 112,88.83064 112,80" fill="none" stroke="black"/> <path d="M 352,96 C 360.83064,96 368,88.83064 368,80" fill="none" stroke="black"/> <path d="M 128,112 C 119.16936,112 112,119.16936 112,128" fill="none" stroke="black"/> <path d="M 352,112 C 360.83064,112 368,119.16936 368,128" fill="none" stroke="black"/> <path d="M 128,144 C 119.16936,144 112,136.83064 112,128" fill="none" stroke="black"/> <path d="M 352,144 C 360.83064,144 368,136.83064 368,128" fill="none" stroke="black"/> <path d="M 128,160 C 119.16936,160 112,167.16936 112,176" fill="none" stroke="black"/> <path d="M 352,160 C 360.83064,160 368,167.16936 368,176" fill="none" stroke="black"/> <path d="M 128,192 C 119.16936,192 112,184.83064 112,176" fill="none" stroke="black"/> <path d="M 352,192 C 360.83064,192 368,184.83064 368,176" fill="none" stroke="black"/> <path d="M 128,208 C 119.16936,208 112,215.16936 112,224" fill="none" stroke="black"/> <path d="M 352,208 C 360.83064,208 368,215.16936 368,224" fill="none" stroke="black"/> <path d="M 128,240 C 119.16936,240 112,232.83064 112,224" fill="none" stroke="black"/> <path d="M 352,240 C 360.83064,240 368,232.83064 368,224" fill="none" stroke="black"/> <path d="M 128,272 C 119.16936,272 112,279.16936 112,288" fill="none" stroke="black"/> <path d="M 352,272 C 360.83064,272 368,279.16936 368,288" fill="none" stroke="black"/> <path d="M 128,304 C 119.16936,304 112,296.83064 112,288" fill="none" stroke="black"/> <path d="M 352,304 C 360.83064,304 368,296.83064 368,288" fill="none" stroke="black"/> <path d="M 128,384 C 119.16936,384 112,391.16936 112,400" fill="none" stroke="black"/> <path d="M 352,384 C 360.83064,384 368,391.16936 368,400" fill="none" stroke="black"/> <path d="M 128,416 C 119.16936,416 112,408.83064 112,400" fill="none" stroke="black"/> <path d="M 352,416 C 360.83064,416 368,408.83064 368,400" fill="none" stroke="black"/> <path d="M 128,464 C 119.16936,464 112,471.16936 112,480" fill="none" stroke="black"/> <path d="M 352,464 C 360.83064,464 368,471.16936 368,480" fill="none" stroke="black"/> <path d="M 128,496 C 119.16936,496 112,488.83064 112,480" fill="none" stroke="black"/> <path d="M 352,496 C 360.83064,496 368,488.83064 368,480" fill="none" stroke="black"/> <path d="M 128,576 C 119.16936,576 112,583.16936 112,592" fill="none" stroke="black"/> <path d="M 352,576 C 360.83064,576 368,583.16936 368,592" fill="none" stroke="black"/> <path d="M 128,608 C 119.16936,608 112,600.83064 112,592" fill="none" stroke="black"/> <path d="M 352,608 C 360.83064,608 368,600.83064 368,592" fill="none" stroke="black"/> <polygon class="arrowhead" points="144,224 132,218.4 132,229.6" fill="black" transform="rotate(0,136,224)"/> <polygon class="arrowhead" points="144,176 132,170.4 132,181.6" fill="black" transform="rotate(0,136,176)"/> <polygon class="arrowhead" points="144,128 132,122.4 132,133.6" fill="black" transform="rotate(0,136,128)"/> <polygon class="arrowhead" points="144,80 132,74.4 132,85.6" fill="black" transform="rotate(0,136,80)"/> <g class="text"> <text x="192" y="36">QoS</text> <text x="236" y="36">output</text> <text x="292" y="36">queues</text> <text x="160" y="52">-</text> <text x="176" y="52">-</text> <text x="192" y="52">-</text> <text x="208" y="52">-</text> <text x="224" y="52">-</text> <text x="240" y="52">-</text> <text x="256" y="52">-</text> <text x="272" y="52">-</text> <text x="288" y="52">-</text> <text x="304" y="52">-</text> <text x="320" y="52">-</text> <text x="336" y="52">-</text> <text x="352" y="52">-</text> <text x="368" y="52">-</text> <text x="384" y="52">-</text> <text x="400" y="52">-</text> <text x="416" y="52">-</text> <text x="432" y="52">-</text> <text x="448" y="52">-</text> <text x="464" y="52">-</text> <text x="480" y="52">-</text> <text x="496" y="52">-</text> <text x="512" y="52">-</text> <text x="528" y="52">-</text> <text x="544" y="52">-</text> <text x="376" y="68">\</text> <text x="392" y="68">/</text> <text x="184" y="84">5Q-QoS-A:</text> <text x="284" y="84">w-5Q-QoS-A-CIR</text> <text x="96" y="100">S</text> <text x="96" y="116">l</text> <text x="96" y="132">-i-</text> <text x="184" y="132">5Q-QoS-B:</text> <text x="284" y="132">w-5Q-QoS-B-CIR</text> <text x="96" y="148">c</text> <text x="476" y="148">weight-Slice-1-CIR</text> <text x="96" y="164">e</text> <text x="472" y="164">shaping-Slice-1-PIR</text> <text x="184" y="180">5Q-QoS-C:</text> <text x="284" y="180">w-5Q-QoS-C-CIR</text> <text x="96" y="196">1</text> <text x="164" y="228">Best</text> <text x="212" y="228">Effort</text> <text x="288" y="228">(remainder)</text> <text x="376" y="244">/</text> <text x="392" y="244">\</text> <text x="56" y="260">A</text> <text x="160" y="260">-</text> <text x="176" y="260">-</text> <text x="192" y="260">-</text> <text x="208" y="260">-</text> <text x="224" y="260">-</text> <text x="240" y="260">-</text> <text x="256" y="260">-</text> <text x="272" y="260">-</text> <text x="288" y="260">-</text> <text x="304" y="260">-</text> <text x="320" y="260">-</text> <text x="336" y="260">-</text> <text x="352" y="260">-</text> <text x="368" y="260">-</text> <text x="384" y="260">-</text> <text x="400" y="260">-</text> <text x="416" y="260">-</text> <text x="432" y="260">-</text> <text x="448" y="260">-</text> <text x="464" y="260">-</text> <text x="480" y="260">-</text> <text x="496" y="260">-</text> <text x="512" y="260">-</text> <text x="528" y="260">-</text> <text x="544" y="260">-</text> <text x="56" y="276">t</text> <text x="376" y="276">\</text> <text x="392" y="276">/</text> <text x="56" y="292">t</text> <text x="56" y="308">a</text> <text x="56" y="324">c</text> <text x="96" y="324">S</text> <text x="56" y="340">h</text> <text x="96" y="340">l</text> <text x="56" y="356">m</text> <text x="96" y="356">i</text> <text x="156" y="356">..</text> <text x="476" y="356">weight-Slice-2-CIR</text> <text x="56" y="372">e</text> <text x="96" y="372">c</text> <text x="472" y="372">shaping-Slice-2-PIR</text> <text x="56" y="388">n</text> <text x="96" y="388">e</text> <text x="56" y="404">t</text> <text x="96" y="420">2</text> <text x="376" y="420">/</text> <text x="392" y="420">\</text> <text x="56" y="436">C</text> <text x="160" y="436">-</text> <text x="176" y="436">-</text> <text x="192" y="436">-</text> <text x="208" y="436">-</text> <text x="224" y="436">-</text> <text x="240" y="436">-</text> <text x="256" y="436">-</text> <text x="272" y="436">-</text> <text x="288" y="436">-</text> <text x="304" y="436">-</text> <text x="320" y="436">-</text> <text x="336" y="436">-</text> <text x="352" y="436">-</text> <text x="368" y="436">-</text> <text x="384" y="436">-</text> <text x="400" y="436">-</text> <text x="416" y="436">-</text> <text x="432" y="436">-</text> <text x="448" y="436">-</text> <text x="464" y="436">-</text> <text x="480" y="436">-</text> <text x="496" y="436">-</text> <text x="512" y="436">-</text> <text x="528" y="436">-</text> <text x="544" y="436">-</text> <text x="56" y="452">i</text> <text x="376" y="452">\</text> <text x="392" y="452">/</text> <text x="56" y="468">r</text> <text x="56" y="484">c</text> <text x="56" y="500">u</text> <text x="56" y="516">i</text> <text x="96" y="516">S</text> <text x="56" y="532">t</text> <text x="96" y="532">l</text> <text x="96" y="548">i</text> <text x="156" y="548">..</text> <text x="476" y="548">weight-Slice-3-CIR</text> <text x="96" y="564">c</text> <text x="472" y="564">shaping-Slice-3-PIR</text> <text x="96" y="580">e</text> <text x="96" y="612">3</text> <text x="392" y="612">/|\</text> <text x="160" y="628">-</text> <text x="176" y="628">-</text> <text x="192" y="628">-</text> <text x="208" y="628">-</text> <text x="224" y="628">-</text> <text x="240" y="628">-</text> <text x="256" y="628">-</text> <text x="272" y="628">-</text> <text x="288" y="628">-</text> <text x="304" y="628">-</text> <text x="320" y="628">-</text> <text x="336" y="628">-</text> <text x="352" y="628">-</text> <text x="368" y="628">-</text> <text x="384" y="628">-</text> <text x="400" y="628">-</text> <text x="416" y="628">-</text> <text x="432" y="628">-</text> <text x="448" y="628">-</text> <text x="464" y="628">-</text> <text x="480" y="628">-</text> <text x="496" y="628">-</text> <text x="512" y="628">-</text> <text x="528" y="628">-</text> <text x="544" y="628">-</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +---------+ QoS output queues | +---|---+ - - - - - - - - - - - - - - - - - - - - - - - - - | | .--|--------------------------. \|/ ---|-----|---|--> 5Q-QoS-A: w-5Q-QoS-A-CIR | | | | S '-----------------------------' | | | l .-----------------------------. | ---|-----|-i-|--> 5Q-QoS-B: w-5Q-QoS-B-CIR | | | | c '-----------------------------' | weight-Slice-1-CIR | | e .-----------------------------. | shaping-Slice-1-PIR ---|-----|---|--> 5Q-QoS-C: w-5Q-QoS-C-CIR | | | | 1 '-----------------------------' | | | .-----------------------------. | ---|-----|---|--> Best Effort (remainder) | | | | '--|--------------------------' /|\ | A +-------+ - - - - - - - - - - - - - - - - - - - - - - - - - | t | .--|--------------------------. \|/ | t | | | | | a | '-----------------------------' | | c | S | | | h | l | | m | i ... | weight-Slice-2-CIR | e | c | | shaping-Slice-2-PIR | n | e .-----------------------------. | | t | | | | | | 2 '-----------------------------' /|\ | C +-------+ - - - - - - - - - - - - - - - - - - - - - - - - - | i | | \|/ | r + .-----------------------------. | | c | | | | | u | '-----------------------------' | | i | S | | | t | l | | | | i ... | weight-Slice-3-CIR | | c | | shaping-Slice-3-PIR | | e .-----------------------------. | | | | | | | | 3 '-----------------------------' /|\ | +---|---+ - - - - - - - - - - - - - - - - - - - - - - - - - +---------+ ]]></artwork> </artset> </figure> </section> </section> </section> <section anchor="transit-resource-control"> <name>Transit Resource Control</name> <t>Transit resource control is much simpler thanEdgeedge resource control in the provider network. As outlined in <xref target="_figure-QoS-5QI-aware"/>, at the provider network edge, 5Q QoS Class marking (represented by DSCP related to 5QI set by mobile network functions in the packets handed off to the TN) is mapped to the TN QoS Class. Based on TN QoS Class, when the packet is encapsulated with an outer header (MPLS or IPv6), the TN QoS Class marking (MPLS TC or IPv6 DSCP in outer header, as depicted in Figures <xref format="counter" target="_figure-15"/> and <xref format="counter" target="_figure-16"/>) is set in the outer header. PHB in provider network transit routers is based exclusively on that TN QoS Class marking, i.e., original 5G QoS Class DSCP is not taken into consideration on transit.</t> <t>Provider network transit resource control does not use any inbound interfacepolicy,policy but only uses an outbound interface policy, which is based on the priority queue combined with a weighted or deficit queuing model, without any shaper. The main purpose of transit resource control is to ensure that during network congestionevents, for exampleevents (for example, events caused by network failuresandor temporaryrerouting,rerouting), premium classes are prioritized, and any drops only occur in traffic that wasde-prioritizeddeprioritized by ingress admission control (see <xreftarget="sec-inbound-edge-resource-control"/>target="sec-inbound-edge-resource-control"/>) or in non-premium (best-effort) classes. Capacity planning and management, as described in <xref target="sec-capacity-planning"/>, ensures that enough capacity is available to fulfill all approved slice requests.</t> </section> </section> <section anchor="transport-plane-mapping-models"> <name>PE Underlay Transport Mapping Models</name> <t>The PE underlay transport (underlay transport, for short) refers to a specific path forwarding behavior between PEs in order to provide packet delivery that is consistent with the corresponding SLOs. This realization step focuses on controlling the paths that will be used for packet delivery between PEs, independent of the underlying network resource partitioning.</t> <t>It is worth noting that TN QoS Classes and underlay transport are each related to different engineering objectives.TheFor example, the TN domain can be operatedwith, e.g.,with 8 TN QoS Classes (representing 8 hardware queues in therouters),routers) and two underlay transports (e.g.,latency optimizeda latency-optimized underlay transport usinglink latencylink-latency metrics for pathcalculation,calculation and an underlay transport followingInterior Gateway Protocol (IGP)IGP metrics). The TN QoS Class determines the per-hop behavior when the packets are transiting through the provider network, while underlay transport determines the paths for packets through the provider network based on the operator's requirements. This path can be optimized or constrained.</t> <t>A network operator can define multiple underlay transports within a single NRP. An underlay transport may be realized in multiple ways such as (but not limited to):</t> <ul spacing="normal"> <li> <t>A mesh of RSVP-TE <xref target="RFC3209"/> or SR-TE <xref target="RFC9256"/> tunnels created with specific optimization criteria and constraints. For example, mesh "A" might represent tunnels optimized for latency, and mesh "B" might represent tunnels optimized for high capacity.</t> </li> <li> <t>A Flex-Algorithm <xref target="RFC9350"/> with a particular metric-type (e.g., latency), or one that only uses links with particular properties (e.g.,MACseca Media Access Control Security (MACsec) link <xreftarget="IEEE802.1AE"/>),target="IEEE802.1AE"/>) or excludes links that are within a particular geography.</t> </li> </ul> <t>These protocols can be controlled, e.g., by tuning the protocol list under the "underlay-transport" data node defined in the L3VPN Network Model (L3NM) <xref target="RFC9182"/> and the L2VPN Network Model (L2NM) <xref target="RFC9291"/>.</t> <!-- [rfced] May we update "2024" as follows in these sentences? Original: However, such an approach is left out of the scope given the current state of the technology (2024). ... it is not necessary (or indeed possible for current SR-TE technology in 2024) to reserve bandwidth at the network layer. Perhaps: However, such an approach is out of the scope given the current state of the technology at the time of writing this document. ... it is not necessary (or indeed possible for current SR-TE technology at the time of writing this document) to reserve bandwidth at the network layer. --> <t>Also, underlay transports may be realized using separate NRPs. However, such an approach is left out of the scope given the current state of the technology (2024).</t> <t>Similar to the QoS mapping models discussed in <xref target="sec-qos-map"/>, for mapping to underlay transports at the ingress PE, both the 5QI-unaware and 5QI-aware models are defined. Essentially, entire slices can be mapped to underlay transports without 5G QoS consideration (5QI-unaware model). For example, flows with different 5G QoS Classes, even from same slice, can be mapped to different underlay transports (5QI-aware model).</t> <t><xref target="_figure-23"/> depicts an example of a simple network with two underlay transports, each using a mesh of TE tunnels with or without Path Computation Element (PCE) <xreftarget="RFC5440"/>,target="RFC5440"/> and with or without per-path bandwidth reservations. <xref target="sec-capacity-planning"/> discusses in detail different bandwidth models that can be deployed in the provider network. However, discussion about how to realize or orchestrate underlay transports is out of scope for this document.</t> <figure anchor="_figure-23"> <name>Example of Underlay Transport Relying on TE Tunnels</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="400" width="496" viewBox="0 0 496 400" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,368" fill="none" stroke="black"/> <path d="M 24,96 L 24,192" fill="none" stroke="black"/> <path d="M 24,224 L 24,336" fill="none" stroke="black"/> <path d="M 112,96 L 112,112" fill="none" stroke="black"/> <path d="M 112,224 L 112,256" fill="none" stroke="black"/> <path d="M 112,304 L 112,336" fill="none" stroke="black"/> <path d="M 136,32 L 136,120" fill="none" stroke="black"/> <path d="M 136,184 L 136,248" fill="none" stroke="black"/> <path d="M 136,312 L 136,368" fill="none" stroke="black"/> <path d="M 160,304 L 160,368" fill="none" stroke="black"/> <path d="M 168,48 L 168,128" fill="none" stroke="black"/> <path d="M 176,176 L 176,248" fill="none" stroke="black"/> <path d="M 176,264 L 176,304" fill="none" stroke="black"/> <path d="M 192,336 L 192,368" fill="none" stroke="black"/> <path d="M 200,64 L 200,96" fill="none" stroke="black"/> <path d="M 200,128 L 200,152" fill="none" stroke="black"/> <path d="M 200,168 L 200,256" fill="none" stroke="black"/> <path d="M 224,160 L 224,256" fill="none" stroke="black"/> <path d="M 224,336 L 224,368" fill="none" stroke="black"/> <path d="M 248,176 L 248,248" fill="none" stroke="black"/> <path d="M 248,264 L 248,272" fill="none" stroke="black"/> <path d="M 256,336 L 256,368" fill="none" stroke="black"/> <path d="M 280,176 L 280,208" fill="none" stroke="black"/> <path d="M 288,336 L 288,368" fill="none" stroke="black"/> <path d="M 304,304 L 304,352" fill="none" stroke="black"/> <path d="M 312,144 L 312,160" fill="none" stroke="black"/> <path d="M 320,288 L 320,336" fill="none" stroke="black"/> <path d="M 360,176 L 360,208" fill="none" stroke="black"/> <path d="M 376,96 L 376,128" fill="none" stroke="black"/> <path d="M 376,272 L 376,336" fill="none" stroke="black"/> <path d="M 432,32 L 432,80" fill="none" stroke="black"/> <path d="M 432,144 L 432,192" fill="none" stroke="black"/> <path d="M 432,240 L 432,288" fill="none" stroke="black"/> <path d="M 432,336 L 432,384" fill="none" stroke="black"/> <path d="M 488,32 L 488,80" fill="none" stroke="black"/> <path d="M 488,144 L 488,192" fill="none" stroke="black"/> <path d="M 488,240 L 488,288" fill="none" stroke="black"/> <path d="M 488,336 L 488,384" fill="none" stroke="black"/> <path d="M 8,32 L 136,32" fill="none" stroke="black"/> <path d="M 432,32 L 488,32" fill="none" stroke="black"/> <path d="M 168,48 L 424,48" fill="none" stroke="black"/> <path d="M 200,64 L 416,64" fill="none" stroke="black"/> <path d="M 432,80 L 488,80" fill="none" stroke="black"/> <path d="M 24,96 L 112,96" fill="none" stroke="black"/> <path d="M 200,96 L 376,96" fill="none" stroke="black"/> <path d="M 120,128 L 168,128" fill="none" stroke="black"/> <path d="M 200,128 L 376,128" fill="none" stroke="black"/> <path d="M 120,144 L 192,144" fill="none" stroke="black"/> <path d="M 208,144 L 312,144" fill="none" stroke="black"/> <path d="M 432,144 L 488,144" fill="none" stroke="black"/> <path d="M 120,160 L 224,160" fill="none" stroke="black"/> <path d="M 312,160 L 424,160" fill="none" stroke="black"/> <path d="M 120,176 L 176,176" fill="none" stroke="black"/> <path d="M 248,176 L 280,176" fill="none" stroke="black"/> <path d="M 360,176 L 416,176" fill="none" stroke="black"/> <path d="M 24,192 L 112,192" fill="none" stroke="black"/> <path d="M 432,192 L 488,192" fill="none" stroke="black"/> <path d="M 280,208 L 360,208" fill="none" stroke="black"/> <path d="M 24,224 L 112,224" fill="none" stroke="black"/> <path d="M 432,240 L 488,240" fill="none" stroke="black"/> <path d="M 120,256 L 200,256" fill="none" stroke="black"/> <path d="M 224,256 L 424,256" fill="none" stroke="black"/> <path d="M 120,272 L 168,272" fill="none" stroke="black"/> <path d="M 184,272 L 248,272" fill="none" stroke="black"/> <path d="M 376,272 L 416,272" fill="none" stroke="black"/> <path d="M 120,288 L 168,288" fill="none" stroke="black"/> <path d="M 184,288 L 320,288" fill="none" stroke="black"/> <path d="M 432,288 L 488,288" fill="none" stroke="black"/> <path d="M 120,304 L 160,304" fill="none" stroke="black"/> <path d="M 176,304 L 304,304" fill="none" stroke="black"/> <path d="M 24,336 L 112,336" fill="none" stroke="black"/> <path d="M 192,336 L 224,336" fill="none" stroke="black"/> <path d="M 256,336 L 288,336" fill="none" stroke="black"/> <path d="M 320,336 L 376,336" fill="none" stroke="black"/> <path d="M 432,336 L 488,336" fill="none" stroke="black"/> <path d="M 304,352 L 424,352" fill="none" stroke="black"/> <path d="M 8,368 L 136,368" fill="none" stroke="black"/> <path d="M 160,368 L 192,368" fill="none" stroke="black"/> <path d="M 224,368 L 256,368" fill="none" stroke="black"/> <path d="M 288,368 L 416,368" fill="none" stroke="black"/> <path d="M 432,384 L 488,384" fill="none" stroke="black"/> <polygon class="arrowhead" points="432,352 420,346.4 420,357.6" fill="black" transform="rotate(0,424,352)"/> <polygon class="arrowhead" points="432,256 420,250.4 420,261.6" fill="black" transform="rotate(0,424,256)"/> <polygon class="arrowhead" points="432,160 420,154.4 420,165.6" fill="black" transform="rotate(0,424,160)"/> <polygon class="arrowhead" points="432,48 420,42.4 420,53.6" fill="black" transform="rotate(0,424,48)"/> <polygon class="arrowhead" points="424,368 412,362.4 412,373.6" fill="black" transform="rotate(0,416,368)"/> <polygon class="arrowhead" points="424,272 412,266.4 412,277.6" fill="black" transform="rotate(0,416,272)"/> <polygon class="arrowhead" points="424,176 412,170.4 412,181.6" fill="black" transform="rotate(0,416,176)"/> <polygon class="arrowhead" points="424,64 412,58.4 412,69.6" fill="black" transform="rotate(0,416,64)"/> <path class="jump" d="M 248,264 C 254,264 254,248 248,248" fill="none" stroke="black"/> <path class="jump" d="M 200,168 C 206,168 206,152 200,152" fill="none" stroke="black"/> <path class="jump" d="M 176,264 C 182,264 182,248 176,248" fill="none" stroke="black"/> <circle cx="112" cy="256" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="112" cy="272" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="112" cy="288" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="112" cy="304" r="6" class="opendot" fill="white" stroke="black"/> <g class="text"> <text x="56" y="52">Ingress</text> <text x="100" y="52">PE</text> <text x="460" y="52">PE-A</text> <text x="424" y="68">></text> <text x="112" y="132">x</text> <text x="60" y="148">Underlay</text> <text x="112" y="148">x</text> <text x="64" y="164">Transport</text> <text x="112" y="164">x</text> <text x="460" y="164">PE-B</text> <text x="64" y="180">A</text> <text x="112" y="180">x</text> <text x="424" y="180">></text> <text x="460" y="260">PE-C</text> <text x="60" y="276">Underlay</text> <text x="424" y="276">></text> <text x="64" y="292">Transport</text> <text x="56" y="308">B</text> <text x="460" y="356">PE-D</text> <text x="424" y="372">></text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +---------------+ +------+ | Ingress PE | +------------------------------->| PE-A | | | | +-------------------------->>| | | | | | +------+ | +----------+ | | +---------------------+ | | | | | | | | x------+ +---------------------+ | |Underlay x----------|-------------+ +------+ | |Transport x----------)--+ +------------->| PE-B | | | A x-------+ | | +---+ +------>>| | | +----------+ | | | | | | | +------+ | | | | | | +---------+ | +----------+ | | | | | | | | | | | | | +------+ | | o-------)--+ +--)--------------------->| PE-C | | |Underlay o-------|--------+ +---->>| | | |Transport o-------|-----------------+ | +------+ | | B o-----+ +---------------+ | | | | | | | | | | | +----------+ | | +---+ +---+ | +------+ +------+ | | | | | | | +-------------->| PE-D | +---------------+ +---+ +---+ +--------------->>| | +------+ ]]></artwork> </artset> </figure> <t>For illustration purposes, <xref target="_figure-23"/> shows only single tunnels per underlay transport for an (ingress PE, egress PE) pair. However, there might be multiple tunnels within a single underlay transport between any pair of PEs.</t> <section anchor="qi-unaware-model"><name>5QI-unaware<name>5QI-Unaware Model</name> <t>As discussed in <xref target="sec-5QI-unaware"/>, in the 5QI-unaware model, the provider network doesn't take into account 5G QoS during execution of per-hop behavior. The entire slice is mapped to a single TN QoSClass, thereforeClass; therefore, the entire slice is subject to the same per-hop behavior. Similarly, in the 5QI-unaware PE underlay transport mapping model, the entire slice is mapped to a single underlay transport, as depicted in <xref target="_figure-24"/>.</t> <figure anchor="_figure-24"><name>Network<name>Mapping of Network Slice toPEsUnderlay TransportMapping (5QI-unaware(5QI-Unaware Model)</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="608" width="368" viewBox="0 0 368 608" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,48" fill="none" stroke="black"/> <path d="M 24,96 L 24,160" fill="none" stroke="black"/> <path d="M 24,192 L 24,256" fill="none" stroke="black"/> <path d="M 24,288 L 24,352" fill="none" stroke="black"/> <path d="M 24,384 L 24,448" fill="none" stroke="black"/> <path d="M 24,480 L 24,544" fill="none" stroke="black"/> <path d="M 48,112 L 48,144" fill="none" stroke="black"/> <path d="M 48,208 L 48,240" fill="none" stroke="black"/> <path d="M 48,304 L 48,336" fill="none" stroke="black"/> <path d="M 48,400 L 48,432" fill="none" stroke="black"/> <path d="M 48,496 L 48,528" fill="none" stroke="black"/> <path d="M 136,112 L 136,144" fill="none" stroke="black"/> <path d="M 136,208 L 136,240" fill="none" stroke="black"/> <path d="M 136,304 L 136,336" fill="none" stroke="black"/> <path d="M 136,400 L 136,432" fill="none" stroke="black"/> <path d="M 136,496 L 136,528" fill="none" stroke="black"/> <path d="M 152,80 L 152,120" fill="none" stroke="black"/> <path d="M 152,176 L 152,216" fill="none" stroke="black"/> <path d="M 152,272 L 152,312" fill="none" stroke="black"/> <path d="M 152,368 L 152,408" fill="none" stroke="black"/> <path d="M 152,464 L 152,504" fill="none" stroke="black"/> <path d="M 200,224 L 200,416" fill="none" stroke="black"/> <path d="M 232,128 L 232,376" fill="none" stroke="black"/> <path d="M 232,392 L 232,512" fill="none" stroke="black"/> <path d="M 264,176 L 264,208" fill="none" stroke="black"/> <path d="M 264,240 L 264,272" fill="none" stroke="black"/> <path d="M 264,336 L 264,368" fill="none" stroke="black"/> <path d="M 264,400 L 264,432" fill="none" stroke="black"/> <path d="M 344,176 L 344,272" fill="none" stroke="black"/> <path d="M 344,336 L 344,432" fill="none" stroke="black"/> <path d="M 360,32 L 360,576" fill="none" stroke="black"/> <path d="M 8,32 L 360,32" fill="none" stroke="black"/> <path d="M 40,80 L 152,80" fill="none" stroke="black"/> <path d="M 48,112 L 136,112" fill="none" stroke="black"/> <path d="M 136,128 L 232,128" fill="none" stroke="black"/> <path d="M 48,144 L 136,144" fill="none" stroke="black"/> <path d="M 24,160 L 136,160" fill="none" stroke="black"/> <path d="M 40,176 L 152,176" fill="none" stroke="black"/> <path d="M 264,176 L 344,176" fill="none" stroke="black"/> <path d="M 48,208 L 136,208" fill="none" stroke="black"/> <path d="M 136,224 L 200,224" fill="none" stroke="black"/> <path d="M 232,224 L 264,224" fill="none" stroke="black"/> <path d="M 48,240 L 136,240" fill="none" stroke="black"/> <path d="M 24,256 L 136,256" fill="none" stroke="black"/> <path d="M 40,272 L 152,272" fill="none" stroke="black"/> <path d="M 264,272 L 344,272" fill="none" stroke="black"/> <path d="M 48,304 L 136,304" fill="none" stroke="black"/> <path d="M 136,320 L 200,320" fill="none" stroke="black"/> <path d="M 48,336 L 136,336" fill="none" stroke="black"/> <path d="M 264,336 L 344,336" fill="none" stroke="black"/> <path d="M 24,352 L 136,352" fill="none" stroke="black"/> <path d="M 40,368 L 152,368" fill="none" stroke="black"/> <path d="M 200,384 L 264,384" fill="none" stroke="black"/> <path d="M 48,400 L 136,400" fill="none" stroke="black"/> <path d="M 136,416 L 200,416" fill="none" stroke="black"/> <path d="M 48,432 L 136,432" fill="none" stroke="black"/> <path d="M 264,432 L 344,432" fill="none" stroke="black"/> <path d="M 24,448 L 136,448" fill="none" stroke="black"/> <path d="M 40,464 L 152,464" fill="none" stroke="black"/> <path d="M 48,496 L 136,496" fill="none" stroke="black"/> <path d="M 136,512 L 232,512" fill="none" stroke="black"/> <path d="M 48,528 L 136,528" fill="none" stroke="black"/> <path d="M 24,544 L 136,544" fill="none" stroke="black"/> <path d="M 8,576 L 360,576" fill="none" stroke="black"/> <path d="M 40,80 C 31.16936,80 24,87.16936 24,96" fill="none" stroke="black"/> <path d="M 136,160 C 144.83064,160 152,152.83064 152,144" fill="none" stroke="black"/> <path d="M 40,176 C 31.16936,176 24,183.16936 24,192" fill="none" stroke="black"/> <path d="M 136,256 C 144.83064,256 152,248.83064 152,240" fill="none" stroke="black"/> <path d="M 40,272 C 31.16936,272 24,279.16936 24,288" fill="none" stroke="black"/> <path d="M 136,352 C 144.83064,352 152,344.83064 152,336" fill="none" stroke="black"/> <path d="M 40,368 C 31.16936,368 24,375.16936 24,384" fill="none" stroke="black"/> <path d="M 136,448 C 144.83064,448 152,440.83064 152,432" fill="none" stroke="black"/> <path d="M 40,464 C 31.16936,464 24,471.16936 24,480" fill="none" stroke="black"/> <path d="M 136,544 C 144.83064,544 152,536.83064 152,528" fill="none" stroke="black"/> <polygon class="arrowhead" points="272,384 260,378.4 260,389.6" fill="black" transform="rotate(0,264,384)"/> <polygon class="arrowhead" points="272,224 260,218.4 260,229.6" fill="black" transform="rotate(0,264,224)"/> <path class="jump" d="M 232,392 C 238,392 238,376 232,376" fill="none" stroke="black"/> <g class="text"> <text x="20" y="52">..</text> <text x="44" y="52">..</text> <text x="68" y="52">..</text> <text x="92" y="52">..</text> <text x="116" y="52">..</text> <text x="140" y="52">..</text> <text x="160" y="52">.</text> <text x="8" y="68">:</text> <text x="84" y="68">AC</text> <text x="168" y="68">:</text> <text x="228" y="68">PE</text> <text x="8" y="84">:</text> <text x="168" y="84">:</text> <text x="8" y="100">:</text> <text x="56" y="100">SDP</text> <text x="168" y="100">:</text> <text x="8" y="116">:</text> <text x="168" y="116">:</text> <text x="8" y="132">:</text> <text x="100" y="132">NS</text> <text x="120" y="132">1</text> <text x="8" y="148">:</text> <text x="168" y="148">:</text> <text x="8" y="164">:</text> <text x="168" y="164">:</text> <text x="8" y="180">:</text> <text x="168" y="180">:</text> <text x="8" y="196">:</text> <text x="56" y="196">SDP</text> <text x="168" y="196">:</text> <text x="8" y="212">:</text> <text x="168" y="212">:</text> <text x="300" y="212">Underlay</text> <text x="8" y="228">:</text> <text x="100" y="228">NS</text> <text x="120" y="228">2</text> <text x="304" y="228">Transport</text> <text x="8" y="244">:</text> <text x="168" y="244">:</text> <text x="304" y="244">A</text> <text x="8" y="260">:</text> <text x="168" y="260">:</text> <text x="8" y="276">:</text> <text x="168" y="276">:</text> <text x="8" y="292">:</text> <text x="56" y="292">SDP</text> <text x="168" y="292">:</text> <text x="8" y="308">:</text> <text x="168" y="308">:</text> <text x="8" y="324">:</text> <text x="100" y="324">NS</text> <text x="120" y="324">3</text> <text x="8" y="340">:</text> <text x="168" y="340">:</text> <text x="8" y="356">:</text> <text x="168" y="356">:</text> <text x="8" y="372">:</text> <text x="168" y="372">:</text> <text x="300" y="372">Underlay</text> <text x="8" y="388">:</text> <text x="56" y="388">SDP</text> <text x="168" y="388">:</text> <text x="304" y="388">Transport</text> <text x="8" y="404">:</text> <text x="168" y="404">:</text> <text x="304" y="404">B</text> <text x="8" y="420">:</text> <text x="100" y="420">NS</text> <text x="120" y="420">4</text> <text x="8" y="436">:</text> <text x="168" y="436">:</text> <text x="8" y="452">:</text> <text x="168" y="452">:</text> <text x="8" y="468">:</text> <text x="168" y="468">:</text> <text x="8" y="484">:</text> <text x="56" y="484">SDP</text> <text x="168" y="484">:</text> <text x="8" y="500">:</text> <text x="168" y="500">:</text> <text x="8" y="516">:</text> <text x="100" y="516">NS</text> <text x="120" y="516">5</text> <text x="8" y="532">:</text> <text x="168" y="532">:</text> <text x="8" y="548">:</text> <text x="168" y="548">:</text> <text x="16" y="564">'..</text> <text x="44" y="564">..</text> <text x="68" y="564">..</text> <text x="92" y="564">..</text> <text x="116" y="564">..</text> <text x="140" y="564">..</text> <text x="164" y="564">.'</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +-------------------------------------------+ |.. .. .. .. .. .. . | : AC : PE | : .--------------. : | : | SDP | : | : | +----------+ | : | : | | NS 1 +-----------+ | : | +----------+ | : | | : '--------------' : | | : .--------------. : | +---------+ | : | SDP | : | | | | : | +----------+ | : | |Underlay | | : | | NS 2 +-------+ +--->Transport| | : | +----------+ | : | | | A | | : '--------------' : | | | | | : .--------------. : | | +---------+ | : | SDP | : | | | : | +----------+ | : | | | : | | NS 3 +-------+ | | : | +----------+ | : | | +---------+ | : '--------------' : | | | | | : .--------------. : | | |Underlay | | : | SDP | : +---)--->Transport| | : | +----------+ | : | | | B | | : | | NS 4 +-------+ | | | | : | +----------+ | : | +---------+ | : '--------------' : | | : .--------------. : | | : | SDP | : | | : | +----------+ | : | | : | | NS 5 +-----------+ | : | +----------+ | : | : '--------------' : | '.. .. .. .. .. .. .' | +-------------------------------------------+ ]]></artwork> </artset> </figure> </section> <section anchor="qi-aware-model-1"><name>5QI-aware<name>5QI-Aware Model</name> <t>In the 5QI-aware model, the traffic can be mapped to underlay transports at the granularity of 5G QoS Class. Given that the potential number of underlay transports is limited, packets from multiple 5G QoS Classes with similar characteristics are mapped to a common underlay transport, as depicted in <xref target="_figure-25"/>.</t> <figure anchor="_figure-25"><name>Network<name>Mapping of Network Slice to Underlay TransportMapping (5QI-aware(5QI-Aware Model)</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="608" width="400" viewBox="0 0 400 608" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 24,32 L 24,48" fill="none" stroke="black"/> <path d="M 40,96 L 40,304" fill="none" stroke="black"/> <path d="M 40,336 L 40,544" fill="none" stroke="black"/> <path d="M 168,80 L 168,120" fill="none" stroke="black"/> <path d="M 168,136 L 168,168" fill="none" stroke="black"/> <path d="M 168,184 L 168,216" fill="none" stroke="black"/> <path d="M 168,232 L 168,264" fill="none" stroke="black"/> <path d="M 168,320 L 168,344" fill="none" stroke="black"/> <path d="M 168,360 L 168,392" fill="none" stroke="black"/> <path d="M 168,408 L 168,440" fill="none" stroke="black"/> <path d="M 168,456 L 168,488" fill="none" stroke="black"/> <path d="M 168,504 L 168,528" fill="none" stroke="black"/> <path d="M 216,128 L 216,216" fill="none" stroke="black"/> <path d="M 216,232 L 216,264" fill="none" stroke="black"/> <path d="M 216,280 L 216,400" fill="none" stroke="black"/> <path d="M 256,224 L 256,232" fill="none" stroke="black"/> <path d="M 256,248 L 256,496" fill="none" stroke="black"/> <path d="M 296,192 L 296,224" fill="none" stroke="black"/> <path d="M 296,256 L 296,288" fill="none" stroke="black"/> <path d="M 296,352 L 296,384" fill="none" stroke="black"/> <path d="M 296,416 L 296,448" fill="none" stroke="black"/> <path d="M 376,192 L 376,288" fill="none" stroke="black"/> <path d="M 376,352 L 376,448" fill="none" stroke="black"/> <path d="M 392,32 L 392,576" fill="none" stroke="black"/> <path d="M 24,32 L 392,32" fill="none" stroke="black"/> <path d="M 56,80 L 168,80" fill="none" stroke="black"/> <path d="M 72,112 L 136,112" fill="none" stroke="black"/> <path d="M 152,128 L 216,128" fill="none" stroke="black"/> <path d="M 72,144 L 136,144" fill="none" stroke="black"/> <path d="M 72,160 L 136,160" fill="none" stroke="black"/> <path d="M 152,176 L 216,176" fill="none" stroke="black"/> <path d="M 72,192 L 136,192" fill="none" stroke="black"/> <path d="M 296,192 L 376,192" fill="none" stroke="black"/> <path d="M 72,208 L 136,208" fill="none" stroke="black"/> <path d="M 152,224 L 256,224" fill="none" stroke="black"/> <path d="M 72,240 L 136,240" fill="none" stroke="black"/> <path d="M 216,240 L 296,240" fill="none" stroke="black"/> <path d="M 72,256 L 136,256" fill="none" stroke="black"/> <path d="M 152,272 L 256,272" fill="none" stroke="black"/> <path d="M 72,288 L 136,288" fill="none" stroke="black"/> <path d="M 296,288 L 376,288" fill="none" stroke="black"/> <path d="M 40,304 L 152,304" fill="none" stroke="black"/> <path d="M 56,320 L 168,320" fill="none" stroke="black"/> <path d="M 72,336 L 136,336" fill="none" stroke="black"/> <path d="M 152,352 L 216,352" fill="none" stroke="black"/> <path d="M 296,352 L 376,352" fill="none" stroke="black"/> <path d="M 72,368 L 136,368" fill="none" stroke="black"/> <path d="M 72,384 L 136,384" fill="none" stroke="black"/> <path d="M 152,400 L 216,400" fill="none" stroke="black"/> <path d="M 256,400 L 296,400" fill="none" stroke="black"/> <path d="M 72,416 L 136,416" fill="none" stroke="black"/> <path d="M 72,432 L 136,432" fill="none" stroke="black"/> <path d="M 152,448 L 256,448" fill="none" stroke="black"/> <path d="M 296,448 L 376,448" fill="none" stroke="black"/> <path d="M 72,464 L 136,464" fill="none" stroke="black"/> <path d="M 72,480 L 136,480" fill="none" stroke="black"/> <path d="M 152,496 L 256,496" fill="none" stroke="black"/> <path d="M 72,512 L 136,512" fill="none" stroke="black"/> <path d="M 40,544 L 152,544" fill="none" stroke="black"/> <path d="M 24,576 L 392,576" fill="none" stroke="black"/> <path d="M 56,80 C 47.16936,80 40,87.16936 40,96" fill="none" stroke="black"/> <path d="M 72,112 C 63.16936,112 56,119.16936 56,128" fill="none" stroke="black"/> <path d="M 136,112 C 144.83064,112 152,119.16936 152,128" fill="none" stroke="black"/> <path d="M 72,144 C 63.16936,144 56,136.83064 56,128" fill="none" stroke="black"/> <path d="M 136,144 C 144.83064,144 152,136.83064 152,128" fill="none" stroke="black"/> <path d="M 72,160 C 63.16936,160 56,167.16936 56,176" fill="none" stroke="black"/> <path d="M 136,160 C 144.83064,160 152,167.16936 152,176" fill="none" stroke="black"/> <path d="M 72,192 C 63.16936,192 56,184.83064 56,176" fill="none" stroke="black"/> <path d="M 136,192 C 144.83064,192 152,184.83064 152,176" fill="none" stroke="black"/> <path d="M 72,208 C 63.16936,208 56,215.16936 56,224" fill="none" stroke="black"/> <path d="M 136,208 C 144.83064,208 152,215.16936 152,224" fill="none" stroke="black"/> <path d="M 72,240 C 63.16936,240 56,232.83064 56,224" fill="none" stroke="black"/> <path d="M 136,240 C 144.83064,240 152,232.83064 152,224" fill="none" stroke="black"/> <path d="M 72,256 C 63.16936,256 56,263.16936 56,272" fill="none" stroke="black"/> <path d="M 136,256 C 144.83064,256 152,263.16936 152,272" fill="none" stroke="black"/> <path d="M 72,288 C 63.16936,288 56,280.83064 56,272" fill="none" stroke="black"/> <path d="M 136,288 C 144.83064,288 152,280.83064 152,272" fill="none" stroke="black"/> <path d="M 152,304 C 160.83064,304 168,296.83064 168,288" fill="none" stroke="black"/> <path d="M 56,320 C 47.16936,320 40,327.16936 40,336" fill="none" stroke="black"/> <path d="M 72,336 C 63.16936,336 56,343.16936 56,352" fill="none" stroke="black"/> <path d="M 136,336 C 144.83064,336 152,343.16936 152,352" fill="none" stroke="black"/> <path d="M 72,368 C 63.16936,368 56,360.83064 56,352" fill="none" stroke="black"/> <path d="M 136,368 C 144.83064,368 152,360.83064 152,352" fill="none" stroke="black"/> <path d="M 72,384 C 63.16936,384 56,391.16936 56,400" fill="none" stroke="black"/> <path d="M 136,384 C 144.83064,384 152,391.16936 152,400" fill="none" stroke="black"/> <path d="M 72,416 C 63.16936,416 56,408.83064 56,400" fill="none" stroke="black"/> <path d="M 136,416 C 144.83064,416 152,408.83064 152,400" fill="none" stroke="black"/> <path d="M 72,432 C 63.16936,432 56,439.16936 56,448" fill="none" stroke="black"/> <path d="M 136,432 C 144.83064,432 152,439.16936 152,448" fill="none" stroke="black"/> <path d="M 72,464 C 63.16936,464 56,456.83064 56,448" fill="none" stroke="black"/> <path d="M 136,464 C 144.83064,464 152,456.83064 152,448" fill="none" stroke="black"/> <path d="M 72,480 C 63.16936,480 56,487.16936 56,496" fill="none" stroke="black"/> <path d="M 136,480 C 144.83064,480 152,487.16936 152,496" fill="none" stroke="black"/> <path d="M 72,512 C 63.16936,512 56,504.83064 56,496" fill="none" stroke="black"/> <path d="M 136,512 C 144.83064,512 152,504.83064 152,496" fill="none" stroke="black"/> <path d="M 152,544 C 160.83064,544 168,536.83064 168,528" fill="none" stroke="black"/> <polygon class="arrowhead" points="304,400 292,394.4 292,405.6" fill="black" transform="rotate(0,296,400)"/> <polygon class="arrowhead" points="304,240 292,234.4 292,245.6" fill="black" transform="rotate(0,296,240)"/> <path class="jump" d="M 256,248 C 262,248 262,232 256,232" fill="none" stroke="black"/> <path class="jump" d="M 216,280 C 222,280 222,264 216,264" fill="none" stroke="black"/> <path class="jump" d="M 216,232 C 222,232 222,216 216,216" fill="none" stroke="black"/> <g class="text"> <text x="36" y="52">..</text> <text x="60" y="52">..</text> <text x="84" y="52">..</text> <text x="108" y="52">..</text> <text x="132" y="52">..</text> <text x="156" y="52">..</text> <text x="176" y="52">.</text> <text x="24" y="68">:</text> <text x="100" y="68">AC</text> <text x="184" y="68">:</text> <text x="244" y="68">PE</text> <text x="24" y="84">:</text> <text x="184" y="84">:</text> <text x="8" y="100">R</text> <text x="24" y="100">:</text> <text x="72" y="100">SDP</text> <text x="184" y="100">:</text> <text x="8" y="116">F</text> <text x="24" y="116">:</text> <text x="184" y="116">:</text> <text x="8" y="132">C</text> <text x="24" y="132">:</text> <text x="76" y="132">5G</text> <text x="104" y="132">QoS</text> <text x="128" y="132">A</text> <text x="8" y="148">9</text> <text x="24" y="148">:</text> <text x="184" y="148">:</text> <text x="8" y="164">5</text> <text x="24" y="164">:</text> <text x="184" y="164">:</text> <text x="8" y="180">4</text> <text x="24" y="180">:</text> <text x="76" y="180">5G</text> <text x="104" y="180">QoS</text> <text x="128" y="180">B</text> <text x="8" y="196">3</text> <text x="24" y="196">:</text> <text x="184" y="196">:</text> <text x="24" y="212">:</text> <text x="184" y="212">:</text> <text x="8" y="228">N</text> <text x="24" y="228">:</text> <text x="76" y="228">5G</text> <text x="104" y="228">QoS</text> <text x="128" y="228">C</text> <text x="332" y="228">Underlay</text> <text x="8" y="244">S</text> <text x="24" y="244">:</text> <text x="184" y="244">:</text> <text x="336" y="244">Transport</text> <text x="24" y="260">:</text> <text x="184" y="260">:</text> <text x="336" y="260">A</text> <text x="8" y="276">1</text> <text x="24" y="276">:</text> <text x="76" y="276">5G</text> <text x="104" y="276">QoS</text> <text x="128" y="276">D</text> <text x="24" y="292">:</text> <text x="184" y="292">:</text> <text x="24" y="308">:</text> <text x="184" y="308">:</text> <text x="8" y="324">R</text> <text x="24" y="324">:</text> <text x="184" y="324">:</text> <text x="8" y="340">F</text> <text x="24" y="340">:</text> <text x="184" y="340">:</text> <text x="8" y="356">C</text> <text x="24" y="356">:</text> <text x="76" y="356">5G</text> <text x="104" y="356">QoS</text> <text x="128" y="356">A</text> <text x="8" y="372">9</text> <text x="24" y="372">:</text> <text x="184" y="372">:</text> <text x="8" y="388">5</text> <text x="24" y="388">:</text> <text x="184" y="388">:</text> <text x="332" y="388">Underlay</text> <text x="8" y="404">4</text> <text x="24" y="404">:</text> <text x="76" y="404">5G</text> <text x="104" y="404">QoS</text> <text x="128" y="404">E</text> <text x="336" y="404">Transport</text> <text x="8" y="420">3</text> <text x="24" y="420">:</text> <text x="184" y="420">:</text> <text x="336" y="420">B</text> <text x="24" y="436">:</text> <text x="184" y="436">:</text> <text x="8" y="452">N</text> <text x="24" y="452">:</text> <text x="76" y="452">5G</text> <text x="104" y="452">QoS</text> <text x="128" y="452">F</text> <text x="8" y="468">S</text> <text x="24" y="468">:</text> <text x="184" y="468">:</text> <text x="24" y="484">:</text> <text x="184" y="484">:</text> <text x="8" y="500">2</text> <text x="24" y="500">:</text> <text x="76" y="500">5G</text> <text x="104" y="500">QoS</text> <text x="128" y="500">G</text> <text x="24" y="516">:</text> <text x="184" y="516">:</text> <text x="24" y="532">:</text> <text x="72" y="532">SDP</text> <text x="184" y="532">:</text> <text x="24" y="548">:</text> <text x="184" y="548">:</text> <text x="32" y="564">'..</text> <text x="60" y="564">..</text> <text x="84" y="564">..</text> <text x="108" y="564">..</text> <text x="132" y="564">..</text> <text x="156" y="564">..</text> <text x="176" y="564">'</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +---------------------------------------------+ |.. .. .. .. .. .. . | : AC : PE | : .--------------. : | R : | SDP | : | F : | .---------. | : | C : | | 5G QoS A +-------+ | 9 : | '---------' | : | | 5 : | .---------. | : | | 4 : | | 5G QoS B +-------+ | 3 : | '---------' | : | +---------+ | : | .---------. | : | | | | N : | | 5G QoS C +-------)----+ |Underlay | | S : | '---------' | : +----)---->Transport| | : | .---------. | : | | | A | | 1 : | | 5G QoS D +-------)----+ | | | : | '---------' | : | | +---------+ | : '--------------' : | | | R : .--------------. : | | | F : | .---------. | : | | | C : | | 5G QoS A +-------+ | +---------+ | 9 : | '---------' | : | | | | | 5 : | .---------. | : | | |Underlay | | 4 : | | 5G QoS E +-------+ +---->Transport| | 3 : | '---------' | : | | B | | : | .---------. | : | | | | N : | | 5G QoS F +------------+ +---------+ | S : | '---------' | : | | : | .---------. | : | | 2 : | | 5G QoS G +------------+ | : | '---------' | : | : | SDP | : | : '--------------' : | '.. .. .. .. .. .. ' | +---------------------------------------------+ ]]></artwork> </artset> </figure> </section> </section> <section anchor="sec-capacity-planning"> <name>Capacity Planning/Management</name> <section anchor="bandwidth-requirements"> <name>Bandwidth Requirements</name> <t>This section describes the information conveyed by the 5G NSO to the NSC with respect to slice bandwidth requirements.</t> <t><xref target="_figure-multi-DC"/> shows three DCs that contain instances of network functions. Also shown are PEs that have links to the DCs. The PEs belong to the provider network. Other details of the provider network, such as P-routers and transitlinkslinks, are not shown.AlsoIn addition, details of the DC infrastructure in customer sites, such as switches and routers, are not shown.</t> <t>The 5G NSO is aware of the existence of the network functions and their locations. However, it is not aware of the details of the provider network. The NSC has the opposite view--- it is aware of the provider network infrastructure and the links between the PEs and the DCs, but it is not aware of the individual network functions at customer sites.</t> <figure anchor="_figure-multi-DC"><name>An Example<name>Example of Multi-DC Architecture</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="464" width="576" viewBox="0 0 576 464" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,32 L 8,208" fill="none" stroke="black"/> <path d="M 24,64 L 24,96" fill="none" stroke="black"/> <path d="M 48,112 L 48,144" fill="none" stroke="black"/> <path d="M 64,160 L 64,192" fill="none" stroke="black"/> <path d="M 80,64 L 80,96" fill="none" stroke="black"/> <path d="M 104,112 L 104,144" fill="none" stroke="black"/> <path d="M 120,160 L 120,192" fill="none" stroke="black"/> <path d="M 176,32 L 176,208" fill="none" stroke="black"/> <path d="M 200,64 L 200,96" fill="none" stroke="black"/> <path d="M 200,160 L 200,192" fill="none" stroke="black"/> <path d="M 208,32 L 208,56" fill="none" stroke="black"/> <path d="M 208,104 L 208,152" fill="none" stroke="black"/> <path d="M 208,200 L 208,416" fill="none" stroke="black"/> <path d="M 240,64 L 240,96" fill="none" stroke="black"/> <path d="M 240,160 L 240,192" fill="none" stroke="black"/> <path d="M 320,64 L 320,96" fill="none" stroke="black"/> <path d="M 320,160 L 320,192" fill="none" stroke="black"/> <path d="M 320,256 L 320,288" fill="none" stroke="black"/> <path d="M 320,352 L 320,384" fill="none" stroke="black"/> <path d="M 352,32 L 352,56" fill="none" stroke="black"/> <path d="M 352,104 L 352,152" fill="none" stroke="black"/> <path d="M 352,200 L 352,248" fill="none" stroke="black"/> <path d="M 352,296 L 352,344" fill="none" stroke="black"/> <path d="M 352,392 L 352,416" fill="none" stroke="black"/> <path d="M 360,64 L 360,96" fill="none" stroke="black"/> <path d="M 360,160 L 360,192" fill="none" stroke="black"/> <path d="M 360,256 L 360,288" fill="none" stroke="black"/> <path d="M 360,352 L 360,384" fill="none" stroke="black"/> <path d="M 384,32 L 384,208" fill="none" stroke="black"/> <path d="M 384,240 L 384,416" fill="none" stroke="black"/> <path d="M 416,64 L 416,96" fill="none" stroke="black"/> <path d="M 416,256 L 416,288" fill="none" stroke="black"/> <path d="M 440,112 L 440,144" fill="none" stroke="black"/> <path d="M 448,304 L 448,336" fill="none" stroke="black"/> <path d="M 472,64 L 472,96" fill="none" stroke="black"/> <path d="M 472,256 L 472,288" fill="none" stroke="black"/> <path d="M 480,160 L 480,192" fill="none" stroke="black"/> <path d="M 480,352 L 480,384" fill="none" stroke="black"/> <path d="M 496,112 L 496,144" fill="none" stroke="black"/> <path d="M 504,304 L 504,336" fill="none" stroke="black"/> <path d="M 536,160 L 536,192" fill="none" stroke="black"/> <path d="M 536,352 L 536,384" fill="none" stroke="black"/> <path d="M 552,32 L 552,208" fill="none" stroke="black"/> <path d="M 552,240 L 552,416" fill="none" stroke="black"/> <path d="M 8,32 L 72,32" fill="none" stroke="black"/> <path d="M 120,32 L 176,32" fill="none" stroke="black"/> <path d="M 208,32 L 352,32" fill="none" stroke="black"/> <path d="M 384,32 L 448,32" fill="none" stroke="black"/> <path d="M 496,32 L 552,32" fill="none" stroke="black"/> <path d="M 24,64 L 80,64" fill="none" stroke="black"/> <path d="M 200,64 L 240,64" fill="none" stroke="black"/> <path d="M 320,64 L 360,64" fill="none" stroke="black"/> <path d="M 416,64 L 472,64" fill="none" stroke="black"/> <path d="M 176,80 L 192,80" fill="none" stroke="black"/> <path d="M 368,80 L 384,80" fill="none" stroke="black"/> <path d="M 24,96 L 80,96" fill="none" stroke="black"/> <path d="M 200,96 L 240,96" fill="none" stroke="black"/> <path d="M 320,96 L 360,96" fill="none" stroke="black"/> <path d="M 416,96 L 472,96" fill="none" stroke="black"/> <path d="M 48,112 L 104,112" fill="none" stroke="black"/> <path d="M 440,112 L 496,112" fill="none" stroke="black"/> <path d="M 48,144 L 104,144" fill="none" stroke="black"/> <path d="M 440,144 L 496,144" fill="none" stroke="black"/> <path d="M 64,160 L 120,160" fill="none" stroke="black"/> <path d="M 200,160 L 240,160" fill="none" stroke="black"/> <path d="M 320,160 L 360,160" fill="none" stroke="black"/> <path d="M 480,160 L 536,160" fill="none" stroke="black"/> <path d="M 176,176 L 192,176" fill="none" stroke="black"/> <path d="M 368,176 L 384,176" fill="none" stroke="black"/> <path d="M 64,192 L 120,192" fill="none" stroke="black"/> <path d="M 200,192 L 240,192" fill="none" stroke="black"/> <path d="M 320,192 L 360,192" fill="none" stroke="black"/> <path d="M 480,192 L 536,192" fill="none" stroke="black"/> <path d="M 8,208 L 176,208" fill="none" stroke="black"/> <path d="M 384,208 L 552,208" fill="none" stroke="black"/> <path d="M 384,240 L 448,240" fill="none" stroke="black"/> <path d="M 488,240 L 552,240" fill="none" stroke="black"/> <path d="M 320,256 L 360,256" fill="none" stroke="black"/> <path d="M 416,256 L 472,256" fill="none" stroke="black"/> <path d="M 368,272 L 384,272" fill="none" stroke="black"/> <path d="M 320,288 L 360,288" fill="none" stroke="black"/> <path d="M 416,288 L 472,288" fill="none" stroke="black"/> <path d="M 448,304 L 504,304" fill="none" stroke="black"/> <path d="M 448,336 L 504,336" fill="none" stroke="black"/> <path d="M 320,352 L 360,352" fill="none" stroke="black"/> <path d="M 480,352 L 536,352" fill="none" stroke="black"/> <path d="M 368,368 L 384,368" fill="none" stroke="black"/> <path d="M 320,384 L 360,384" fill="none" stroke="black"/> <path d="M 480,384 L 536,384" fill="none" stroke="black"/> <path d="M 208,416 L 352,416" fill="none" stroke="black"/> <path d="M 384,416 L 552,416" fill="none" stroke="black"/> <circle cx="24" cy="448" r="6" class="closeddot" fill="black"/> <circle cx="200" cy="80" r="6" class="closeddot" fill="black"/> <circle cx="200" cy="176" r="6" class="closeddot" fill="black"/> <circle cx="360" cy="80" r="6" class="closeddot" fill="black"/> <circle cx="360" cy="176" r="6" class="closeddot" fill="black"/> <circle cx="360" cy="272" r="6" class="closeddot" fill="black"/> <circle cx="360" cy="368" r="6" class="closeddot" fill="black"/> <g class="text"> <text x="92" y="36">DC</text> <text x="112" y="36">1</text> <text x="468" y="36">DC</text> <text x="488" y="36">2</text> <text x="52" y="84">NF1A</text> <text x="220" y="84">PE1A</text> <text x="340" y="84">PE2A</text> <text x="444" y="84">NF2A</text> <text x="76" y="132">NF1B</text> <text x="468" y="132">NF2B</text> <text x="92" y="180">NF1C</text> <text x="220" y="180">PE1B</text> <text x="340" y="180">PE2B</text> <text x="508" y="180">NF2C</text> <text x="276" y="212">Provider</text> <text x="280" y="244">Network</text> <text x="460" y="244">DC</text> <text x="480" y="244">3</text> <text x="340" y="276">PE3A</text> <text x="444" y="276">NF3A</text> <text x="476" y="324">NF3B</text> <text x="340" y="372">PE3B</text> <text x="508" y="372">NF3C</text> <text x="52" y="452">SDP,</text> <text x="92" y="452">with</text> <text x="164" y="452">fine-grained</text> <text x="232" y="452">QoS</text> <text x="292" y="452">(dedicated</text> <text x="376" y="452">resources</text> <text x="432" y="452">per</text> <text x="464" y="452">RFC</text> <text x="500" y="452">9543</text> <text x="536" y="452">NS)</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ +-------- DC 1-------+ +-----------------+ +-------- DC 2-------+ | | | | | | | +------+ | +----+ +----+ | +------+ | | | NF1A | +--*PE1A| |PE2A*--+ | NF2A | | | +------+ | +----+ +----+ | +------+ | | +------+ | | | | +------+ | | | NF1B | | | | | | NF2B | | | +------+ | | | | +------+ | | +------+ | +----+ +----+ | +------+ | | | NF1C | +--*PE1B| |PE2B*--+ | NF2C | | | +------+ | +----+ +----+ | +------+ | +--------------------+ | Provider | +--------------------+ | | | Network | +--------DC 3--------+ | +----+ | +------+ | | |PE3A*--+ | NF3A | | | +----+ | +------+ | | | | +------+ | | | | | NF3B | | | | | +------+ | | +----+ | +------+ | | |PE3B*--+ | NF3C | | | +----+ | +------+ | | | | | +-----------------+ +--------------------+ * SDP, with fine-grained QoS (dedicated resources per RFC 9543 NS) ]]></artwork> </artset> </figure> <t>Let us consider 5G slice "X" that uses some of the network functions in the three DCs. If this slice has latency requirements, the 5G NSO will have taken those into account when deciding which NF instances in which DC are to be invoked for this slice. As a result of such a placement decision, the three DCs shown are involved in 5G slice "X", rather than other DCs. For its decision-making, the 5G NSO needs information from the NSC about the observed latency between DCs. Preferably, the NSC would present the topology in an abstracted form, consisting of point-to-point abstracted links between pairs of DCs and associated latency and, optionally, delay variation andlink losslink-loss values. It would be valuable to have a mechanism for the 5G NSO to inform the NSC which DC-pairs are of interest for thesemetrics -metrics; there may beof orderthousands of DCs, but the 5G NSO will only be interested in these metrics for a small fraction of all the possible DC-pairs,i.e.i.e., those in the same region of the provider network. The mechanism for conveying the information is out of scope for this document.</t> <t><xref target="_table-x"/> shows the matrix of bandwidth demands for 5G slice "X". Within the slice, multiple NF instances might be sending traffic from DCi to DCj. However, the 5G NSO sums the associated demands into one value. For example, "NF1A" and "NF1B" in "DC1" might be sending traffic to multiple NFs in "DC2", but this is expressed as one value in the traffic matrix: the total bandwidth required for 5G slice "X" from "DC1" to "DC2" (8 units). Each row in the right-most column in the traffic matrix shows the total amount of traffic going from a given DC into the transport network, regardless of the destination DC. Note that this number can be less than the sum of DC-to-DC demands in the same row, on the basis that not all the NFs are likely to be sending at their maximum rate simultaneously. For example, the total traffic from "DC1" for slice "X" is 11 units, which is less than the sum of the DC-to-DC demands in the same row (13 units). Note, as described in <xref target="sec-qos-map"/>, a slice may have per-QoS class bandwidthrequirements,requirements and may have CIR and PIR limits. This is not included in the example, but the same principles apply in such cases.</t> <table anchor="_table-x"> <name>Inter-DC Traffic Demand Matrix (Slice X)</name> <thead> <tr> <th align="left">From/To</th> <th align="left">DC 1</th> <th align="left">DC 2</th> <th align="left">DC 3</th> <th align="center">Total from DC</th> </tr> </thead> <tbody> <tr> <td align="left">DC 1</td> <td align="left">n/a</td> <td align="left">8</td> <td align="left">5</td> <td align="center">11.0</td> </tr> <tr> <td align="left">DC 2</td> <td align="left">1</td> <td align="left">n/a</td> <td align="left">2</td> <td align="center">2.5</td> </tr> <tr> <td align="left">DC 3</td> <td align="left">4</td> <td align="left">7</td> <td align="left">n/a</td> <td align="center">10.0</td> </tr> </tbody> </table><t><xref<!-- [rfced] We updated "[I-D.ietf-teas-ietf-network-slice-nbi-yang]" in these sentences to "the YANG data model defined in [NSSM]" for clarity. Let us know any concerns. Original: [I-D.ietf-teas-ietf-network-slice-nbi-yang] can be used to convey all of the information in the traffic matrix to an NSC. ... ...could be used instead of [I-D.ietf-teas-ietf-network-slice-nbi-yang], as they support conveying the bandwidth information in the right-most column of the traffic matrix. ... The 5G NSO can use [I-D.ietf-teas-ietf-network-slice-nbi-yang] to request low- latency transport for a given slice if required. ... For example, [I-D.ietf-teas-ietf-network-slice-nbi-yang] exposes a set of statistics per SDP, connectivity construct, and connection group. Updated: The YANG data model defined in [NSSM] can be used to convey all of the information in the traffic matrix to an NSC. ... ...could be used instead of the YANG data model defined in [NSSM], as they support conveying the bandwidth information in the right-most column of the traffic matrix. ... The 5G NSO can use the YANG data model defined in [NSSM] to request low-latency transport for a given slice if required. ... For example, the YANG data model defined in [NSSM] exposes a set of statistics per SDP, connectivity construct, and connection group. --> <t>The YANG data model defined in <xref target="I-D.ietf-teas-ietf-network-slice-nbi-yang"/> can be used to convey all of the information in the traffic matrix to an NSC. The NSC applies policers corresponding to the last column in the traffic matrix to the appropriate PE routers, in order to enforce the bandwidth contract. For example, it applies a policer of 11 units to PE1A and PE1B that face DC1, as this is the total bandwidth that DC1 sends into the provider network corresponding toSlice X.slice "X". Also, the controller may apply shapers in the direction from the TN to theDC,DC ifotherwisethere is the possibility of a link in the DC being oversubscribed. Note that a peer NF endpoint of an AC can be identified using'peer-sap-id'"peer-sap-id" as defined in <xref target="RFC9408"/>.</t> <t>Depending on the bandwidth model used in the provider network (<xref target="sec-bw"/>), the other values in the matrix, i.e., the DC-to-DC demands, may not be directly applied to the provider network. Even so, the information may be useful to the NSC for capacity planning and failure simulation purposes.If, onOn the other hand, if the DC-to-DC demand information is not used by the NSC, the IETF YANGData Modeldata models for L3VPNService Deliveryservice delivery <xref target="RFC8299"/> orthe IETF YANG Data Model forL2VPNService Deliveryservice delivery <xref target="RFC8466"/> could be used instead of the YANG data model defined in <xref target="I-D.ietf-teas-ietf-network-slice-nbi-yang"/>, as they support conveying the bandwidth information in the right-most column of the traffic matrix.</t> <t>The provider network may be implemented in such a way that it has various types of paths, forexampleexample, low-latency traffic might be mapped onto a different transport pathtofrom other traffic (forexampleexample, a particular Flex-Algorithm, a particular set of TE paths, or a specific queue <xref target="RFC9330"/>), as discussed in <xref target="sec-qos-map"/>. The 5G NSO can use the YANG data model defined in <xref target="I-D.ietf-teas-ietf-network-slice-nbi-yang"/> to request low-latency transport for a given slice if required. However, the YANG data models in <xref target="RFC8299"/> or <xref target="RFC8466"/> do not support requesting a particular transport-type, e.g., low-latency. One option is to augment these models to convey this information. This can be achieved by reusing the'underlay- transport'"underlay-transport" construct defined in <xref target="RFC9182"/> and <xref target="RFC9291"/>.</t> </section> <section anchor="sec-bw"> <name>Bandwidth Models</name> <t>This section describes three bandwidth management schemes that could be employed in the provider network. Many variations are possible, but each example describes the salient points of the corresponding scheme. Schemes 2 and 3 use TE; other variations on TE are possible as described in <xref target="RFC9522"/>.</t> <section anchor="scheme-1-shortest-path-forwarding-spf"> <name>Scheme 1: Shortest Path Forwarding (SPF)</name> <t>Shortest path forwarding is used according to the IGP metric. Given that some slices are likely to have latency SLOs, the IGP metric on each link can be set to be in proportion to the latency of the link. In this way, all traffic follows the minimum latency path between endpoints.</t> <t>In Scheme 1, although the operator provides bandwidth guarantees to the slice customers, there is no explicit end-to-end underpinning of the bandwidth SLO, in the form of bandwidth reservations across the provider network. Rather, the expected performance is achieved via capacity planning, based on traffic growth trends and anticipated future demands, in order to ensure that network links are notover- subscribed.over-subscribed. This scheme is analogous to that used in many existing business VPN deployments, in that bandwidth guarantees are provided to the customers but are not explicitly underpinned end to end across the provider network.</t> <t>A variation on the scheme is that Flex-Algorithm <xref target="RFC9350"/> is used. For example, one Flex-Algorithm could use latency-basedmetricsmetrics, and another Flex-Algorithm could use the IGP metric. There would be a many-to-one mapping of Network Slices to Flex-Algorithms.</t> <t>While Scheme 1 is technically feasible, it is vulnerable to unexpected changes in traffic patterns and/or network element failures resulting in congestion. This is because, unlike Schemes 2 and33, which employ TE, traffic cannot be diverted from the shortest path.</t> </section> <section anchor="scheme-2-te-paths-with-fixed-bandwidth-reservations"> <name>Scheme 2: TE Paths with Fixed Bandwidth Reservations</name> <t>Scheme 2 uses RSVP-TE <xref target="RFC3209"/> or SR-TEpaths<xref target="RFC9256"/> paths with fixed bandwidth reservations. By "fixed", we mean a value that stays constant over time, unless the 5G NSO communicates a change in slice bandwidth requirements, due to the creation or modification of a slice. Note that the "reservations" may be maintained by the transportcontroller -controller; it is not necessary (or indeed possible for current SR-TE technology in 2024) to reserve bandwidth at the network layer. The bandwidth requirement acts as a constraint whenever the controller (re)computes a path. There could be a single mesh of paths between endpoints that carry all of the traffic types, or there could be a small handful of meshes, forexampleexample, one mesh for low-latency traffic that follows the minimum latency path and another mesh for the other traffic that follows the minimum IGP metric path, as described in <xref target="sec-qos-map"/>. There would be a many-to-one mapping of slices to paths.</t> <t>The bandwidth requirement from DCi to DCj is the sum of the DCi-DCj demands of the individual slices. For example, if only slices "X" and "Y" are present, then the bandwidth requirement from "DC1" to "DC2" is 12 units (8 units for slice "X" (<xref target="_table-x"/>) and 4 units for slice "Y" (<xref target="_table-y"/>)). When the 5G NSO requests a new slice, the NSC, increments the bandwidth requirement according to the requirements of the new slice. For example, in <xref target="_figure-multi-DC"/>, suppose a new slice is instantiated that needs 0.8 Gbps from "DC1" to "DC2". The transport controller would increase its notion of the bandwidth requirement from "DC1" to "DC2" from 12 Gbps to 12.8 Gbps to accommodate the additional expected traffic.</t> <table anchor="_table-y"> <name>Inter-DC Traffic Demand Matrix (Slice Y)</name> <thead> <tr> <th align="left">From/To</th> <th align="left">DC 1</th> <th align="left">DC 2</th> <th align="left">DC 3</th> <th align="center">Total from DC</th> </tr> </thead> <tbody> <tr> <td align="left">DC 1</td> <td align="left">n/a</td> <td align="left">4</td> <td align="left">2.5</td> <td align="center">6.0</td> </tr> <tr> <td align="left">DC 2</td> <td align="left">0.5</td> <td align="left">n/a</td> <td align="left">0.8</td> <td align="center">1.0</td> </tr> <tr> <td align="left">DC 3</td> <td align="left">2.6</td> <td align="left">3</td> <td align="left">n/a</td> <td align="center">5.1</td> </tr> </tbody> </table> <t>In the example, each DC has two PEs facing it for reasons of resilience. The NSC needs to determine how to map the "DC1" to "DC2" bandwidth requirement to bandwidth reservations of TE LSPs from "DC1" to "DC2". For example, if the routing configuration is arranged such that in the absence of any network failure, traffic from "DC1" to "DC2" always enters "PE1A" and goes to "PE2A", the controller reserves 12.8 Gbps of bandwidth on the path from "PE1A" to "PE2A".If, onOn the other hand, if the routing configuration is arranged such that in the absence of any network failure, traffic from "DC1" to "DC2" always enters "PE1A" and is load-balanced across "PE2A" and "PE2B", the controller reserves 6.4 Gbps of bandwidth on the path from "PE1A" to "PE2A" and 6.4 Gbps of bandwidth on the path from "PE1A" to "PE2B". It might be tricky for the NSC to be aware of all conditions that change the way traffic lands on the variousPEs,PEs and therefore know that it needs to change bandwidth reservations of paths accordingly. For example, there might be an internal failure within "DC1" that causes traffic from "DC1" to land on"PE1B","PE1B" rather than "PE1A". The NSC may not be aware of the failure and therefore may not know that it now needs to apply bandwidth reservations to paths from "PE1B" to "PE2A"/and "PE2B".</t> </section> <section anchor="scheme-3-te-paths-without-bandwidth-reservation"> <name>Scheme 3: TE Paths without Bandwidth Reservation</name> <t>Like Scheme 2, Scheme 3 uses RSVP-TE or SR-TE paths. There could be a single mesh of paths between endpoints that carry all of the traffic types, or there could be a small handful of meshes, forexampleexample, one mesh for low-latency traffic that follows the minimum latency path and another mesh for the other traffic that follows the minimum IGP metric path, as described in <xref target="sec-qos-map"/>. There would be a many-to-one mapping of slices to paths.</t> <!-- [rfced] Please confirm that "the paths of one or more paths" is correct here. Original: In this approach, when the actual traffic volume in the data plane on given link exceeds a threshold, the controller, knowing how much actual data plane traffic is currently traveling along each RSVP or SR-TE path, can tune the paths of one or more paths using the link such that they avoid that link. This approach is similar to that described in Section 4.3.1 of [RFC9522]. Perhaps: In this approach, when the actual traffic volume in the data plane on given link exceeds a threshold, the controller, knowing how much actual data plane traffic is currently traveling along each RSVP or SR-TE path, can tune one or more paths using the link such that they avoid that link. This approach is similar to that described in Section 4.3.1 of [RFC9522]. --> <t>The difference between Scheme 2 and Scheme 3 is that Scheme 3 does not have fixed bandwidth reservations for the paths. Instead, actual measureddata-planedata plane traffic volumes are used to influence the placement of TE paths. One way of achieving this is to use distributed RSVP-TE with auto-bandwidth. Alternatively, the NSC can use telemetry-driven automatic congestion avoidance. In this approach, when the actual traffic volume in the data plane on a given link exceeds a threshold, the controller, knowing how much actual data plane traffic is currently traveling along each RSVP or SR-TE path, can tune the paths of one or more paths using the link such that they avoid that link. This approach is similar to that described in <xref section="4.3.1" sectionFormat="of" target="RFC9522"/>.</t> <t>It would be undesirable to move a path that has latency as its cost function, rather than another type of path, in order to ease the congestion, as the altered path will typically have a higher latency. This can be avoided by designing the algorithms described in the previous paragraph such that they avoid moving minimum-latency paths unless there is no alternative.</t> </section> </section> </section> <section anchor="network-slicing-oam"> <name>Network Slicing OAM</name> <t>The deployment and maintenance of slices within a network imply that a set of OAM functions(<xref target="RFC6291"/>)<xref target="RFC6291"/> need to be deployed by the providers,e.g.:</t>for example:</t> <ul spacing="normal"> <li> <t>Providers should be able to execute OAM tasks on a per Network Slice basis. These tasks can cover the "full" slice within a domain or a portion of that slice (for troubleshooting purposes, for example). </t> <t> For example, per-slice OAM tasks can consist of (but not limited to): </t> <ul spacing="normal"> <li> <t>tracing resources that are bound to a given Network Slice,</t> </li> <li> <t>tracing resources that are invoked when forwarding a given flow bound to a given Network Slice,</t> </li> <li> <t>assessing whether flow isolation characteristics are in conformance with the Network Slice Service requirements, or</t> </li> <li> <t>assessing the compliance of the allocated Network Slice resources againstflow/flow and customer service requirements.</t> </li> </ul> <t> <xref target="RFC7276"/> provides an overview of available OAM tools. These technology-specific tools can be reused in the context of network slicing. Providers that deploy network slicing capabilities should be able to select whatever OAM technology or specific feature that would address their needs.</t> </li> <li> <t>Providers may want to enable differentiated failuredetectdetection and repair features for a subset of network slices. For example, a given Network Slice may require fastdetectdetection and repair mechanisms, while others may not be engineered with such means. The provider can use techniques such as those described in <xref target="RFC5286"/>, <xref target="RFC5714"/>,orand <xref target="RFC8355"/>.</t> </li> <li> <t>Providers may deploy means to dynamically discover the set of Network Slices that are enabled within its network. Such dynamic discovery capability facilitates the detection of any mismatch between the view maintained by the control/management plane and the actual network configuration. When mismatches are detected, corrective actions should be undertaken accordingly. For example, a provider may rely upon the L3NM <xref target="RFC9182"/> or the L2NM <xref target="RFC9291"/> to maintain the full set of L3VPN/L2VPNs that are used to deliver Network Slice Services. The correlation between an LxVPN instance and a Network Slice Service is maintained using the "parent-service-id" attribute (<xref section="7.3" sectionFormat="of" target="RFC9182"/>).</t> </li> <li><t>Means<!-- [rfced] FYI - We updated this sentence as follows. Let us know any concerns. Original: For example, [RFC9375] can be used to report links' one-way delay, one-way delay variation, etc. Perhaps: For example, the YANG data model in [RFC9375] can be used to report the one-way delay and one-way delay variation of links. --> <t>The means to report a set of network performance metrics to assess whether the agreed slice service objectives are honored. These means are used for SLO monitoring and violationdetectdetection purposes. For example, the YANG data model in <xref target="RFC9375"/> can be used to reportlinks'the one-waydelay,delay and one-way delayvariation, etc.variation of links. Both conventional active/passive measurement methods <xref target="RFC7799"/> and more recent telemetry methods (e.g., YANG Push <xref target="RFC8641"/>) can be used.</t> </li> <li><t>Means<!-- [rfced] The top-level bullets in the list in Section 8 are all complete sentences except for the items below. How may we revise these to create complete sentences? Original: * Means to report a set of network performance metrics to assess whether the agreed slice service objectives are honored. ... * Means to report and expose observed performance metrics and other OAM state to customer. Perhaps: * Providers should provide the means to report a set of network performance metrics to assess whether the agreed slice service objectives are honored. ... * Providers should have the means to report and expose observed performance metrics and other OAM state to customer. --> <t>The means to report and expose observed performance metrics and other OAM state to customer. For example, the YANG data model defined in <xref target="I-D.ietf-teas-ietf-network-slice-nbi-yang"/> exposes a set of statistics per SDP, connectivity construct, and connection group.</t> </li> </ul> </section> <section anchor="sec-sca-impli"> <name>Scalability Implications</name><t>The<!-- [rfced] The last two sentences mention 1-to-1 mapping and N-to-1 mapping, but these are not listed in Section 3.5 (which only lists 1 to N, M to 1, and M to N). Please review and let us know if any updates are needed. (The first two sentences are included for context.) Original: The mapping between 5G slice to TN slices (see Section 3.5) is a design choice of service operators that may be a function of, e.g., the number of instantiated slices, requested services, or local engineering capabilities and guidelines. However, operators should carefully consider means to ease slice migration strategies. For example, a provider may initially adopt a 1-to-1 mapping if it has to instantiate just a few Network Slices and accommodate the need of only a few customers. That provider may decide to move to an N-to-1 mapping for aggregation/scalability purposes if sustained increased slice demand is observed. --> <t>The mapping of 5G slices to TN slices (see <xref target="sec-mapping"/>) is a design choice of service operators that may be a function of, e.g., the number of instantiated slices, requested services, or local engineering capabilities and guidelines. However, operators should carefully consider means to ease slice migration strategies. For example, a provider may initially adopt a 1-to-1 mapping if it has to instantiate just a few Network Slices and accommodate the need of only a few customers. That provider may decide to move to an N-to-1 mapping for aggregation/scalability purposes if sustained increased slice demand is observed.</t> <t>Putting in place adequate automation means to realize Network Slices (including the adjustment of the mapping of Slice Services to NetworkSlices mapping)Slices) would ease slice migration operations.</t> <t>The realization model described inthethis document inherits the scalability properties of the underlying L2VPN and L3VPN technologies (<xref target="sec-over-rea-model"/>). Readers may refer, for example, to <xref section="13" sectionFormat="of" target="RFC4365"/> or <xref section="1.2.5" sectionFormat="of" target="RFC6624"/> for a scalability assessment of some of these technologies. Providers may adjust the mapping model to better handle local scalability constraints.</t> </section> <section anchor="iana-considerations"> <name>IANA Considerations</name> <t>This documentdoes not make anyhas no IANArequest.</t>actions.</t> </section> <section anchor="security-considerations"> <name>Security Considerations</name> <t><xref section="10" sectionFormat="of" target="RFC9543"/> discusses generic security considerations that are applicable to network slicing, with a focus on the following considerations:</t><dl><dl newline="true"> <dt>Conformance to security constraints:</dt> <dd> <t>Specific security requests, such as not routing traffic through a particular geographical region can be met by mapping the traffic to an underlay transport (<xref target="transport-plane-mapping-models"/>) that avoids that region.</t> </dd> <dt>NSC authentication:</dt> <dd> <t>Per <xref target="RFC9543"/>,this is aboutunderlay networks need to be protected against attacks from an adversary NSC as this could destabilize overall network operations. The interaction between an NSC and theunderlyunderlay network is used to pass service provisioning requests following a set of YANG modules that are designed to be accessed via YANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. These YANG-based management protocols(1)have to use (1) a secure transport layer (e.g., SSH <xref target="RFC4252"/>, TLS <xref target="RFC8446"/>, and QUIC <xref target="RFC9000"/>) and (2)have to usemutual authentication.</t></dd> <dt/> <dd><t>The NETCONF access control model <xref target="RFC8341"/> provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.</t></dd> <dt/> <dd><t>Readers may refer to documents that describe NSCrealizationrealization, such as <xref target="I-D.ietf-teas-ns-controller-models"/>.</t> </dd> <dt>Specific isolation criteria:</dt> <dd> <t>Adequate admission control policies, forexampleexample, policers as described in <xref target="sec-inbound-edge-resource-control"/>, should be configured in the edge of the provider network to control access to specific slice resources. This prevents the possibility of one slice consuming resources at the expense of other slices. Likewise, access to classification and mapping tables have to be controlled to prevent misbehaviors (an unauthorized entity may modify the table to bind traffic to a random slice, redirect the traffic, etc.). Network devices have to check that a required access privilege is provided before granting access to specific data or performing specific actions.</t> </dd> <dt>Data Confidentiality and Integrity of an IETF Network Slice:</dt> <dd> <t>As described in <xref section="5.1.2.1" sectionFormat="of" target="RFC9543"/>, the customer might request a Service Level Expectation (SLE) that mandates encryption.</t></dd> <dt/> <dd><t>This can be achieved, e.g., by mapping the traffic to an underlay transport (<xref target="transport-plane-mapping-models"/>) that uses only MACsec-encrypted links.</t> </dd> </dl> <t>In order to avoid the need for a mapping table to associate source/destination IP addresses andslices'the specificS-NSSAIs,S-NSSAIs of slices, <xref target="sec-ip-hof"/> describes an approach where some or all S-NSSAI bits are embedded in an IPv6 address using an algorithm approach. An attacker from within the transport network who has access to the mapping configuration may infer the slices to whichbelongapacket.packet belongs. It may also alter thesebitsbits, which may lead to steering the packet via a distinct networkslice,slice and thusleadto service disruption. Note that such an attacker from within the transport network may inflict more damage (e.g., randomly drop packets).</t> <t>Security considerations specific to each of the technologies and protocols listed in the document are discussed in the specification documents of each of these protocols. In particular, readers should refer to the "Security Framework for Provider-Provisioned Virtual Private Networks (PPVPNs)" <xref target="RFC4111"/>, the "Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)" (<xref section="6" sectionFormat="of" target="RFC4365"/>), and the "Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs)" <xref target="RFC4381"/> for a comprehensive discussion about security considerations related to VPN technologies (including authentication and encryption between PEs, use of IPsec tunnels that terminate within the customer sites to protect user data, prevention of illegitimate traffic from entering a VPN instance, etc.). Also, readers may refer to <xref section="9" sectionFormat="of" target="RFC9522"/> for a discussion about security considerations related to TE mechanisms.</t> </section> </middle> <back> <displayreference target="I-D.cbs-teas-5qi-to-dscp-mapping" to="MAPPING"/> <displayreference target="I-D.ietf-teas-5g-network-slice-application" to="NS-APP"/> <displayreference target="I-D.ietf-teas-ietf-network-slice-nbi-yang" to="NSSM"/> <displayreference target="I-D.ietf-teas-ns-controller-models" to="NSC-MODEL"/> <displayreference target="I-D.ietf-teas-ns-ip-mpls" to="NS-IP-MPLS"/> <references anchor="sec-combined-references"> <name>References</name> <references anchor="sec-normative-references"> <name>Normative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9543.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4364.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7608.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> </references> <references anchor="sec-informative-references"> <name>Informative References</name> <!-- [rfced] FYI, we updated the title for this reference to match the title at the URL. Please let us know if you prefer otherwise. Original: [Book-5G] Peterson, L., Sunay, O., and B. Davie, "5G Mobile Networks: A Systems Approach", 2022, <https://5g.systemsapproach.org/>. Current: [Book-5G] Peterson, L., Sunay, O., and B. Davie, "Private 5G: A Systems Approach", 2023, <https://5g.systemsapproach.org/>. --> <referenceanchor="RFC9543">anchor="Book-5G" target="https://5g.systemsapproach.org/"> <front><title>A Framework for Network Slices in Networks Built from IETF Technologies</title> <author fullname="A. Farrel" initials="A." role="editor" surname="Farrel"/> <author fullname="J. Drake" initials="J." role="editor" surname="Drake"/> <author fullname="R. Rokui" initials="R." surname="Rokui"/> <author fullname="S. Homma" initials="S." surname="Homma"/><title>Private 5G: A Systems Approach</title> <authorfullname="K. Makhijani" initials="K." surname="Makhijani"/>fullname="Larry Peterson"> <organization/> </author> <authorfullname="L. Contreras" initials="L." surname="Contreras"/>fullname="Oguz Sunay"> <organization/> </author> <authorfullname="J. Tantsura" initials="J." surname="Tantsura"/>fullname="Bruce Davie"> <organization/> </author> <datemonth="March" year="2024"/> <abstract> <t>This document describes network slicing in the context of networks built from IETF technologies. It defines the term "IETF Network Slice"year="2023"/> </front> </reference> <!-- [rfced] Would it be helpful todescribe this typepoint to specific versions ofnetwork slice[TS-23.501] andestablishes the general principles of network slicing in the IETF context.</t> <t>The document discusses the general framework[TS-28.530]? The original date forrequestingboth references was 2024, but there are multiple versions across multiple releases from that year, andoperating IETF Network Slices,both also have new 2025 versions. Note that specific sections and figures in [TS-28.530] are mentioned in thecharacteristics of an IETF Network Slice,text. We are not sure if these will be stable across versions. Current: [TS-23.501] 3GPP, "System architecture for thenecessary system components5G System (5GS)", 3GPP TS 23.501, <https://portal.3gpp.org/desktopmodules/Specifications/ SpecificationDetails.aspx?specificationId=3144>. ... [TS-28.530] 3GPP, "Management andinterfaces,orchestration; Concepts, use cases and requirements", 3GPP TS 28.530, <https://portal.3gpp.org/desktopmodules/Specifications/ SpecificationDetails.aspx?specificationId=3273>. --> <reference anchor="TS-23.501" target="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144"> <front> <title>System architecture for themapping of abstract requests to more specific technologies. The document also discusses related considerations with monitoring5G System (5GS)</title> <author> <organization abbrev="3GPP">3rd Generation Partnership Project</organization> </author> </front> <seriesInfo name="3GPP TS" value="23.501"/> </reference> <reference anchor="TS-28.530" target="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3273"> <front> <title>Management andsecurity.</t> <t>This document also provides definitions of related terms to enable consistent usage in other IETF documents that describe or use aspects of IETF Network Slices.</t> </abstract> </front> <seriesInfo name="RFC" value="9543"/> <seriesInfo name="DOI" value="10.17487/RFC9543"/> </reference> <reference anchor="RFC4364"> <front> <title>BGP/MPLS IP Virtual Private Networks (VPNs)</title> <author fullname="E. Rosen" initials="E." surname="Rosen"/> <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/> <date month="February" year="2006"/> <abstract> <t>This document describes a method by which a Service Provider mayorchestration; Concepts, usean IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm,cases andCE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]</t> </abstract>requirements</title> <author> <organization>3GPP</organization> </author> </front> <!-- 28.530 --> <seriesInfoname="RFC" value="4364"/> <seriesInfo name="DOI" value="10.17487/RFC4364"/>name="3GPP TS" value="28.530"/> </reference><reference anchor="RFC7608"> <front> <title>IPv6 Prefix Length Recommendation<!-- [rfced] The current URL forForwarding</title> <author fullname="M. Boucadair" initials="M." surname="Boucadair"/> <author fullname="A. Petrescu" initials="A." surname="Petrescu"/> <author fullname="F. Baker" initials="F." surname="Baker"/> <date month="July" year="2015"/> <abstract> <t>IPv6 prefix length, as in IPv4, isthis reference (https://www.o-ran.org/specifications) goes to aparameter conveyed and used in IPv6 routing and forwarding processes in accordance with the Classless Inter-domain Routing (CIDR) architecture. The length of an IPv6 prefix may be any number from zeropage titled "O-RAN Specifications". We were able to128, although subnets using stateless address autoconfiguration (SLAAC) for address allocation conventionally usefind a/64 prefix. Hardware and software implementations of routing and forwarding should therefore impose no rules on prefix length, but implement longest-match-first on prefixeslist ofany valid length.</t> </abstract> </front> <seriesInfo name="BCP" value="198"/> <seriesInfo name="RFC" value="7608"/> <seriesInfo name="DOI" value="10.17487/RFC7608"/> </reference> <reference anchor="RFC8341"> <front> <title>Network Configuration Access Control Model</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <date month="March" year="2018"/> <abstract> <t>The standardizationO-RAN specifications here: https://specifications.o-ran.org/specifications. We were unable to find Version 04.00 ofnetwork configuration interfaces for use withtheNetwork Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environmentO-RAN specification. It appears thatpromotes human usability and multi-vendor interoperability. There is a need for standard mechanismsthis page only has the most recent version - Version 08.00 - published in June 2024. May we update this reference accordingly torestrict NETCONF or RESTCONF protocol access for particular userspoint toa preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.</t> <t>This document obsoletes RFC 6536.</t> </abstract> </front> <seriesInfo name="STD" value="91"/> <seriesInfo name="RFC" value="8341"/> <seriesInfo name="DOI" value="10.17487/RFC8341"/> </reference> </references> <references anchor="sec-informative-references"> <name>Informative References</name> <reference anchor="Book-5G" target="https://5g.systemsapproach.org/"> <front> <title>5G Mobile Networks: A Systems Approach</title> <author fullname="Larry Peterson"> <organization/> </author> <author fullname="Oguz Sunay"> <organization/> </author> <author fullname="Bruce Davie"> <organization/> </author> <date year="2022"/> </front> </reference> <reference anchor="TS-23.501" target="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144"> <front> <title>TS 23.501: System architecture for the 5G System (5GS)</title> <author> <organization>3GPP</organization> </author> <date year="2024"/> </front> </reference> <reference anchor="TS-28.530" target="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3273"> <front> <title>TS 28.530: Management and orchestration; Concepts, use cases and requirements)</title> <author> <organization>3GPP</organization> </author> <date year="2024"/> </front> </reference> <reference anchor="O-RAN.WG9.XPSAAS" target="https://www.o-ran.org/specifications"> <front> <title>O-RAN.WG9.XPSAAS:this version? Original: [O-RAN.WG9.XPSAAS] O-RAN Alliance, "O-RAN.WG9.XPSAAS: O-RAN WG9 Xhaul Packet Switched Architectures and Solutions Version04.00</title>04.00", March 2023, <https://www.o-ran.org/specifications>. Perhaps: [O-RAN.WG9.XPSAAS] O-RAN Alliance, "Xhaul Packet Switched Architectures and Solutions", O-RAN.WG9.XPSAAS, Version 08.00, June 2024, <https://specifications.o-ran.org/specifications>. --> <reference anchor="O-RAN.WG9.XPSAAS" target="https://specifications.o-ran.org/specifications"> <front> <title>Xhaul Packet Switched Architectures and Solutions</title> <author> <organization>O-RAN Alliance</organization> </author> <date year="2023" month="March"/> </front> <refcontent>O-RAN.WG9.XPSAAS, Version 04.00</refcontent> </reference> <reference anchor="NG.113" target="https://www.gsma.com/newsroom/wp-content/uploads//NG.113-v4.0.pdf"> <front> <title>NG.113: 5GS RoamingGuidelines Version 4.0</title>Guidelines</title> <author> <organization>GSMA</organization> </author> <date year="2021" month="May"/> </front> <refcontent>Version 4.0</refcontent> </reference> <reference anchor="IEEE802.1AE" target="https://1.ieee802.org/security/802-1ae/"> <front> <title>802.1AE: MAC Security (MACsec)</title> <author> <organization>IEEE</organization> </author><date>n.d.</date></front> </reference> <reference anchor="ECPRI" target="https://www.cpri.info/downloads/eCPRI_v_2.0_2019_05_10c.pdf"> <front> <title>Common Public Radio Interface: eCPRI Interface Specification</title> <author> <organization>Common Public Radio Interface</organization> </author><date>n.d.</date></front> </reference> <!-- [I-D.ietf-teas-5g-network-slice-application] draft-ietf-teas-5g-network-slice-application-05 IESG State: I-D Exists as of 10/3/25 Long Way --> <referenceanchor="I-D.ietf-teas-5g-network-slice-application">anchor="I-D.ietf-teas-5g-network-slice-application" target="https://datatracker.ietf.org/doc/html/draft-ietf-teas-5g-network-slice-application-05"> <front> <title>IETF Network Slice Application in 3GPP 5G End-to-End Network Slice</title> <authorfullname="Xuesong Geng"initials="X."surname="Geng">surname="Geng" fullname="Xuesong Geng"> <organization>Huawei Technologies</organization> </author> <author initials="L. M." surname="Contreras" fullname="Luis M. Contreras"initials="L. M." surname="Contreras">role="editor"> <organization>Telefonica</organization> </author> <authorfullname="Reza Rokui"initials="R."surname="Rokui">surname="Rokui" fullname="Reza Rokui"> <organization>Ciena</organization> </author> <authorfullname="Jie Dong"initials="J."surname="Dong">surname="Dong" fullname="Jie Dong"> <organization>Huawei Technologies</organization> </author> <authorfullname="Ivan Bykov"initials="I."surname="Bykov">surname="Bykov" fullname="Ivan Bykov"> <organization>Ribbon Communications</organization> </author> <dateday="3" month="March" year="2025"/> <abstract> <t> Network Slicing is one of the core features of 5G defined in 3GPP, which provides different network service as independent logical networks. To provide 5G network slices services, an end-to-end network slice has to span three network segments: Radio Access Network (RAN), Mobile Core Network (CN) and Transport Network (TN). This document describes the application of the IETF network slice framework in providing 5G end-to-end network slices, including network slice mapping in the management, control and data planes. </t> </abstract>month="July" day="7" year="2025" /> </front> <seriesInfo name="Internet-Draft"value="draft-ietf-teas-5g-network-slice-application-04"/>value="draft-ietf-teas-5g-network-slice-application-05" /> </reference> <!-- [I-D.ietf-teas-ns-ip-mpls] draft-ietf-teas-ns-ip-mpls-05 IESG State: I-D Exists as of 06/23/25 Long Way --> <referenceanchor="I-D.ietf-teas-ns-ip-mpls">anchor="I-D.ietf-teas-ns-ip-mpls" target="https://datatracker.ietf.org/doc/html/draft-ietf-teas-ns-ip-mpls-05"> <front> <title>Realizing Network Slices in IP/MPLS Networks</title> <author fullname="Tarek Saad" initials="T." surname="Saad"> <organization>Cisco Systems Inc.</organization> </author> <author fullname="Vishnu Pavan Beeram"initials="V. P."initials="V." surname="Beeram"> <organization>Juniper Networks</organization> </author> <author fullname="Jie Dong" initials="J." surname="Dong"> <organization>Huawei Technologies</organization> </author> <author fullname="Joel M. Halpern"initials="J. M."initials="J." surname="Halpern"> <organization>Ericsson</organization> </author> <author fullname="Shaofu Peng" initials="S." surname="Peng"> <organization>ZTE Corporation</organization> </author> <date day="2" month="March" 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 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-05"/> </reference><reference anchor="RFC4664"> <front> <title>Framework for Layer 2 Virtual Private Networks (L2VPNs)</title> <author fullname="L. Andersson" initials="L." role="editor" surname="Andersson"/> <author fullname="E. Rosen" initials="E." role="editor" surname="Rosen"/> <date month="September" year="2006"/> <abstract> <t>This document provides a framework for Layer 2 Provider Provisioned Virtual Private Networks (L2VPNs). This framework is intended to aid in standardizing protocols and mechanisms to support interoperable L2VPNs. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4664"/> <seriesInfo name="DOI" value="10.17487/RFC4664"/> </reference> <reference anchor="RFC8986"> <front> <title>Segment Routing over IPv6 (SRv6) Network Programming</title> <author fullname="C. Filsfils" initials="C." role="editor" surname="Filsfils"/> <author fullname="P. Camarillo" initials="P." role="editor" surname="Camarillo"/> <author fullname="J. Leddy" initials="J." surname="Leddy"/> <author fullname="D. Voyer" initials="D." surname="Voyer"/> <author fullname="S. Matsushima" initials="S." surname="Matsushima"/> <author fullname="Z. Li" initials="Z." surname="Li"/> <date month="February" year="2021"/> <abstract> <t>The Segment Routing over IPv6 (SRv6) Network Programming framework enables a network operator or an application to specify a packet processing program by encoding a sequence of instructions in the IPv6 packet header.</t> <t>Each instruction is implemented on one or several nodes in the network and identified by an SRv6 Segment Identifier in the packet.</t> <t>This document defines the SRv6 Network Programming concept and specifies the base set of SRv6 behaviors that enables the creation of interoperable overlays with underlay optimization.</t> </abstract> </front> <seriesInfo name="RFC" value="8986"/> <seriesInfo name="DOI" value="10.17487/RFC8986"/> </reference> <reference anchor="I-D.ietf-opsawg-teas-attachment-circuit"> <front> <title>YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service (ACaaS)</title> <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair"> <organization>Orange</organization> </author> <author fullname="Richard Roberts" initials="R." surname="Roberts"> <organization>Juniper</organization> </author> <author fullname="Oscar Gonzalez de Dios" initials="O. G." surname="de Dios"> <organization>Telefonica</organization> </author> <author fullname="Samier Barguil" initials="S." surname="Barguil"> <organization>Nokia</organization> </author> <author fullname="Bo Wu" initials="B." surname="Wu"> <organization>Huawei Technologies</organization> </author> <date day="23" month="January" year="2025"/> <abstract> <t> Delivery of network services assumes that appropriate setup is provisioned over the links that connect customer termination points and a provider network. The required setup to allow successful data exchange over these links is referred to as an attachment circuit (AC), while the underlying link is referred to as "bearer". This document specifies a YANG service data model for ACs. This model can be used for the provisioning of ACs before or during service provisioning (e.g., Network Slice Service). The document also specifies a YANG service model for managing bearers over which ACs are established. </t> </abstract> </front> <seriesInfo name="Internet-Draft" value="draft-ietf-opsawg-teas-attachment-circuit-20"/> </reference> <reference anchor="I-D.ietf-opsawg-ntw-attachment-circuit"> <front> <title>A Network YANG Data Model for Attachment Circuits</title> <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair"> <organization>Orange</organization> </author> <author fullname="Richard Roberts" initials="R." surname="Roberts"> <organization>Juniper</organization> </author> <author fullname="Oscar Gonzalez de Dios" initials="O. G." surname="de Dios"> <organization>Telefonica</organization> </author> <author fullname="Samier Barguil" initials="S." surname="Barguil"> <organization>Nokia</organization> </author> <author fullname="Bo Wu" initials="B." surname="Wu"> <organization>Huawei Technologies</organization> </author> <date day="23" month="January" year="2025"/> <abstract> <t> This document specifies a network model for attachment circuits. The model can be used for the provisioning of attachment circuits prior or during service provisioning (e.g., VPN, Network Slice Service). A companion service model is specified in the YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service (ACaaS) (I-D.ietf- opsawg-teas-attachment-circuit). The module augments the base network ('ietf-network') and the Service Attachment Point (SAP) models with the detailed information for the provisioning of attachment circuits in Provider Edges (PEs). </t> </abstract> </front> <seriesInfo name="Internet-Draft" value="draft-ietf-opsawg-ntw-attachment-circuit-16"/> </reference> <reference anchor="RFC8969"> <front> <title>A Framework for Automating Service and Network Management with YANG</title> <author fullname="Q. Wu" initials="Q." role="editor" surname="Wu"/> <author fullname="M. Boucadair" initials="M." role="editor" surname="Boucadair"/> <author fullname="D. Lopez" initials="D." surname="Lopez"/> <author fullname="C. Xie" initials="C." surname="Xie"/> <author fullname="L. Geng" initials="L." surname="Geng"/> <date month="January" year="2021"/> <abstract> <t>Data models provide a programmatic approach to represent services and networks. Concretely, they can be used to derive configuration information for network and service components, and state information that will be monitored and tracked. Data models can be used during the service and network management life cycle (e.g., service instantiation, service provisioning, service optimization, service monitoring, service diagnosing, and service assurance). Data models are also instrumental in the automation of network management, and they can provide closed-loop control for adaptive and deterministic service creation, delivery, and maintenance.</t> <t>This document describes a framework for service and network management automation that takes advantage of YANG modeling technologies. This framework is drawn from a network operator perspective irrespective of the origin of a data model; thus, it can accommodate YANG modules that are developed outside the IETF.</t> </abstract> </front> <seriesInfo name="RFC" value="8969"/> <seriesInfo name="DOI" value="10.17487/RFC8969"/> </reference> <reference anchor="I-D.ietf-teas-ietf-network-slice-nbi-yang"> <front> <title>A YANG Data Model for the RFC 9543 Network Slice Service</title> <author fullname="Bo Wu" initials="B." surname="Wu"> <organization>Huawei Technologies</organization> </author> <author fullname="Dhruv Dhody" initials="D." surname="Dhody"> <organization>Huawei Technologies</organization> </author> <author fullname="Reza Rokui" initials="R." surname="Rokui"> <organization>Ciena</organization> </author> <author fullname="Tarek Saad" initials="T." surname="Saad"> <organization>Cisco Systems, Inc</organization> </author> <author fullname="John Mullooly" initials="J." surname="Mullooly"> <organization>Cisco Systems, Inc</organization> </author> <date day="8" month="February" year="2025"/> <abstract> <t> This document defines a YANG data model for RFC 9543 Network Slice Service. The model can be used in the Network Slice Service interface between a customer and a provider that offers RFC 9543 Network Slice Services. </t> </abstract> </front> <seriesInfo name="Internet-Draft" value="draft-ietf-teas-ietf-network-slice-nbi-yang-22"/> </reference> <reference anchor="RFC4761"> <front> <title>Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling</title> <author fullname="K. Kompella" initials="K." role="editor" surname="Kompella"/> <author fullname="Y. Rekhter" initials="Y." role="editor" surname="Rekhter"/> <date month="January" year="2007"/> <abstract> <t>Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature.</t> <t>This document describes the functions required to offer VPLS, a mechanism for signaling a VPLS, and rules for forwarding VPLS frames across a packet switched network. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4761"/> <seriesInfo name="DOI" value="10.17487/RFC4761"/> </reference> <reference anchor="RFC4762"> <front> <title>Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling</title> <author fullname="M. Lasserre" initials="M." role="editor" surname="Lasserre"/> <author fullname="V. Kompella" initials="V." role="editor" surname="Kompella"/> <date month="January" year="2007"/> <abstract> <t>This document describes a Virtual Private LAN Service (VPLS) solution using pseudowires, a service previously implemented over other tunneling technologies and known as Transparent LAN Services (TLS). A VPLS creates an emulated LAN segment for a given set of users; i.e., it creates a Layer 2 broadcast domain that is fully capable of learning and forwarding on Ethernet MAC addresses and that is closed to a given set of users. Multiple VPLS services can be supported from a single Provider Edge (PE) node.</t> <t>This document describes the control plane functions of signaling pseudowire labels using Label Distribution Protocol (LDP), extending RFC 4447. It is agnostic to discovery protocols. The data plane functions of forwarding are also described, focusing in particular on the learning of MAC addresses. The encapsulation of VPLS packets is described by RFC 4448. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4762"/> <seriesInfo name="DOI" value="10.17487/RFC4762"/> </reference> <reference anchor="RFC8214"> <front> <title>Virtual Private Wire Service Support in Ethernet VPN</title> <author fullname="S. Boutros" initials="S." surname="Boutros"/> <author fullname="A. Sajassi" initials="A." surname="Sajassi"/> <author fullname="S. Salam" initials="S." surname="Salam"/> <author fullname="J. Drake" initials="J." surname="Drake"/> <author fullname="J. Rabadan" initials="J." surname="Rabadan"/> <date month="August" year="2017"/> <abstract> <t>This document describes how Ethernet VPN (EVPN) can be used to support the Virtual Private Wire Service (VPWS) in MPLS/IP networks. EVPN accomplishes the following for VPWS: provides Single-Active as well as All-Active multihoming with flow-based load-balancing, eliminates the need for Pseudowire (PW) signaling, and provides fast protection convergence upon node or link failure.</t> </abstract> </front> <seriesInfo name="RFC" value="8214"/> <seriesInfo name="DOI" value="10.17487/RFC8214"/> </reference> <reference anchor="RFC7623"> <front> <title>Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)</title> <author fullname="A. Sajassi" initials="A." role="editor" surname="Sajassi"/> <author fullname="S. Salam" initials="S." surname="Salam"/> <author fullname="N. Bitar" initials="N." surname="Bitar"/> <author fullname="A. Isaac" initials="A." surname="Isaac"/> <author fullname="W. Henderickx" initials="W." surname="Henderickx"/> <date month="September" year="2015"/> <abstract> <t>This document discusses how Ethernet Provider Backbone Bridging (PBB) can be combined with Ethernet VPN (EVPN) in order to reduce the number of BGP MAC Advertisement routes by aggregating Customer/Client MAC (C-MAC) addresses via Provider Backbone MAC (B-MAC) address, provide client MAC address mobility using C-MAC aggregation, confine the scope of C-MAC learning to only active flows, offer per-site policies, and avoid C-MAC address flushing on topology changes. The combined solution is referred to<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4664.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8986.xml"/> <!-- [I-D.ietf-opsawg-teas-attachment-circuit] Published asPBB-EVPN.</t> </abstract> </front> <seriesInfo name="RFC" value="7623"/> <seriesInfo name="DOI" value="10.17487/RFC7623"/> </reference> <reference anchor="RFC7432"> <front> <title>BGP MPLS-Based Ethernet VPN</title> <author fullname="A. Sajassi" initials="A." role="editor" surname="Sajassi"/> <author fullname="R. Aggarwal" initials="R." surname="Aggarwal"/> <author fullname="N. Bitar" initials="N." surname="Bitar"/> <author fullname="A. Isaac" initials="A." surname="Isaac"/> <author fullname="J. Uttaro" initials="J." surname="Uttaro"/> <author fullname="J. Drake" initials="J." surname="Drake"/> <author fullname="W. Henderickx" initials="W." surname="Henderickx"/> <date month="February" year="2015"/> <abstract> <t>This document describes procedures for BGP MPLS-based Ethernet VPNs (EVPN). The procedures described here meet the requirements specified inRFC7209 -- "Requirements for Ethernet VPN (EVPN)".</t> </abstract> </front> <seriesInfo name="RFC" value="7432"/> <seriesInfo name="DOI" value="10.17487/RFC7432"/> </reference> <reference anchor="RFC8365"> <front> <title>A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)</title> <author fullname="A. Sajassi" initials="A." role="editor" surname="Sajassi"/> <author fullname="J. Drake" initials="J." role="editor" surname="Drake"/> <author fullname="N. Bitar" initials="N." surname="Bitar"/> <author fullname="R. Shekhar" initials="R." surname="Shekhar"/> <author fullname="J. Uttaro" initials="J." surname="Uttaro"/> <author fullname="W. Henderickx" initials="W." surname="Henderickx"/> <date month="March" year="2018"/> <abstract> <t>This document specifies how Ethernet VPN (EVPN) can be used as a Network Virtualization Overlay (NVO) solution and explores the various tunnel encapsulation options over IP and their impact on the EVPN control plane and procedures. In particular, the following encapsulation options are analyzed: Virtual Extensible LAN (VXLAN), Network Virtualization using Generic Routing Encapsulation (NVGRE), and MPLS over GRE. This specification is also applicable to Generic Network Virtualization Encapsulation (GENEVE); however, some incremental work is required, which will be covered in a separate document. This document also specifies new multihoming procedures for split-horizon filtering and mass withdrawal. It also specifies EVPN route constructions for VXLAN/NVGRE encapsulations and Autonomous System Border Router (ASBR) procedures for multihoming of Network Virtualization Edge (NVE) devices.</t> </abstract> </front> <seriesInfo name="RFC" value="8365"/> <seriesInfo name="DOI" value="10.17487/RFC8365"/> </reference> <reference anchor="RFC9522"> <front> <title>Overview and Principles of Internet Traffic Engineering</title> <author fullname="A. Farrel" initials="A." role="editor" surname="Farrel"/> <date month="January" year="2024"/> <abstract> <t>This document describes the principles of traffic engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks and the networks that support IP networking and to provide a common basis for the development of traffic-engineering capabilities for the Internet. The principles, architectures, and methodologies for performance evaluation and performance optimization of operational networks are also discussed.</t> <t>This work was first published9834 --> <!-- [I-D.ietf-opsawg-ntw-attachment-circuit] Published as RFC3272 in May 2002. This document obsoletes9835 --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9834.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9835.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8969.xml"/> <!-- [I-D.ietf-teas-ietf-network-slice-nbi-yang] draft-ietf-teas-ietf-network-slice-nbi-yang-25 IESG State: RFC3272 by making a complete update to bring the text in line with best current practices for Internet traffic engineering and to include references to the latest relevant work in the IETF.</t> </abstract> </front> <seriesInfo name="RFC" value="9522"/> <seriesInfo name="DOI" value="10.17487/RFC9522"/> </reference> <reference anchor="RFC4026"> <front> <title>Provider Provisioned Virtual Private Network (VPN) Terminology</title> <author fullname="L. Andersson" initials="L." surname="Andersson"/> <author fullname="T. Madsen" initials="T." surname="Madsen"/> <date month="March" year="2005"/> <abstract> <t>The widespread interest in provider-provisioned Virtual Private Network (VPN) solutions lead to memos proposing different and overlapping solutions. The IETF working groups (first Provider Provisioned VPNs and later Layer 2 VPNs and Layer 3 VPNs) have discussed these proposals and documented specifications. This has lead to the development of a partially new set of concepts used to describe the set of VPN services.</t> <t>To a certain extent, more than one term covers the same concept, and sometimes the same term covers more than one concept. This document seeks to make the terminology in the area clearer and more intuitive. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4026"/> <seriesInfo name="DOI" value="10.17487/RFC4026"/> </reference> <reference anchor="RFC4176"> <front> <title>Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management</title> <author fullname="Y. El Mghazli" initials="Y." role="editor" surname="El Mghazli"/> <author fullname="T. Nadeau" initials="T." surname="Nadeau"/> <author fullname="M. Boucadair" initials="M." surname="Boucadair"/> <author fullname="K. Chan" initials="K." surname="Chan"/> <author fullname="A. Gonguet" initials="A." surname="Gonguet"/> <date month="October" year="2005"/> <abstract> <t>This document provides a framework for the operation and management of Layer 3 Virtual Private Networks (L3VPNs). This framework intends to produce a coherent description of the significant technical issues that are important in the design of L3VPN management solutions. The selection of specific approaches, and making choices among information models and protocols are outside the scope of this document. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4176"/> <seriesInfo name="DOI" value="10.17487/RFC4176"/> </reference> <reference anchor="RFC6136"> <front> <title>Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and Framework</title> <author fullname="A. Sajassi" initials="A." role="editor" surname="Sajassi"/> <author fullname="D. Mohan" initials="D." role="editor" surname="Mohan"/> <date month="March" year="2011"/> <abstract> <t>This document provides framework and requirements for Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM). The OAM framework is intended to provide OAM layering across L2VPN services, pseudowires (PWs), and Packet Switched Network (PSN) tunnels. This document is intended to identify OAM requirements for L2VPN services, i.e., Virtual Private LAN Service (VPLS), Virtual Private Wire Service (VPWS), and IP-only LAN Service (IPLS). Furthermore, if L2VPN service OAM requirements impose specific requirements on PW OAM and/or PSN OAM, those specific PW and/or PSN OAM requirements are also identified. This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="6136"/> <seriesInfo name="DOI" value="10.17487/RFC6136"/> </reference> <reference anchor="RFC7422"> <front> <title>Deterministic Address Mapping to Reduce Logging in Carrier-Grade NAT Deployments</title> <author fullname="C. Donley" initials="C." surname="Donley"/> <author fullname="C. Grundemann" initials="C." surname="Grundemann"/> <author fullname="V. Sarawat" initials="V." surname="Sarawat"/> <author fullname="K. Sundaresan" initials="K." surname="Sundaresan"/> <author fullname="O. Vautrin" initials="O." surname="Vautrin"/> <date month="December" year="2014"/> <abstract> <t>In some instances, Service Providers (SPs) have a legal logging requirement to be able to map a subscriber's inside address with the address used on the public Internet (e.g., for abuse response). Unfortunately, many logging solutions for Carrier-Grade NATs (CGNs) require active logging of dynamic translations. CGN port assignments are often per connection, but they could optionally use port ranges. Research indicates that per-connection logging is not scalable in many residential broadband services. This document suggests a way to manage CGN translations in such a wayEd Queue (MISSREF) asto significantly reduce the amount of logging required while providing traceability for abuse response. IPv6 is,ofcourse, the preferred solution. While deployment is in progress, SPs are forced by business imperatives to maintain support for IPv4. This note addresses the IPv4 part of the network when a CGN solution is in use.</t> </abstract> </front> <seriesInfo name="RFC" value="7422"/> <seriesInfo name="DOI" value="10.17487/RFC7422"/> </reference> <reference anchor="RFC7510"> <front> <title>Encapsulating MPLS in UDP</title> <author fullname="X. Xu" initials="X." surname="Xu"/> <author fullname="N. Sheth" initials="N." surname="Sheth"/> <author fullname="L. Yong" initials="L." surname="Yong"/> <author fullname="R. Callon" initials="R." surname="Callon"/> <author fullname="D. Black" initials="D." surname="Black"/> <date month="April" year="2015"/> <abstract> <t>This document specifies an IP-based encapsulation for MPLS, called MPLS-in-UDP for situations where UDP (User Datagram Protocol) encapsulation is preferred to direct use of MPLS, e.g., to enable UDP-based ECMP (Equal-Cost Multipath) or link aggregation. The MPLS- in-UDP encapsulation technology must only be deployed within a single network (with a single network operator) or networks of an adjacent set of cooperating network operators where traffic is managed to avoid congestion, rather than over the Internet where congestion control is required. Usage restrictions apply to MPLS-in-UDP usage for traffic that is not congestion controlled and to UDP zero checksum usage with IPv6.</t> </abstract> </front> <seriesInfo name="RFC" value="7510"/> <seriesInfo name="DOI" value="10.17487/RFC7510"/> </reference> <reference anchor="RFC4360"> <front> <title>BGP Extended Communities Attribute</title> <author fullname="S. Sangli" initials="S." surname="Sangli"/> <author fullname="D. Tappan" initials="D." surname="Tappan"/> <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/> <date month="February" year="2006"/> <abstract> <t>This document describes the "extended community" BGP-4 attribute. This attribute provides a mechanism for labeling information carried in BGP-4. These labels can be used to control the distribution of this information, or for other applications. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4360"/> <seriesInfo name="DOI" value="10.17487/RFC4360"/> </reference> <reference anchor="RFC1997"> <front> <title>BGP Communities Attribute</title> <author fullname="R. Chandra" initials="R." surname="Chandra"/> <author fullname="P. Traina" initials="P." surname="Traina"/> <author fullname="T. Li" initials="T." surname="Li"/> <date month="August" year="1996"/> <abstract> <t>This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="1997"/> <seriesInfo name="DOI" value="10.17487/RFC1997"/> </reference>06/23/25 --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-teas-ietf-network-slice-nbi-yang.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4761.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4762.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8214.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7623.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7432.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8365.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9522.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4026.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4176.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6136.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7422.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7510.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4360.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1997.xml"/> <!-- [I-D.cbs-teas-5qi-to-dscp-mapping] draft-cbs-teas-5qi-to-dscp-mapping-04 IESG State: I-D Exists Long Way --> <referenceanchor="I-D.cbs-teas-5qi-to-dscp-mapping">anchor="I-D.cbs-teas-5qi-to-dscp-mapping" target="https://datatracker.ietf.org/doc/html/draft-cbs-teas-5qi-to-dscp-mapping-04"> <front> <title>5QI to DiffServ DSCP Mapping Example for Enforcement of 5G End-to-End Network Slice QoS</title> <author initials="L. M." surname="Contreras" fullname="Luis M. Contreras"initials="L. M." surname="Contreras">role="editor"> <organization>Telefonica</organization> </author> <author initials="I." surname="Bykov" fullname="Ivan Bykov"initials="I." surname="Bykov">role="editor"> <organization>Ribbon Communications</organization> </author> <author initials="K. G." surname="Szarkowicz" fullname="Krzysztof Grzegorz Szarkowicz"initials="K. G." surname="Szarkowicz">role="editor"> <organization>Juniper Networks</organization> </author> <dateday="21" month="October" year="2024"/> <abstract> <t> 5G End-to-End Network Slice QoS is an essential aspect of network slicing, as described in both IETF drafts and the 3GPP specifications. Network slicing allows for the creation of multiple logical networks on top of a shared physical infrastructure, tailored to support specific use cases or services. The primary goal of QoS in network slicing is to ensure that the specific performance requirements of each slice are met, including latency, reliability, and throughput. </t> </abstract>month="July" day="5" year="2025" /> </front> <seriesInfo name="Internet-Draft"value="draft-cbs-teas-5qi-to-dscp-mapping-03"/>value="draft-cbs-teas-5qi-to-dscp-mapping-04" /> </reference><reference anchor="RFC2475"> <front> <title>An Architecture for Differentiated Services</title> <author fullname="S. Blake" initials="S." surname="Blake"/> <author fullname="D. Black" initials="D." surname="Black"/> <author fullname="M. Carlson" initials="M." surname="Carlson"/> <author fullname="E. Davies" initials="E." surname="Davies"/> <author fullname="Z. Wang" initials="Z." surname="Wang"/> <author fullname="W. Weiss" initials="W." surname="Weiss"/> <date month="December" year="1998"/> <abstract> <t>This document defines an architecture for implementing scalable service differentiation in the Internet. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="2475"/> <seriesInfo name="DOI" value="10.17487/RFC2475"/> </reference> <reference anchor="RFC2698"> <front> <title>A Two Rate Three Color Marker</title> <author fullname="J. Heinanen" initials="J." surname="Heinanen"/> <author fullname="R. Guerin" initials="R." surname="Guerin"/> <date month="September" year="1999"/> <abstract> <t>This document defines a Two Rate Three Color Marker (trTCM), which can be used<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2475.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2698.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4115.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7806.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2474.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8100.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3209.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9256.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9350.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9182.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9291.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5440.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9408.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8299.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8466.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9330.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6291.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7276.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5286.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5714.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8355.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9375.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7799.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8641.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4365.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6624.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4252.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9000.xml"/> <!-- [I-D.ietf-teas-ns-controller-models] draft-ietf-teas-ns-controller-models-05 IESG State: I-D Exists asa component in a Diffserv traffic conditioner. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="2698"/> <seriesInfo name="DOI" value="10.17487/RFC2698"/> </reference> <reference anchor="RFC4115"> <front> <title>A Differentiated Service Two-Rate, Three-Color Marker with Efficient Handlingofin-Profile Traffic</title> <author fullname="O. Aboul-Magd" initials="O." surname="Aboul-Magd"/> <author fullname="S. Rabie" initials="S." surname="Rabie"/> <date month="July" year="2005"/> <abstract> <t>This document describes a two-rate, three-color marker that has been in use for data services including Frame Relay services. This marker can be used for metering per-flow traffic in the emerging IP and L2 VPN services. The marker defined here is different from previously defined markers in the handling of the in-profile traffic. Furthermore, this marker doesn't impose peak-rate shaping requirements on customer edge (CE) devices. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4115"/> <seriesInfo name="DOI" value="10.17487/RFC4115"/> </reference> <reference anchor="RFC7806"> <front> <title>On Queuing, Marking, and Dropping</title> <author fullname="F. Baker" initials="F." surname="Baker"/> <author fullname="R. Pan" initials="R." surname="Pan"/> <date month="April" year="2016"/> <abstract> <t>This note discusses queuing and marking/dropping algorithms. While these algorithms may be implemented in a coupled manner, this note argues that specifications, measurements, and comparisons should decouple the different algorithms and their contributions to system behavior.</t> </abstract> </front> <seriesInfo name="RFC" value="7806"/> <seriesInfo name="DOI" value="10.17487/RFC7806"/> </reference> <reference anchor="RFC2474"> <front> <title>Definition10/3/25 --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-teas-ns-controller-models.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4111.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4381.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9099.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5952.xml"/> </references> </references> <?line 2318?> <section anchor="sec-v6-ex"> <name>Example ofthe Differentiated Services Field (DS Field) in the IPv4 andLocal IPv6Headers</title> <author fullname="K. Nichols" initials="K." surname="Nichols"/> <author fullname="S. Blake" initials="S." surname="Blake"/> <author fullname="F. Baker" initials="F." surname="Baker"/> <author fullname="D. Black" initials="D." surname="Black"/> <date month="December" year="1998"/> <abstract> <t>This document defines the IP header field, called the DS (for differentiated services) field. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="2474"/> <seriesInfo name="DOI" value="10.17487/RFC2474"/> </reference> <reference anchor="RFC8100"> <front> <title>Diffserv-Interconnection Classes and Practice</title> <author fullname="R. Geib" initials="R." role="editor" surname="Geib"/> <author fullname="D. Black" initials="D." surname="Black"/> <date month="March" year="2017"/> <abstract> <t>This document defines a limited common set of Diffserv Per-Hop Behaviors (PHBs) and Diffserv Codepoints (DSCPs) to be applied at (inter)connections of two separately administered and operated networks, and it explains how this approach can simplify network configuration and operation. Many network providers operate Multiprotocol Label Switching (MPLS) using Treatment Aggregates for traffic marked with different Diffserv Per-Hop Behaviors and use MPLS for interconnection with other networks. This document offers a simple interconnection approach that may simplify operation of Diffserv for network interconnection among providers that use MPLS and apply the Short Pipe Model. While motivated by the requirements of MPLS network operators that use Short Pipe Model tunnels, this document is applicable to other networks, both MPLS and non-MPLS.</t> </abstract> </front> <seriesInfo name="RFC" value="8100"/> <seriesInfo name="DOI" value="10.17487/RFC8100"/> </reference> <reference anchor="RFC3209"> <front> <title>RSVP-TE: Extensions to RSVP for LSP Tunnels</title> <author fullname="D. Awduche" initials="D." surname="Awduche"/> <author fullname="L. Berger" initials="L." surname="Berger"/> <author fullname="D. Gan" initials="D." surname="Gan"/> <author fullname="T. Li" initials="T." surname="Li"/> <author fullname="V. Srinivasan" initials="V." surname="Srinivasan"/> <author fullname="G. Swallow" initials="G." surname="Swallow"/> <date month="December" year="2001"/> <abstract> <t>This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="3209"/> <seriesInfo name="DOI" value="10.17487/RFC3209"/> </reference> <reference anchor="RFC9256"> <front> <title>Segment Routing Policy Architecture</title> <author fullname="C. Filsfils" initials="C." surname="Filsfils"/> <author fullname="K. Talaulikar" initials="K." role="editor" surname="Talaulikar"/> <author fullname="D. Voyer" initials="D." surname="Voyer"/> <author fullname="A. Bogdanov" initials="A." surname="Bogdanov"/> <author fullname="P. Mattes" initials="P." surname="Mattes"/> <date month="July" year="2022"/> <abstract> <t>Segment Routing (SR) allows a node to steer a packet flow along any path. Intermediate per-path states are eliminated thanks to source routing. SR Policy is an ordered list of segments (i.e., instructions) that represent a source-routed policy. Packet flows are steered into an SR Policy on a node where it is instantiated called a headend node. The packets steered into an SR Policy carry an ordered list of segments associated with that SR Policy.</t> <t>This document updates RFC 8402 as it details the concepts of SR Policy and steering into an SR Policy.</t> </abstract> </front> <seriesInfo name="RFC" value="9256"/> <seriesInfo name="DOI" value="10.17487/RFC9256"/> </reference> <reference anchor="RFC9350"> <front> <title>IGP Flexible Algorithm</title> <author fullname="P. Psenak" initials="P." role="editor" surname="Psenak"/> <author fullname="S. Hegde" initials="S." surname="Hegde"/> <author fullname="C. Filsfils" initials="C." surname="Filsfils"/> <author fullname="K. Talaulikar" initials="K." surname="Talaulikar"/> <author fullname="A. Gulko" initials="A." surname="Gulko"/> <date month="February" year="2023"/> <abstract> <t>IGP protocols historically compute the best paths over the network based on the IGP metric assigned to the links. Many network deployments use RSVP-TE or Segment Routing - Traffic Engineering (SR-TE) to steer traffic over a path that is computed using different metrics or constraints than the shortest IGP path. This document specifies a solution that allows IGPs themselves to compute constraint-based paths over the network. This document also specifies a way of using Segment Routing (SR) Prefix-SIDs and SRv6 locators to steer packets along the constraint-based paths.</t> </abstract> </front> <seriesInfo name="RFC" value="9350"/> <seriesInfo name="DOI" value="10.17487/RFC9350"/> </reference> <reference anchor="RFC9182"> <front> <title>A YANG Network Data Model for Layer 3 VPNs</title> <author fullname="S. Barguil" initials="S." surname="Barguil"/> <author fullname="O. Gonzalez de Dios" initials="O." role="editor" surname="Gonzalez de Dios"/> <author fullname="M. Boucadair" initials="M." role="editor" surname="Boucadair"/> <author fullname="L. Munoz" initials="L." surname="Munoz"/> <author fullname="A. Aguado" initials="A." surname="Aguado"/> <date month="February" year="2022"/> <abstract> <t>As a complement to the Layer 3 Virtual Private Network Service Model (L3SM), which is used for communication between customers and service providers, this document defines an L3VPN Network Model (L3NM) that can be used for the provisioning of Layer 3 Virtual Private Network (L3VPN) services within a service provider network. The model provides a network-centric view of L3VPN services.</t> <t>The L3NM is meant to be used by a network controller to derive the configuration information that will be sent to relevant network devices. The model can also facilitate communication between a service orchestrator and a network controller/orchestrator.</t> </abstract> </front> <seriesInfo name="RFC" value="9182"/> <seriesInfo name="DOI" value="10.17487/RFC9182"/> </reference> <reference anchor="RFC9291"> <front> <title>A YANG Network Data Model for Layer 2 VPNs</title> <author fullname="M. Boucadair" initials="M." role="editor" surname="Boucadair"/> <author fullname="O. Gonzalez de Dios" initials="O." role="editor" surname="Gonzalez de Dios"/> <author fullname="S. Barguil" initials="S." surname="Barguil"/> <author fullname="L. Munoz" initials="L." surname="Munoz"/> <date month="September" year="2022"/> <abstract> <t>This document defines an L2VPN Network Model (L2NM) that can be used to manage the provisioning of Layer 2 Virtual Private Network (L2VPN) services within a network (e.g., a service provider network). The L2NM complements the L2VPN Service Model (L2SM) by providing a network-centric view of the service that is internal to a service provider. The L2NM is particularly meant to be used by a network controller to derive the configuration information that will be sent to relevant network devices.</t> <t>Also, this document defines a YANG module to manage Ethernet segments and the initial versions of two IANA-maintained modules that include a set of identities of BGP Layer 2 encapsulation types and pseudowire types.</t> </abstract> </front> <seriesInfo name="RFC" value="9291"/> <seriesInfo name="DOI" value="10.17487/RFC9291"/> </reference> <reference anchor="RFC5440"> <front> <title>Path Computation Element (PCE) Communication Protocol (PCEP)</title> <author fullname="JP. Vasseur" initials="JP." role="editor" surname="Vasseur"/> <author fullname="JL. Le Roux" initials="JL." role="editor" surname="Le Roux"/> <date month="March" year="2009"/> <abstract> <t>This document specifies the Path Computation Element (PCE) Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a PCE, or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed to be flexible and extensible so as to easily allow for the addition of further messages and objects, should further requirements be expressed in the future. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="5440"/> <seriesInfo name="DOI" value="10.17487/RFC5440"/> </reference> <reference anchor="RFC9408"> <front> <title>A YANG Network Data Model for Service Attachment Points (SAPs)</title> <author fullname="M. Boucadair" initials="M." role="editor" surname="Boucadair"/> <author fullname="O. Gonzalez de Dios" initials="O." surname="Gonzalez de Dios"/> <author fullname="S. Barguil" initials="S." surname="Barguil"/> <author fullname="Q. Wu" initials="Q." surname="Wu"/> <author fullname="V. Lopez" initials="V." surname="Lopez"/> <date month="June" year="2023"/> <abstract> <t>This document defines a YANG data model for representing an abstract view of the provider network topology that contains the points from which its services can be attached (e.g., basic connectivity, VPN, network slices). Also, the model can be used to retrieve the points where the services are actually being delivered to customers (including peer networks).</t> <t>This document augments the 'ietf-network' data model defined in RFC 8345 by adding the concept of Service Attachment Points (SAPs). The SAPs are the network reference points to which network services, such as Layer 3 Virtual Private Network (L3VPN) or Layer 2 Virtual Private Network (L2VPN), can be attached. One or multiple services can be bound to the same SAP. Both User-to-Network Interface (UNI) and Network-to-Network Interface (NNI) are supported in the SAP data model.</t> </abstract> </front> <seriesInfo name="RFC" value="9408"/> <seriesInfo name="DOI" value="10.17487/RFC9408"/> </reference> <reference anchor="RFC8299"> <front> <title>YANG Data Model for L3VPN Service Delivery</title> <author fullname="Q. Wu" initials="Q." role="editor" surname="Wu"/> <author fullname="S. Litkowski" initials="S." surname="Litkowski"/> <author fullname="L. Tomotaki" initials="L." surname="Tomotaki"/> <author fullname="K. Ogaki" initials="K." surname="Ogaki"/> <date month="January" year="2018"/> <abstract> <t>This document defines a YANG data model that can be used for communication between customers and network operators and to deliver a Layer 3 provider-provisioned VPN service. This document is limited to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364. This model is intended to be instantiated at the management system to deliver the overall service. It is not a configuration model to be used directly on network elements. This model provides an abstracted view of the Layer 3 IP VPN service configuration components. It will be up to the management system to take this model as input and use specific configuration models to configure the different network elements to deliver the service. How the configuration of network elements is done is out of scope for this document.</t> <t>This document obsoletes RFC 8049; it replaces the unimplementable module in that RFC with a new module with the same name that is not backward compatible. The changes are a series of small fixes to the YANG module and some clarifications to the text.</t> </abstract> </front> <seriesInfo name="RFC" value="8299"/> <seriesInfo name="DOI" value="10.17487/RFC8299"/> </reference> <reference anchor="RFC8466"> <front> <title>A YANG Data ModelAddressing Plan forLayer 2 Virtual PrivateNetwork(L2VPN) Service Delivery</title> <author fullname="B. Wen" initials="B." surname="Wen"/> <author fullname="G. Fioccola" initials="G." role="editor" surname="Fioccola"/> <author fullname="C. Xie" initials="C." surname="Xie"/> <author fullname="L. Jalil" initials="L." surname="Jalil"/> <date month="October" year="2018"/> <abstract> <t>This document defines a YANG data model that can be used to configure a Layer 2 provider-provisioned VPN service. It is up to a management system to take this as an input and generate specific configuration models to configure the different network elements to deliver the service. How this configuration of network elements is doneFunctions</name> <!-- [rfced] Will readers understand what "the above approach" isout of scope for this document.</t> <t>The YANG data model definedin thisdocument includes support for point-to-point Virtual Private Wire Services (VPWSs) and multipoint Virtual Private LAN Services (VPLSs) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFCs 4761 and 6624.</t> <t>The YANG data model defined insentence? Does thisdocument conforms to the Network Management Datastore Architecture defined in RFC 8342.</t> </abstract> </front> <seriesInfo name="RFC" value="8466"/> <seriesInfo name="DOI" value="10.17487/RFC8466"/> </reference> <reference anchor="RFC9330"> <front> <title>Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture</title> <author fullname="B. Briscoe" initials="B." role="editor" surname="Briscoe"/> <author fullname="K. De Schepper" initials="K." surname="De Schepper"/> <author fullname="M. Bagnulo" initials="M." surname="Bagnulo"/> <author fullname="G. White" initials="G." surname="White"/> <date month="January" year="2023"/> <abstract> <t>This document describes the L4S architecture, which enables Internet applications to achieve low queuing latency, low congestion loss, and scalable throughput control. L4S is based on the insight that the root cause of queuing delay is in the capacity-seeking congestion controllers of senders, not in the queue itself. With the L4S architecture, all Internet applications could (but do not have to) transition away from congestion control algorithms that cause substantial queuing delay and instead adopt a new class of congestion controls that can seek capacity with very little queuing. These are aided by a modified form of Explicit Congestion Notification (ECN) from the network. With this new architecture, applications can have both low latency and high throughput.</t> <t>The architecture primarily concerns incremental deployment. It defines mechanisms that allow the new class of L4S congestion controls to coexist with 'Classic' congestion controls in a shared network. The aim is for L4S latency and throughput to be usually much better (and rarely worse) while typically not impacting Classic performance.</t> </abstract> </front> <seriesInfo name="RFC" value="9330"/> <seriesInfo name="DOI" value="10.17487/RFC9330"/> </reference> <reference anchor="RFC6291"> <front> <title>Guidelines for the Use of the "OAM" Acronym in the IETF</title> <author fullname="L. Andersson" initials="L." surname="Andersson"/> <author fullname="H. van Helvoort" initials="H." surname="van Helvoort"/> <author fullname="R. Bonica" initials="R." surname="Bonica"/> <author fullname="D. Romascanu" initials="D." surname="Romascanu"/> <author fullname="S. Mansfield" initials="S." surname="Mansfield"/> <date month="June" year="2011"/> <abstract> <t>At first glance, the acronym "OAM" seems to be well-known and well-understood. Looking at the acronym a bit more closely reveals a set of recurring problems that are revisited time and again.</t> <t>This document provides a definition of the acronym "OAM" (Operations, Administration, and Maintenance) for use in all future IETF documents thatrefer toOAM. There are other definitions and acronyms that will be discussed while exploringthedefinition of the constituent parts of the "OAM" term. This memo documents an Internet Best Current Practice.</t> </abstract> </front> <seriesInfo name="BCP" value="161"/> <seriesInfo name="RFC" value="6291"/> <seriesInfo name="DOI" value="10.17487/RFC6291"/> </reference> <reference anchor="RFC7276"> <front> <title>An Overview of Operations, Administration, and Maintenance (OAM) Tools</title> <author fullname="T. Mizrahi" initials="T." surname="Mizrahi"/> <author fullname="N. Sprecher" initials="N." surname="Sprecher"/> <author fullname="E. Bellagamba" initials="E." surname="Bellagamba"/> <author fullname="Y. Weingarten" initials="Y." surname="Weingarten"/> <date month="June" year="2014"/> <abstract> <t>Operations, Administration, and Maintenance (OAM) is a general term that refers to a toolset for fault detection and isolation, and for performance measurement. Over the years, various OAM tools have been defined for various layers in the protocol stack.</t> <t>This document summarizes some of the OAM tools defined in the IETF in the context of IP unicast, MPLS, MPLS Transport Profile (MPLS-TP), pseudowires, and Transparent Interconnection of Lots of Links (TRILL). This document focuses on tools for detecting and isolating failures in networks and for performance monitoring. Control and management aspects of OAM are outside the scope of this document. Network repair functions such as Fast Reroute (FRR) and protection switching, which are often triggered by OAM protocols, are also out of the scope of this document.</t> <t>The target audience of this document includes network equipment vendors, network operators, and standards development organizations. This document can be used as an index to some of the main OAM tools defined in the IETF. At the end of the document, a list of the OAM toolsets and a list of the OAM functions are presented as a summary.</t> </abstract> </front> <seriesInfo name="RFC" value="7276"/> <seriesInfo name="DOI" value="10.17487/RFC7276"/> </reference> <reference anchor="RFC5286"> <front> <title>Basic Specification for IP Fast Reroute: Loop-Free Alternates</title> <author fullname="A. Atlas" initials="A." role="editor" surname="Atlas"/> <author fullname="A. Zinin" initials="A." role="editor" surname="Zinin"/> <date month="September" year="2008"/> <abstract> <t>This document describes the use of loop-free alternates to provide local protection for unicast traffic in pure IP and MPLS/LDP networks in the event of a single failure, whether link, node, or shared risk link group (SRLG). The goal of this technology is to reduce the packet loss that happens while routers converge after a topology change due to a failure. Rapid failure repair is achieved through use of precalculated backup next-hops that are loop-free and safe to use until the distributed network convergence process completes. This simpleapproachdoes not require any support from other routers. The extent to which this goal can be met by this specification is dependent on the topology of the network. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="5286"/> <seriesInfo name="DOI" value="10.17487/RFC5286"/> </reference> <reference anchor="RFC5714"> <front> <title>IP Fast Reroute Framework</title> <author fullname="M. Shand" initials="M." surname="Shand"/> <author fullname="S. Bryant" initials="S." surname="Bryant"/> <date month="January" year="2010"/> <abstract> <t>This document provides a framework for the development of IP fast- reroute mechanisms that provide protection against link or router failure by invoking locally determined repair paths. Unlike MPLS fast-reroute, the mechanisms are applicable to a network employing conventional IP routing and forwarding. This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="5714"/> <seriesInfo name="DOI" value="10.17487/RFC5714"/> </reference> <reference anchor="RFC8355"> <front> <title>Resiliency Use Cases in Source Packet Routing in Networking (SPRING) Networks</title> <author fullname="C. Filsfils" initials="C." role="editor" surname="Filsfils"/> <author fullname="S. Previdi" initials="S." role="editor" surname="Previdi"/> <author fullname="B. Decraene" initials="B." surname="Decraene"/> <author fullname="R. Shakir" initials="R." surname="Shakir"/> <date month="March" year="2018"/> <abstract> <t>This document identifies and describes the requirements for a set of use cases related to Segment Routing network resiliency on Source Packet Routing in Networking (SPRING) networks.</t> </abstract> </front> <seriesInfo name="RFC" value="8355"/> <seriesInfo name="DOI" value="10.17487/RFC8355"/> </reference> <reference anchor="RFC9375"> <front> <title>A YANG Data Model for Network and VPN Service Performance Monitoring</title> <author fullname="B. Wu" initials="B." role="editor" surname="Wu"/> <author fullname="Q. Wu" initials="Q." role="editor" surname="Wu"/> <author fullname="M. Boucadair" initials="M." role="editor" surname="Boucadair"/> <author fullname="O. Gonzalez de Dios" initials="O." surname="Gonzalez de Dios"/> <author fullname="B. Wen" initials="B." surname="Wen"/> <date month="April" year="2023"/> <abstract> <t>The data model for network topologies defined in RFC 8345 introduces vertical layering relationships between networks that can be augmented to cover network and service topologies. This document defines a YANG module for performance monitoring (PM) of both underlay networks and overlay VPN services that can be used to monitor and manage network performance on the topology of both layers.</t> </abstract> </front> <seriesInfo name="RFC" value="9375"/> <seriesInfo name="DOI" value="10.17487/RFC9375"/> </reference> <reference anchor="RFC7799"> <front> <title>Active and Passive Metrics and Methods (with Hybrid Types In-Between)</title> <author fullname="A. Morton" initials="A." surname="Morton"/> <date month="May" year="2016"/> <abstract> <t>This memo provides clear definitions for Active and Passive performance assessment. The construction of Metrics and Methods can be described as either "Active" or "Passive". Some methods may use a subset of both Active and Passive attributes, and we refer to these as "Hybrid Methods". This memo also describes multiple dimensions to help evaluate new methods as they emerge.</t> </abstract> </front> <seriesInfo name="RFC" value="7799"/> <seriesInfo name="DOI" value="10.17487/RFC7799"/> </reference> <reference anchor="RFC8641"> <front> <title>Subscription to YANG Notifications for Datastore Updates</title> <author fullname="A. Clemm" initials="A." surname="Clemm"/> <author fullname="E. Voit" initials="E." surname="Voit"/> <date month="September" year="2019"/> <abstract> <t>This document describes a mechanism that allows subscriber applications to request a continuous and customized stream of updates from a YANG datastore. Providing such visibility into updates enables new capabilities based on the remote mirroring and monitoring of configuration and operational state.</t> </abstract> </front> <seriesInfo name="RFC" value="8641"/> <seriesInfo name="DOI" value="10.17487/RFC8641"/> </reference> <reference anchor="RFC4365"> <front> <title>Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)</title> <author fullname="E. Rosen" initials="E." surname="Rosen"/> <date month="February" year="2006"/> <abstract> <t>This document provides an Applicability Statement for the Virtual Private Network (VPN) solutiondescribed inRFC 4364 and other documents listed in the References section. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4365"/> <seriesInfo name="DOI" value="10.17487/RFC4365"/> </reference> <reference anchor="RFC6624"> <front> <title>Layer 2 Virtual Private Networks Using BGP for Auto-Discovery and Signaling</title> <author fullname="K. Kompella" initials="K." surname="Kompella"/> <author fullname="B. Kothari" initials="B." surname="Kothari"/> <author fullname="R. Cherukuri" initials="R." surname="Cherukuri"/> <date month="May" year="2012"/> <abstract> <t>Layer 2 Virtual Private Networks (L2VPNs) based on Frame RelaySection 4.2 orATM circuits have been around a long time; more recently, Ethernet VPNs, including Virtual Private LAN Service, have become popular. Traditional L2VPNs often required a separate Service Provider infrastructure for each type and yet another for the Internet and IP VPNs. In addition, L2VPN provisioning was cumbersome. This document presents a new approach to the problem of offering L2VPN services where the L2VPN customer's experience is virtually identical to that offered by traditional L2VPNs, but such that a Service Provider can maintain a single network for L2VPNs, IP VPNs, and the Internet, as well as a common provisioning methodology for all services. This document is not an Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="6624"/> <seriesInfo name="DOI" value="10.17487/RFC6624"/> </reference> <reference anchor="RFC6241"> <front> <title>Network Configuration Protocol (NETCONF)</title> <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/> <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/> <date month="June" year="2011"/> <abstract> <t>The Network Configuration Protocol (NETCONF) definedin this documentprovides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6241"/> <seriesInfo name="DOI" value="10.17487/RFC6241"/> </reference> <reference anchor="RFC8040"> <front> <title>RESTCONF Protocol</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="K. Watsen" initials="K." surname="Watsen"/> <date month="January" year="2017"/> <abstract> <t>This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t> </abstract> </front> <seriesInfo name="RFC" value="8040"/> <seriesInfo name="DOI" value="10.17487/RFC8040"/> </reference> <reference anchor="RFC4252"> <front> <title>The Secure Shell (SSH) Authentication Protocol</title> <author fullname="T. Ylonen" initials="T." surname="Ylonen"/> <author fullname="C. Lonvick" initials="C." role="editor" surname="Lonvick"/> <date month="January" year="2006"/> <abstract> <t>The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are describedinseparate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="4252"/> <seriesInfo name="DOI" value="10.17487/RFC4252"/> </reference> <reference anchor="RFC8446"> <front> <title>The Transport Layer Security (TLS) Protocol Version 1.3</title> <author fullname="E. Rescorla" initials="E." surname="Rescorla"/> <date month="August" year="2018"/> <abstract> <t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t> <t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t> </abstract> </front> <seriesInfo name="RFC" value="8446"/> <seriesInfo name="DOI" value="10.17487/RFC8446"/> </reference> <reference anchor="RFC9000"> <front> <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title> <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/> <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/> <date month="May" year="2021"/> <abstract> <t>This document defines the core ofgeneral? Original: Different IPv6 address allocation schemes following theQUIC transport protocol. QUIC provides applicationsabove approach may be used, withflow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availabilityone example allocation shown ina range of deployment circumstances. Accompanying documents describeFigure 31. Perhaps: Different IPv6 address allocation schemes following theintegration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t> </abstract> </front> <seriesInfo name="RFC" value="9000"/> <seriesInfo name="DOI" value="10.17487/RFC9000"/> </reference> <reference anchor="I-D.ietf-teas-ns-controller-models"> <front> <title>IETF Network Slice Controller and its Associated Data Models</title> <author fullname="Luis M. Contreras" initials="L. M." surname="Contreras"> <organization>Telefonica</organization> </author> <author fullname="Reza Rokui" initials="R." surname="Rokui"> <organization>Ciena</organization> </author> <author fullname="Jeff Tantsura" initials="J." surname="Tantsura"> <organization>Nvidia</organization> </author> <author fullname="Bo Wu" initials="B." surname="Wu"> <organization>Huawei</organization> </author> <author fullname="Xufeng Liu" initials="X." surname="Liu"> <organization>Alef Edge</organization> </author> <date day="3" month="March" year="2025"/> <abstract> <t> This document describes anapproachfor structuring the IETF Network Slice Controller as well as how to use different data models being defined for IETF Network Slice Service provision (and how they are related). It is not the purpose of this document to standardize or constrain the implementation the IETF Network Slice Controller. </t> </abstract> </front> <seriesInfo name="Internet-Draft" value="draft-ietf-teas-ns-controller-models-04"/> </reference> <reference anchor="RFC4111"> <front> <title>Security Framework for Provider-Provisioned Virtual Private Networks (PPVPNs)</title> <author fullname="L. Fang" initials="L." role="editor" surname="Fang"/> <date month="July" year="2005"/> <abstract> <t>This document addresses security aspects pertaining to Provider-Provisioned Virtual Private Networks (PPVPNs). First, it describes the security threatsinthe context of PPVPNs and defensive techniques to combat those threats. It considers security issues deriving both from malicious behavior of anyone and from negligent or incorrect behavior of the providers. It also describes how these security attacks should be detected and reported. It then discusses possible user requirements for security of a PPVPN service. These user requirements translate into corresponding provider requirements. In addition, the provider may have additional requirements to make its network infrastructure secure to a level that can meet the PPVPN customer's expectations. Finally,this documentdefines a template thatmay beused to describe and analyze the security characteristics of a specific PPVPN technology. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4111"/> <seriesInfo name="DOI" value="10.17487/RFC4111"/> </reference> <reference anchor="RFC4381"> <front> <title>Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs)</title> <author fullname="M. Behringer" initials="M." surname="Behringer"/> <date month="February" year="2006"/> <abstract> <t>This document analyses the security of the BGP/MPLS IP virtual private network (VPN) architecture that is described in RFC 4364, for the benefit of service providers and VPN users.</t> <t>The analysis shows that BGP/MPLS IP VPN networks can be as secure as traditional layer-2 VPN services using Asynchronous Transfer Mode (ATM) or Frame Relay. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="4381"/> <seriesInfo name="DOI" value="10.17487/RFC4381"/> </reference> <reference anchor="RFC9099"> <front> <title>Operational Security Considerations for IPv6 Networks</title> <author fullname="É. Vyncke" surname="É. Vyncke"/> <author fullname="K. Chittimaneni" initials="K." surname="Chittimaneni"/> <author fullname="M. Kaeo" initials="M." surname="Kaeo"/> <author fullname="E. Rey" initials="E." surname="Rey"/> <date month="August" year="2021"/> <abstract> <t>Knowledge and experience on how to operate IPv4 networks securely is available, whether the operator is an Internet Service Provider (ISP) or an enterprise internal network. However, IPv6 presents some new security challenges. RFC 4942 describes security issues in the protocol, but network managers also need a more practical, operations-minded document to enumerate advantages and/or disadvantages of certain choices.</t> <t>This document analyzes the operational security issues associatedused, withseveral types of networks and proposes technical and procedural mitigation techniques. This document is only applicable to managed networks, such as enterprise networks, service provider networks, or managed residential networks.</t> </abstract> </front> <seriesInfo name="RFC" value="9099"/> <seriesInfo name="DOI" value="10.17487/RFC9099"/> </reference> <reference anchor="RFC5952"> <front> <title>A Recommendation for IPv6 Address Text Representation</title> <author fullname="S. Kawamura" initials="S." surname="Kawamura"/> <author fullname="M. Kawashima" initials="M." surname="Kawashima"/> <date month="August" year="2010"/> <abstract> <t>As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addressesone example allocation shown intext. While theFigure 31. Or: Different IPv6 addressarchitectureallocation schemes following the approach in Section2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users. This document defines a canonical textual representation format. It does not define a format for internal storage, such as within an application or database. It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and4.2 may beable to handle any legitimate RFC 4291 format. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="5952"/> <seriesInfo name="DOI" value="10.17487/RFC5952"/> </reference> </references> </references> <?line 2318?> <section anchor="sec-v6-ex"> <name>An Example of Local IPv6 Addressing Plan for Network Functions</name>used, with one example allocation shown in Figure 31. --> <t>Different IPv6 address allocation schemes following the above approach may be used, with one example allocation shown in <xref target="_figure-11"/>.</t> <figure anchor="_figure-11"><name>An Example<name>Example of S-NSSAI Embedded into an IPv6 Address</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="208" width="336" viewBox="0 0 336 208" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,80 L 8,112" fill="none" stroke="black"/> <path d="M 328,80 L 328,112" fill="none" stroke="black"/> <path d="M 8,64 L 328,64" fill="none" stroke="black"/> <path d="M 8,80 L 328,80" fill="none" stroke="black"/> <path d="M 8,112 L 328,112" fill="none" stroke="black"/> <path d="M 8,128 L 152,128" fill="none" stroke="black"/> <path d="M 224,128 L 328,128" fill="none" stroke="black"/> <polygon class="arrowhead" points="336,128 324,122.4 324,133.6" fill="black" transform="rotate(0,328,128)"/> <polygon class="arrowhead" points="336,64 324,58.4 324,69.6" fill="black" transform="rotate(0,328,64)"/> <polygon class="arrowhead" points="256,64 244,58.4 244,69.6" fill="black" transform="rotate(180,248,64)"/> <polygon class="arrowhead" points="248,64 236,58.4 236,69.6" fill="black" transform="rotate(0,240,64)"/> <polygon class="arrowhead" points="16,128 4,122.4 4,133.6" fill="black" transform="rotate(180,8,128)"/> <polygon class="arrowhead" points="16,64 4,58.4 4,69.6" fill="black" transform="rotate(180,8,64)"/> <g class="text"> <text x="128" y="36">NF-specific</text> <text x="284" y="36">Reserved</text> <text x="60" y="52">(not</text> <text x="104" y="52">slice</text> <text x="168" y="52">specific)</text> <text x="256" y="52">for</text> <text x="304" y="52">S-NSSAI</text> <text x="168" y="100">xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:ttdd:dddd</text> <text x="168" y="132">128</text> <text x="204" y="132">bits</text> <text x="20" y="164">tt</text> <text x="72" y="164">-</text> <text x="96" y="164">SST</text> <text x="124" y="164">(8</text> <text x="160" y="164">bits)</text> <text x="36" y="180">dddddd</text> <text x="72" y="180">-</text> <text x="92" y="180">SD</text> <text x="120" y="180">(24</text> <text x="160" y="180">bits)</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ NF-specific Reserved (not slice specific) for S-NSSAI <----------------------------><---------> +----+----+----+----+----+----+----+----+ |xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:ttdd:dddd| +----+----+----+----+----+----+----+----+ <------------------128 bits-------------> tt - SST (8 bits) dddddd - SD (24 bits) ]]></artwork> </artset> </figure> <t>In reference to <xref target="_figure-11"/>, the most significant 96 bits of the IPv6 address are unique to theNF,NF but do not carry any slice-specific information. The S-NSSAI information is embedded in the least significant 32 bits. The 96-bit part of the address may be structured by the provider, for example, on the geographical location or the DC identification. Refer to <xrefsection="2.1."section="2.1" sectionFormat="of" target="RFC9099"/> for a discussion on the benefits of structuring an address plan around both services and geographic locations for more structured security policies in a network.</t> <!-- [rfced] We see some differences in the terms below in text in Appendix A and Figure 32. Please review and let us know if updates are needed. 2001:db8:b:0::/96 2001:db8:b::/96 2001:db8:a:0::/96 2001:db8:a::/96 SST-01 SST=1 SST-03 SST=3 --> <t><xref target="_figure-s-nssai-deployment"/> uses the example from <xref target="_figure-11"/> to demonstrate a slicing deployment, where the entire S-NSSAI is embedded into IPv6 addresses used by NFs. Let us consider that "NF-A" has a set of tunnel termination points with unique per-slice IP addresses allocated from 2001:db8:a:0::/96, while "NF-B" uses a set of tunnel termination points with per-slice IP addresses allocated from 2001:db8:b:0::/96. This example shows two slices: "customer A eMBB" (SST-01, SD-00001) and "customer BMassive Internet of Things (MIoT)"MIoT" (SST-03, SD-00003). For "customer A eMBB" slice, the tunnel IP addresses are auto-derived as the IP addresses {2001:db8:a::100:1, 2001:db8:b::100:1}, where {:0100:0001} is used as the last two octets. "customer B MIoT" slice (SST-3, SD-00003) tunnel uses the IP addresses {2001:db8:a::300:3, 2001:db8:b::300:3} and simply adds {:0300:0003} as the last two octets. Leading zeros are not represented in the resulting IPv6 addresses as per <xref target="RFC5952"/>.</t> <figure anchor="_figure-s-nssai-deployment"> <name>Deployment Example with S-NSSAI Embedded into IPv6 Addresses</name> <artset> <artwork type="svg" align="center"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="352" width="552" viewBox="0 0 552 352" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round"> <path d="M 8,128 L 8,224" fill="none" stroke="black"/> <path d="M 48,80 L 48,128" fill="none" stroke="black"/> <path d="M 48,224 L 48,272" fill="none" stroke="black"/> <path d="M 64,128 L 64,144" fill="none" stroke="black"/> <path d="M 64,208 L 64,224" fill="none" stroke="black"/> <path d="M 128,128 L 128,144" fill="none" stroke="black"/> <path d="M 128,208 L 128,224" fill="none" stroke="black"/> <path d="M 152,96 L 152,128" fill="none" stroke="black"/> <path d="M 152,224 L 152,256" fill="none" stroke="black"/> <path d="M 176,128 L 176,144" fill="none" stroke="black"/> <path d="M 176,208 L 176,224" fill="none" stroke="black"/> <path d="M 264,128 L 264,144" fill="none" stroke="black"/> <path d="M 264,208 L 264,224" fill="none" stroke="black"/> <path d="M 296,96 L 296,128" fill="none" stroke="black"/> <path d="M 296,224 L 296,256" fill="none" stroke="black"/> <path d="M 312,128 L 312,144" fill="none" stroke="black"/> <path d="M 312,208 L 312,224" fill="none" stroke="black"/> <path d="M 352,112 L 352,144" fill="none" stroke="black"/> <path d="M 352,224 L 352,248" fill="none" stroke="black"/> <path d="M 376,128 L 376,144" fill="none" stroke="black"/> <path d="M 376,208 L 376,224" fill="none" stroke="black"/> <path d="M 424,128 L 424,144" fill="none" stroke="black"/> <path d="M 424,208 L 424,224" fill="none" stroke="black"/> <path d="M 488,128 L 488,144" fill="none" stroke="black"/> <path d="M 488,208 L 488,224" fill="none" stroke="black"/> <path d="M 504,80 L 504,128" fill="none" stroke="black"/> <path d="M 504,224 L 504,272" fill="none" stroke="black"/> <path d="M 544,128 L 544,224" fill="none" stroke="black"/> <path d="M 8,128 L 40,128" fill="none" stroke="black"/> <path d="M 128,128 L 176,128" fill="none" stroke="black"/> <path d="M 264,128 L 312,128" fill="none" stroke="black"/> <path d="M 376,128 L 424,128" fill="none" stroke="black"/> <path d="M 512,128 L 544,128" fill="none" stroke="black"/> <path d="M 56,158 L 144,158" fill="none" stroke="black"/> <path d="M 56,162 L 144,162" fill="none" stroke="black"/> <path d="M 160,158 L 280,158" fill="none" stroke="black"/> <path d="M 160,162 L 280,162" fill="none" stroke="black"/> <path d="M 296,158 L 496,158" fill="none" stroke="black"/> <path d="M 296,162 L 496,162" fill="none" stroke="black"/> <path d="M 64,176 L 128,176" fill="none" stroke="black"/> <path d="M 312,176 L 376,176" fill="none" stroke="black"/> <path d="M 56,190 L 144,190" fill="none" stroke="black"/> <path d="M 56,194 L 144,194" fill="none" stroke="black"/> <path d="M 160,190 L 280,190" fill="none" stroke="black"/> <path d="M 160,194 L 280,194" fill="none" stroke="black"/> <path d="M 296,190 L 496,190" fill="none" stroke="black"/> <path d="M 296,194 L 496,194" fill="none" stroke="black"/> <path d="M 8,224 L 40,224" fill="none" stroke="black"/> <path d="M 128,224 L 176,224" fill="none" stroke="black"/> <path d="M 264,224 L 312,224" fill="none" stroke="black"/> <path d="M 376,224 L 424,224" fill="none" stroke="black"/> <path d="M 512,224 L 544,224" fill="none" stroke="black"/> <polygon class="arrowhead" points="512,224 500,218.4 500,229.6" fill="black" transform="rotate(270,504,224)"/> <polygon class="arrowhead" points="512,128 500,122.4 500,133.6" fill="black" transform="rotate(90,504,128)"/> <polygon class="arrowhead" points="360,224 348,218.4 348,229.6" fill="black" transform="rotate(270,352,224)"/> <polygon class="arrowhead" points="360,144 348,138.4 348,149.6" fill="black" transform="rotate(90,352,144)"/> <polygon class="arrowhead" points="56,224 44,218.4 44,229.6" fill="black" transform="rotate(270,48,224)"/> <polygon class="arrowhead" points="56,128 44,122.4 44,133.6" fill="black" transform="rotate(90,48,128)"/> <circle cx="16" cy="320" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="16" cy="336" r="6" class="closeddot" fill="black"/> <circle cx="48" cy="160" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="48" cy="192" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="152" cy="160" r="6" class="closeddot" fill="black"/> <circle cx="152" cy="192" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="160" r="6" class="closeddot" fill="black"/> <circle cx="288" cy="192" r="6" class="closeddot" fill="black"/> <circle cx="504" cy="160" r="6" class="opendot" fill="white" stroke="black"/> <circle cx="504" cy="192" r="6" class="opendot" fill="white" stroke="black"/> <g class="text"> <text x="72" y="36">2001:db8:a::/96</text> <text x="164" y="36">(NF-A)</text> <text x="424" y="36">2001:db8:b::/96</text> <text x="516" y="36">(NF-B)</text> <text x="96" y="68">2001:db8:a::100:1/128</text> <text x="392" y="68">2001:db8:b::100:1/128</text> <text x="168" y="100">-</text> <text x="184" y="100">-</text> <text x="200" y="100">-</text> <text x="216" y="100">-</text> <text x="232" y="100">-</text> <text x="248" y="100">-</text> <text x="264" y="100">-</text> <text x="280" y="100">-</text> <text x="340" y="100">eMBB</text> <text x="392" y="100">(SST=1)</text> <text x="56" y="132">-</text> <text x="220" y="132">Provider</text> <text x="496" y="132">-</text> <text x="28" y="180">NF</text> <text x="148" y="180">PE</text> <text x="176" y="180">|</text> <text x="264" y="180">|</text> <text x="284" y="180">PE</text> <text x="436" y="180">L2/L3+.......+</text> <text x="524" y="180">NF</text> <text x="352" y="212">v</text> <text x="56" y="228">-</text> <text x="224" y="228">Network</text> <text x="496" y="228">-</text> <text x="168" y="260">-</text> <text x="184" y="260">-</text> <text x="200" y="260">-</text> <text x="216" y="260">-</text> <text x="232" y="260">-</text> <text x="248" y="260">-</text> <text x="264" y="260">-</text> <text x="280" y="260">-</text> <text x="324" y="260">MIoT</text> <text x="376" y="260">(SST=3)</text> <text x="96" y="292">2001:db8:a::300:3/128</text> <text x="384" y="292">2001:db8:b::300:3/128</text> <text x="52" y="324">Tunnel</text> <text x="112" y="324">(IPsec,</text> <text x="172" y="324">GTP-U,</text> <text x="224" y="324">etc.)</text> <text x="296" y="324">termination</text> <text x="368" y="324">point</text> <text x="40" y="340">SDP</text> </g> </svg> </artwork> <artwork type="ascii-art" align="center"><![CDATA[ 2001:db8:a::/96 (NF-A) 2001:db8:b::/96 (NF-B) 2001:db8:a::100:1/128 2001:db8:b::100:1/128 | | | + - - - - - - - - + eMBB (SST=1) | | | | | | +----v-+ +--+--+ Provider +---+-+ | +-----+ +-v----+ | | | | | | v | | | | | o============*================*==========================o | | NF +-------+ PE | | PE +-------+L2/L3+.......+ NF | | o============*================*==========================o | | | | | | | v | | | | +----^-+ +--+--+ Network +---+-+ ^ +-----+ +-^----+ | | | | | | + - - - - - - - - + MIoT (SST=3) | | | 2001:db8:a::300:3/128 2001:db8:b::300:3/128 o Tunnel (IPsec, GTP-U, etc.) termination point * SDP ]]></artwork> </artset> </figure> </section> <sectionanchor="ext-abbr"> <name>Acronyms and Abbreviations</name> <dl> <dt>3GPP:</dt> <dd> <t>3rd Generation Partnership Project</t> </dd> <dt>5GC:</dt> <dd> <t>5G Core</t> </dd> <dt>5QI:</dt> <dd> <t>5G QoS Indicator</t> </dd> <dt>A2A:</dt> <dd> <t>Any-to-Any</t> </dd> <dt>AC:</dt> <dd> <t>Attachment Circuit</t> </dd> <dt>CE:</dt> <dd> <t>Customer Edge</t> </dd> <dt>CIR:</dt> <dd> <t>Committed Information Rate</t> </dd> <dt>CS:</dt> <dd> <t>Customer Site</t> </dd> <dt>CN:</dt> <dd> <t>Core Network</t> </dd> <dt>CoS:</dt> <dd> <t>Class of Service</t> </dd> <dt>CP:</dt> <dd> <t>Control Plane</t> </dd> <dt>CU:</dt> <dd> <t>Centralized Unit</t> </dd> <dt>CU-CP:</dt> <dd> <t>Centralized Unit Control Plane</t> </dd> <dt>CU-UP:</dt> <dd> <t>Centralized Unit User Plane</t> </dd> <dt>DC:</dt> <dd> <t>Data Center</t> </dd> <dt>DDoS:</dt> <dd> <t>Distributed Denial of Services</t> </dd> <dt>DSCP:</dt> <dd> <t>Differentiated Services Code Point</t> </dd> <dt>eCPRI:</dt> <dd> <t>enhanced Common Public Radio Interface</t> </dd> <dt>FIB:</dt> <dd> <t>Forwarding Information Base</t> </dd> <dt>GPRS:</dt> <dd> <t>Generic Packet Radio Service</t> </dd> <dt>gNB:</dt> <dd> <t>gNodeB</t> </dd> <dt>GTP:</dt> <dd> <t>GPRS Tunneling Protocol</t> </dd> <dt>GTP-U:</dt> <dd> <t>GPRS Tunneling Protocol User plane</t> </dd> <dt>IGP:</dt> <dd> <t>Interior Gateway Protocol</t> </dd> <dt>L2VPN:</dt> <dd> <t>Layer 2 Virtual Private Network</t> </dd> <dt>L3VPN:</dt> <dd> <t>Layer 3 Virtual Private Network</t> </dd> <dt>LSP:</dt> <dd> <t>Label Switched Path</t> </dd> <dt>MIoT:</dt> <dd> <t>Massive Internet of Things</t> </dd> <dt>MPLS:</dt> <dd> <t>Multiprotocol Label Switching</t> </dd> <dt>NF:</dt> <dd> <t>Network Function</t> </dd> <dt>NS:</dt> <dd> <t>Network Slice</t> </dd> <dt>NRP:</dt> <dd> <t>Network Resource Partition</t> </dd> <dt>NSC:</dt> <dd> <t>Network Slice Controller</t> </dd> <dt>PE:</dt> <dd> <t>Provider Edge</t> </dd> <dt>PIR:</dt> <dd> <t>Peak Information Rate</t> </dd> <dt>QoS:</dt> <dd> <t>Quality of Service</t> </dd> <dt>RAN:</dt> <dd> <t>Radio Access Network</t> </dd> <dt>RIB:</dt> <dd> <t>Routing Information Base</t> </dd> <dt>RSVP:</dt> <dd> <t>Resource Reservation Protocol</t> </dd> <dt>SD:</dt> <dd> <t>Slice Differentiator</t> </dd> <dt>SDP:</dt> <dd> <t>Service Demarcation Point</t> </dd> <dt>SLA:</dt> <dd> <t>Service Level Agreement</t> </dd> <dt>SLO:</dt> <dd> <t>Service Level Objective</t> </dd> <dt>S-NSSAI:</dt> <dd> <t>Single Network Slice Selection Assistance Information</t> </dd> <dt>SST:</dt> <dd> <t>Slice/Service Type</t> </dd> <dt>SR:</dt> <dd> <t>Segment Routing</t> </dd> <dt>SRv6:</dt> <dd> <t>Segment Routing version 6</t> </dd> <dt>TC:</dt> <dd> <t>Traffic Class</t> </dd> <dt>TE:</dt> <dd> <t>Traffic Engineering</t> </dd> <dt>TN:</dt> <dd> <t>Transport Network</t> </dd> <dt>UE:</dt> <dd> <t>User Equipment</t> </dd> <dt>UP:</dt> <dd> <t>User Plane</t> </dd> <dt>UPF:</dt> <dd> <t>User Plane Function</t> </dd> <dt>URLLC:</dt> <dd> <t>Ultra Reliable Low Latency Communication</t> </dd> <dt>VLAN:</dt> <dd> <t>Virtual Local Area Network</t> </dd> <dt>VPN:</dt> <dd> <t>Virtual Private Network</t> </dd> <dt>VRF:</dt> <dd> <t>Virtual Routing and Forwarding</t> </dd> <dt>VXLAN:</dt> <dd> <t>Virtual Extensible Local Area Network</t> </dd> </dl> </section> <sectionnumbered="false" anchor="acknowledgments"> <name>Acknowledgments</name> <t>The authors would like to thankAdrian Farrel, Joel Halpern, Tarek Saad, Greg Mirsky, Rüdiger Geib, Nicklous<contact fullname="Adrian Farrel"/>, <contact fullname="Joel Halpern"/>, <contact fullname="Tarek Saad"/>, <contact fullname="Greg Mirsky"/>, <contact fullname="Rüdiger Geib"/>, <contact fullname="Nicklous D.Morris, Daniele Ceccarelli, Bo Wu, Xuesong Geng,Morris"/>, <contact fullname="Daniele Ceccarelli"/>, <contact fullname="Bo Wu"/>, <contact fullname="Xuesong Geng"/>, andDeborah Brungard<contact fullname="Deborah Brungard"/> for their review of this document and for providing valuable comments.</t> <t>Special thanks toJie Dong<contact fullname="Jie Dong"/> andAdrian Farrel<contact fullname="Adrian Farrel"/> for the detailed and careful reviews.</t> <t>Thanks toAlvaro Retana<contact fullname="Alvaro Retana"/> andMike McBride<contact fullname="Mike McBride"/> for the rtg-dir reviews,Yoshifumi Nishida<contact fullname="Yoshifumi Nishida"/> for the tsv-art review,Timothy Winters<contact fullname="Timothy Winters"/> for the int-dir review,Lars Eggert<contact fullname="Lars Eggert"/> for the genart review,Joseph Salowey<contact fullname="Joseph Salowey"/> for the secdir review, andTim Wicinski<contact fullname="Tim Wicinski"/> for the opsdir review.</t> <t>Thanks toJim Guichard<contact fullname="Jim Guichard"/> for the AD review.</t> <t>Thanks toErik Kline, Ketan Talaulikar,<contact fullname="Erik Kline"/>, <contact fullname="Ketan Talaulikar"/>, andDeb Cooley<contact fullname="Deb Cooley"/> for the IESG review.</t> </section> <section anchor="contributors" numbered="false" toc="include" removeInRFC="false"> <name>Contributors</name> <contact fullname="John Drake"><organization/><address> <postal> <city>Sunnyvale</city> <region>CA</region> <country>United States of America</country> </postal> <email>je_drake@yahoo.com</email> </address> </contact> <contact fullname="Ivan Bykov"> <organization>Ribbon Communications</organization> <address> <postal> <city>Tel Aviv</city> <country>Israel</country> </postal> <email>ivan.bykov@rbbn.com</email> </address> </contact> <contact fullname="Reza Rokui"> <organization>Ciena</organization> <address> <postal> <city>Ottawa</city> <country>Canada</country> </postal> <email>rrokui@ciena.com</email> </address> </contact> <contact fullname="Luay Jalil"> <organization>Verizon</organization> <address> <postal><city>Dallas, TX</city><city>Dallas</city><region>TX</region> <country>United States of America</country> </postal> <email>luay.jalil@verizon.com</email> </address> </contact> <contact fullname="Beny Dwi Setyawan"> <organization>XL Axiata</organization> <address> <postal> <city>Jakarta</city> <country>Indonesia</country> </postal> <email>benyds@xl.co.id</email> </address> </contact> <contact fullname="Amit Dhamija"> <organization>Rakuten</organization> <address> <postal> <city>Bangalore</city> <country>India</country> </postal> <email>amitd@arrcus.com</email> </address> </contact> <contact fullname="Mojdeh Amani"> <organization>British Telecom</organization> <address> <postal> <city>London</city> <country>United Kingdom</country> </postal> <email>mojdeh.amani@bt.com</email> </address> </contact> </section> </back> <!--##markdown-source: H4sIAAAAAAAAA+y9a3Mb17Eo+h2/Yg5ddQmEACiSkmxrO94BQVJmjkQhhGTn VKUqNQSG5FgABsEMSNGG72+//VyvmcFDUk7dvWsjjojHrFevXr363Z1Op1Gk xSR5Fe31ousknqS/xUWazaLsNrpKisds8TEaTtJRkke32SJ68Vq/zaMPeTq7 i/rLxSKZFdHl4PDt4M0wep+M7mfZJLtLk3yvEd/cLJIH6PxyOp8kU3gQ20Av 7xfxLJ9ni0J632uM4iK5yxZPr6J0dps1GvP0VSOKimz0KnpKcn47TubF/avo GD7l0HaR3Ob6a/40dT+Osuk8HhXORxxcfm6Ms9EsnsKix4v4tuikSXHbKZI4 77y468zyTjrvwHTzztF3jXx5M03zHCBSPM2hweX5+4vGbDm9SRavGmOY8qvG KJvlySxfQufFYpk0YLknjXiRxLDs62yJK95rIMjuFtlyDl++P+8N9xofkyf4 cgyL7ERvTn4eXNGbY3lDUImGyeIB/jYa8bK4z2BE+AlWE90uJxNewP9e/PaU /1bAbr3uRsPf4sXH7DEd/YYPLTLc1mScFtkCP2eLu3gm2/sq+utyls6ThdlO fGKUFgD+X9JkRp+y5azA/egt82KRxvhdMo3TyavoY25G+suv3FF3lhTl6V2n o/t4MY6uMwBYkX/JtK6T2SzJvYldABIBdOy8FgseZ/2k/rqcpPEserMcJR93 mcGbbDbOfNB8mKVFMo7+N+zxOJs6M/l1gr1XzcOZyNvsHv6Oo9NsOYrHcUrw KAEomN87WPQdLboKEDr+lLvu3mjXf8moXRdOQhkib5ZpHr3tRn1A80WyiPMy WN4nk+Q2m6UjwgNAiCSB03UNIImjcRJNYmg8XeLvI3i+HeWHMwu5t/F4kY49 yA3ncTpzADaBKUzTu2UygSnKLKbLRTqZZH8pzNg0fWgEP7yCP/dFMc9fHR5O pqYNPnHYaDToi/RmWVQem79m97PobBF/TOwkh8vZ7OkhniRVOzws4KznSBV7 02QhUNC9Tv45xq7+8hTfZ1k1hC8fAONOnz5mD2XQXqc3N0BxAX4MQPzWQTuA fNR7SB+8aV3miziZOJNIYYDuDQ7wl8XNzax6FnCIfoth0z4u0/I0+nDuYzvs u6KIH2Nv0H48A1zyzxt09ZcRtqzDrPgp+itcK5PygD8DIH/LHDQ5iyeTOG9H 7/++6xZMYJjurzjMXx641+rpnCazp+jsMQXKWjzB8mblWf39TdT7lMaFA4q/ xh/jReHD4hJpQZJ7ZPEGeh/nf/mEKNwFfC8N35umRXQGJzP9Na7Ag/jjskgc eJzCiY0n2SIJR/ZGhd6K8V/ixWK0zKtX/Tb7dZzcw+gwWHnY00VapPk9nXA5 XrvTuykN0Y1xiL/cFDyPWbaYwiAPcEk28FI3n6DdaZZ97Lx4Te+dlzIjwCK8 zW7SSWLoMEAvGj7lRTLNo958vsji0f1e0FqvySh4dUrfeDgKsHuKBkmRLHJe 7w6N390tf0PSET/t2PB0ATcEoPxDmgTPEVsRHT87Pg6BEy/ukOoq2Xtx180Z IrEApAtbC9QPnn0/7ByfdF88O6qD8PthJA8IWKN4MbqH7R0Vy0VC3F5xnyCv Jj83X7wetkKIm7k+33IrYILAH70eDDasDXnDeNI9uZvPaVHjJP9YZPNpNl5O kvxwOE9G6a0SS//jWVIATubdOJ9/+s/c/eVy/OeTo+fPDYC+6744ebYOQPwA 3F+z+I7Y1yiejWENo/sErkDq8z/w1hwBYwqEa5kn0SjOgUrhY4vkX8t0Qc3y EuBq4FMHnlo4/1+D2/G3JwS3d53r3lX3l9ffd/8+GPZ6wzrwlZ7jlhF8E/39 Pl5OokE8+piAAPCYFgDPcdRz8I8hOMwmS5oo3hXIhEfPnnefPdsFljxob4Is 36j6pL1FxEfYnmyA7ePjYzfrAB9FkPUglBNsrl53j45O3IkoNOQXOE5DuH+B ZIMY9HqZjpNJCreIWR6szl1cxcJoUa+Hb3vOl4Ic38FKnnAdR+4EKtZwl0/p uj6cJY/5IoM3j/MOMkyAqYfL+SSLx/nhIU+58wBz6s7Ht7TAy/Pz8++eHXeP eudVq9Sfore9PlyxI2DTiqeoCZ/yZNTaZmU4wJrZH3XTJElwGNoBGeEQvugc xQlTvvP+4PqyDiuRyQI4D5Y3IGDBjTtOM7hQgfLfxiPkurGt/SLyzse2tw0t ZO1AW+DZaL5Iu3hpHo6zxxlvCc3unw//PO4+++fxs6Pv//nsxT+Pno14dzqd ThTfIFUagayhsnsOoyOuAX8fR7dJTLS9uI+L6DHOQdIuFkAYRnD4bp6I3J+A sPY6mSVM2+CILgr4kN+n82iwyH6Fwxk1kTy1oC1c+nRDz+SG7oYKBLg7zPgg UKeA6C5NpDsGWD7tBzgKkAmAjKaz0WQ5xmY4JYZdbzRK8tzoJJpwqlttgPIi sd/18SukG1a7YH57f9XqNhrv7wEQIP0viZYDbRyBjIDExld2wDTtQoB0AgeO c1Udhy44Asp1j3CFDoExndF0y2PDnX8LcoxoPhQicN5mAM70AY9IzoJ+lN38 St8lAMz391XzWCRLvF+Az3qKbpbphMB0M8lGMJ0R62ImT6TvyGbwBh4e41bp AMAmPADVWdhNazDqTNPxGESfRuObCPGU0AKHDWFGa01otbMAx0RBpD23YRbI jMs2euu9gWeSZGZAdLGcjZjQN68u8lYUjxYZ7PZ0OSnSuUWNKF8CpQbETcZ3 0OMkW45hGCB/cTRK8HDlvP843i+wTLhSEru1zV8AZxiuO6KAsld8cmQ/c3c3 Pby+Qbjjt8mnNCeNl2JO4WjHoib0hTMt0mmCx2VOtMKcnsKFeysqsiibw6Nw YHB/cYsmPlBFWxS9SR5QZLwDEZ3n0xy+6QFQs9vbZAHoIPuUk+IN4JHxsuJ0 2vYHdaCD88xH2TzhmVWhOWAZ9Bp7l3jz99+BSHeo5R9/wOkcp3k8vQE5n2Q5 q04koCOkAGNyOEzl7vUB6fLFXTHjHhfxI89vDsg2RS5e5/gQL9IMT6bLrxlc AoDyHicCCu0aH6euEZUAi2YFXAECA9nnMUA+W8DZ4y4VneEJ4ACrhyNiN4bm sHI4jsVyTqIsSNmjewJ2PwUJLsXtguuypZMpZp1ZnsJ0lHoxrHPWcBbpDZwO IkM4u9sFiBb0wDi5BcaCjv7vv/+v64v+9y+en/zxR/R4nwIa230Nz3A608Na JJ8KnKEhdkhtAPkX2ZS0oB4ud+1NCehZj0axe5ay6D57jGBuEU4uVDfHCz2D sAxcIUytRL1oi7AXIgy5bQnHjplKGKWMS4Ca2XKBz0KnQDuWeZFNodscMLcC BNXIyAhzm951ktm4U2T4h/YpJNzQA6y7ep1RM+0m3bZ/kGk/AZtJYgaulch5 WrAgAfN7yCYPgo8hRAggc7i1U6IT+AiwYk38Ozjv5EgT5XD0+kQL3X2K8xze 5EwOCAYBYAC/AK+XLCFCS6TvHZoCcq8AbToxOr/8HkEGJ77ARQC0JrBRE0D/ 2eipBZgIxCi6iXNgj/6WDQ9z3K4l3ZKIUyPsP1/eAkqlODfYR8T4yZPFdp/e vTNXJ9K7dzkemP8XXlEc5w93wnGtOqXX+yveifIvq0aFAM+v6s2sfbxL/Q3P BtH7JyChJ/ipW/v0ChtE5unnnS58t+7pVemL2qcf6L/gC3j6wF34gf35IIDJ QfUvBw0at6/44k6J3g4UT92f/BbcRTREVDuKyl0oqMMuuMVxZLvw2/FkD4Jl 2c9+C+riQFaKD+EbOEL8WDinFf50wA/5XayuLqKDbrd7EPXPFVYHcAb9Lgby 2wE8vQq7CGfhjBrOQpZUmsVXgEVVFyHKhTvidfHFqIWnuPH7q+gbn9ayTPfn vRrqHP0/dcc0GiI7ku/BRUHfdoBU383+vMcs5N4fa1heuUiD/sYJyMxPzGsx WXPJ01kyBaZI5KksZYbsbIBcLjwJnHuMKlU0OeFxz6MToqLPkU5fAKO0wNMA 791rnHiBGhZVL9sxX2TuQuB98TTnOzoqFundHfGDwK4G8JGZI7MDjAzc7j8B 5Q4Z5OAp7H0+iUfCYDpzcwU6vKtTehaIARDrMTMUMekZq7pt0z2zpHuY2Mhu 9BbWKhIUXmjMZ+WGCUPxlEBIXEr1nJtJ9w5u3an0hH2rgBQjD4WiBO8PXF+w +yBFtSNuQxzVf152zrq+2ZjH6RAP0oF+lZU3uwUrVLYd4DRLIkIqwhSYg9V0 m6lOEpKJol6eyx0Kkplo0eHr5rBzNRz2LlsEbxq3odyqoNvvvxs1MEwjOk1G MaoopSFzSrOsiPD+RkayyFggMSeKmdc2zl352BHwMsmneZYnqh8Wtits3OAW iF4KZ3gEmiKrWbDUxoAwPPYi1515Ez/BgTjWNydt4Krl/XPgWwbAqjC7auGh ++8xLcwhlvnGFFURIA4tmEWMeSP27uHpDshJe92I2W/8Aj53ZPXAQU9gL1Ba BBYe8UZbRIA099k4t5thVj1fLhBcKGp/mE3Sj4k5rMpriVQB03vEuRbZCJAE mM9klrNQzEAp4Z31VSB5pajUGKwhCISBZikldcLWSoTdRFkWwXlyNIPmUUs3 PPo5XRTLeAIMQ/qAkpIR3sk1ooUwADL4/OXL57AXAPtDgxcna9qeuG1PqK0u BnZV+FPcOWI9oYs8QULA1Kt5DEcMpKnO3SImoUrFB3OeZfWGyTkf3+GyBuc5 7ErzpAUPxot8TQci31Rx9CyGNp9DJ/E8RsscnZoZbNTh1NglgCqiKmzMKnw6 2NIR7dwwEfXK77//QCIuMu6AKh3ahT/+aOsP/8ryDuCtfGPOcocOakcwmlvl +BDOTZrq9Do6PaF8dNRCpFTM8ynftcIF9Y4pU7mr6wEJw7KE6NsuXYf2MhR8 EpJ7k04QRHCmjfIIeshLt0ij0ZvAgV3e3QdnwrntX7wunSlLM2+Xs3GMLVQh gxI/7a6oUoEyqj0oUDrBcNhDigr3MROgG1hAdNrni2ucJfzEaBKnU/yZbQ1I SGHQIlvAO5C+41maTz1FhivOo1R+HcNMFrBN0cfkKbrLALNF/POYgkyRBf7G d0hPR6SxJdTy+YuE1FsTELngSU/HBXMYp5OnTvwAKBjDddIGtIa9fuowf4QL RZVBivd6GSLxJM88kBBXRnMV/bBq9uheB34JgcICH+6qKiGZnXAxznkUtv0C 9TCsH0nxK6GPc6VVxD4YadrVZhlkwNMJwu1yMuZLBGcbXLV0Gs1xxDvzBm2q y5moZMT8TUfkG2AReTZkR/IAY3gE4EimeZ1ap6x+Ie4Cl7OnEtYeK41myEtg zyRGe7qhm2XhqJKyCYjrwmahImRpAdrMk4T3iy9JAALscQ7bBafxVaOhQ75q vIp6wC3A5Y5HEm86IgZAUmbMcCDJJSKGAwWmVdEbOwx/ySmgjacEUO1pg6GA ui7ZCrowPSJPMkGkAoTLI1FzeSoQ1OKECkvDUJZMC9P4I2yc7IEPT9pJB0rE pxCo7GBM2Jl54dPDytILwwvcXQEdPY2ad1envDz4mVbYfPG63yLzjM8Idd3+ SZ8jWJmkSCNgcfP7p5wuPzohD3KZkoACu47tzd1UsY14dBeqxkK08UeH9Z1/ ipGm0HENmbRF4urh5nKB69h4l6LkhC0HMHCCvDB8NYDr9Qz5yD6JblHzDJaO 1C7kBPpoKoiaPw/6LeIk8fJHbvM+ywurXqxUqMHTwI3JRJRrgP02d1Wf73Dc wcuS6tC7W9rliz/NmbtC7nLyxKRcKMrNEvX10dT3PViAWPAQw4e/4YEErIVB jFTzt2zYwouJL3uY5F5Zw74XNWFJ4Q/JXotHpttgr7pN2CD2CBKZD5F4Mikk 1wmib0gCPgldR+6ZjhI5Bqeyu8pglsRVl4f5/XfopYMNhWpWmQ/QxHonmndo U9INAAf0DZsPQMz/5htWBdTbNPhhNl8wZSaRxlq5SkwzYPKrr2y2pKuywt5i oa/GW5J8Ub0gvJIoDpztQPL8+6t/LbMCFvQjaYqjfDnHjktGSTkVODOVrfpX 9BFdKrApolgvtzKyw2pGz7vPu+Xx23aiDmKzF5Ple8YgDI0Kx85VuTuvRJOg egDUPyNTOctmHWeEsXTf9VaOMDUPEhhYSQEzeK+Lo4dq5iqYyZezx3b5tkCR ikfZggkm4Uqpu5xREIVqb1I5ax14/VfeduXbbpazV5doQomhyShpa5/T+Ilg Drw9cV3Abc2yCfY28j3CsC9n4iwRd6NL2oNbUteQ7TlP7vAB1JjgWpazFGX0 ttOeEHackjkSeqLrl4xIyJslfEug/IH6PuCm8AZMRwVZj64ujMBmGArDXtL6 2Tbs2ITpVlBgCWtJHanqjWxA4qjBFwUQJvjqF4Cc3LZovO2ADKn0Hw7lpZAr M1+Bp9yqOe5AzBYv8crAU7FI5nR/FczwuNyNbyCP8Tgt5+RUsEgSy5mIJuJV dNZv4xQZsO708aa2TgvVhI37R4630liZer4hRHytZbTKsBIqcyteqt9tiMqb PwEpRWoCE/WIou30oKH67e1GWEWNknZ67QsbPGx+zL4eogZrzLebEj7bWF1d uFr38oY4uu+Dq4uVHaGkJg8+6AjOesL1VXywj4dLf6j6gNPxOC0Zl5wa4FyI nYKxkD40yntAlqrTePTxJpslNBM0ANGBW1GDAwsx+kvfHFi4RJ6hAhrs44P7 kfm7ilaDcxmY3q1e/6If4fFup+v9f13/1Pu+9/9VyQJiPq4qlxv0vunxYO5f ufc1cy/jsY/cYoSSD7495kjNMMDlCYNfbTI/Q+fyeZaTmLvG9oJc2Wc5hihj V8z+KPu/3RNnYO+caRLPHH8HvuRZtoR2E7ZkWz04fdcVGU86GSUerTcSo6NP QKMEGr3ppiIt67Jo4DPWz0v85Gq9XDqyAmDdqnnERtCkmDlNiIXJgzmpBivQ PyWf7mMQwFhL8g3sQsW0DJDNGI1GxWM1rKnPCurtKIolnzFlM5pqY1XPfDhX vSCvYrRIYmI02BEPewLREQW+NM8mor61zh6kYEAfKvIpKbI5eq+Q0EXyIIrA rKpXETGlPea4RGYFjErvEJADnRPM7yRX4oX79uodC8OzGN314hxm2yIxUsRb 8oQQNTMzk7KOaA+v4ASVfHvs74N758wf/fIVzd7DzX+N1z+wecZzUlVkS9jX xeRJTCSO1wb0qgz6SQV7LttW8swC2OT+BsXh5jCSG7ZYvaPNz6geJuVsKjth friPkTtKFsjhjGARjjyiHlyO5WGeLKgLBLXPdxv4Cv5uIhXOSWHZDjUz0R7w cNTfniMQxzJEWufjKbYuESQDPzgWJKwG6Ha5IJVLMolvsgVHNc3INFo/5TRv BLJ2nZaBWHL2issc6jZ2dIyVBBr3JByVJHzHfBSK9u9dWlbvKiU0AQDJ5zJp N+6WsOuwgITODZzaDMOQfquCrT0AuOee3g1kBlerRF5g3nl51WA1CqDVJJ19 NDYUGjV5ALotIbqeafUUDjjI6peiWgOx5DFejKufuoCnEBK1CzdHQpF5nKBr Jk8YcF8M0HbaKr9Zr0Q9st/hg//pWj48ickVRY2xSO8oGInJMXpcc9cYsLIk 84U4MptNAUkNkGW6nJJfAj3NEEMPgxSEWFgR6tfk4PEQ0JNIVHCppPwunE6X TDs5a1PvUtwAfQQF0aVYlRHIaLd4vMcbOcPTkpsfAYHgpAZrx8O3GLPmLIf9 yW+fSMCbgIh1B8eGHZHvbMgFbqwhUrnjdKCie1thBgTBbs6I1P43vnkNZ3UD jC2FtaCqbJqO8b3odSw4tutKWlNP2q2ogawNUG9CXBbJb8ndk5WGWbcgy+OD iiI8OTQoD0T82Ey1FMbeEykBzB0ptOHYm9QJW5WseoKCo2INq82fry/yVqPO vvq3bGj0X3ilNs6dHWu+P4el/3KfsJJ6ItrpfHkjVmv2uXXWgotMZmiAGnPY gwOR0X3G2tvK6+E6UcbujKwZck845g24AkkrAVdHTLKw0U2waUjb8+M1ek0y emSEh3ebxHNH4WLcmwGgxnbwABRQzc6VHo/WwS54OR555Ze2ooAvT0PgvGp/ KP8qkznjW7L8qv3B/tgoiylW/KlTBlT9esDikQsYFbscqFi5XAWlciuVs4zL otNRxWvl/zVui57AJrKv6eigtJYDpyPvV+5IxULxDFyp96LnOej/GP7KHa2u LlZdeK0cD0YezvFitC6M5lfPlbF6RlF5TP/H6hl9NRgFr213rdk/bzk/fD2E rBz4s17c1Q+lwUskJvj9R1+qF/qmsn2JMBK/YM4CYTJpIYPTs9bFsmR5L9S8 4hDzHLjiGXOePt0NjEO+iZVuB2MEQ1nAn2uzP2wJcR/lMJl3M5QGVRS/QEHK tcU+CRmO4vGY7ly4wOCSTCYaX8NKYjEqgsQJF6KJRco5vBVEQFXR+8ZPmCCa dXEUYAXEIIkOF3Ds2p4lxNFf02/IHVgHUuPucjmAXua5ekL0z1nxn8OIKjOI K0N1SNaFOKWh6oJ99ij4J4bmrtmYdOQg4yToxFllOVXxwLsl1NJ2VQMNGz1g 3NLEBjTBi4+CaJbwuHh2iGed7kA5nEx4FPVcuPRDGJpXFz9fkj1uVqDvjiX7 NgS02b/CRy7imwUwihwJjnsLM/FsBr3BZd5Sc4jraoQQNHf/PWmDmGOxy0KW xfBfyTjEWXQnY+IjOIvGyB6SZQ7rlNUGEriyWt4uE9/tQ1z0RiP0IdTdLlnB 5aH5zPhbVXZPzhSwSWg1gLmoU1/gp0dRIsipzrIphlBR4EhFKBRGQplAqHhE Q7viXv88V6sdWV4s2RB84IPYljPI5/EWTtQj8JE5y3bkxqKuFRyLg2YZYYWt PC8CvvK+qAZfSHASJsWA7fmAzghpzllnzNdnH9jj4ANQh2hA7q6KnVHzw+Ci hVyb7qX1znYMZa4XSpucdKBfPIQ09RvEpI4+btx3dAPJ68P+zsPYI8kj3GTS yiCG6pFsN2ruQt1Xu/ywQRiVKO/jB+vlgGotY79KWK2WzW7Ru924aAlvW54w qm5phsBpkB/PuXVx0IlyONIsQ0kI2HHkahQvUcKI1dUPDQ9IadVkbEOdoAXH jNkApPt4Pk9muVHmTZ5cRxEEZZEnk1s+DgYA6rojnTqhgdhEATs4L7kM3VHY NaJULnpkVdjwqYXWZntTJ0KXvLxcxOuf7/2HGkd5q+rOqomvu3kyG0L2aRN3 S5uVG5WTbrkaf9/zqgwFEhcqmUmXvL+sUWDsTZIQvjJUznMlymYSTBtzmjQj qxsZKQ47ZkMD/ohw48MfNYUYybEX2qBfn7Q0mM/2hXQWSU5vlrG6bt1KAkbl xbPQThqwfQdV3Fv4DLGqjshRyaHil254lfC3xOhE6xq5Mo5a39bOMOiJhIT1 j9Q1ktCmgFd3oXBQbiRWK3r6z6VXaSzbyFtZr+8u0Q/IMo2u31/TSMNfth/p s9b0GdCDrpzTvuU+8QtQtXqYqkafhbCeFOEdJZUlHCNhQLTqhYVfSA1IGSfy QjLs4OUvNAK5lsF5LnQC+F+5/pFFNbEBb3pXKBekytjl5CgIEMH7gK5Sp7dK Hoi7Z1rgBfIrU0DW8M48Q/9ajr9FP3ucULGErid5BzmBIfvHGLWZPPPwMmoO rx9eapjCd99/9xI9e4XE3lOIyhJuvEfgFmfoVIZxFjpHIYp5cK8KIPy4Izfc RqeOkwEmihKRACN0/V7YI/7+jF28l2lOitjm9VkOfAtGhaEfeNvchzneoZjQ o5p7Mbcf3Itpbgk4wQ0hA8t344L8CHNSf2IIMPAJZKrR6HsT0LzWjxO3mW90 jx0RWe0VczfIT6+n9nBxq/GhQ1tBiIh/lxQkdhsopfkmt/GBVb5yJizj6NkN R7XYL0bs7AjiQEk1xcLAfEbCgMOAkfBUWn+RefdqyTt4Qyh4qT93Ay8H7CLF MinAL5wySzADI8GQO+XgXPWzDxwuZZDGmb46eZXkX0WIChE2Vk4rjmQMlVPl CM/Iwmu4nF4/96WMTawZ9OpwZ9txZYN/G1dWFtZYjjHfV/l4iRQ3qGfexHHX nII4OAfKv+29tby6kKG9wDjj7Ceqvcn12mHllHLTSUI10nkuiSrwXBHvH1AU 011zREa4tOWzXhpjZmfmCkyx58r0GsSgR7wDclHmW42Srr6Zpi22lRvezvGG d4UVukxIkEU8xQVBM7Nx1kLt0k4ShTkWLWcXT6FoFRqV/0oM5Tr2okJHeuA3 KnNMnjLXsFleoxre8O3sbmx8nlblRq6CW/lDE7gvTOJ2I+lP1SN91prqoOcx gSH0qhrpl4Nz5+PnoVH5ETyCPrkrGWz+f4ihlZ5v1TOzMKaOgKkTlaA3Xu1u rswX+oCPN2f9CrxZGddG9XA8cHD0IHr9SwWGlv0ct8DQSm/HTWuqwkIXemsx FGWR7TB0S7T2PiLuOUT+s9CaqL6P06KA8sWcF88C2SYPhZvBOuEGdfNoryD/ +UjtFhXBQzYMUNgbnI8wnsR30k0pIbXkd+BMQXgGYczqdK3MnQETxLp75tOr eBXVNvNdRxwnTEpVyYmokon/UtWxKFNEUAj4OXgOpbUKzqzEjJmQyBHnXa3Q xwhwmiF/jRNz2eu5ThT1gdkkxUSatJLDXv/QZ/IcPtSLoCxKJg7XTu8lFFNZ zjI5yAxhSmgMDWEfqkmFxLSWj8vVSQY16H2Pxc/F0iAPSuyrWcDISaUELUnu 4sBuka7YO7Ii90A2z+PHO05BEBtM6owYkwyISw1mxWPl860wYZgnfcjCrGir Wr+9mwTQf7HXFmbRxFbkoQ+ky2FX+ExxPxT0MJksVTFOwNkDirmH7CCnYiFM qtASKlI5qr+eTttIsU8d45DjmTFQ/MBzrP40b8htyU1diC40b3pXmBWux7Es HiBM4GZqrVa8JvI7BQC+A1ZzAqzpz39HNcj5z5eVHaEgJ2CDZ7ULWMuZ40FD yheb5YbXSJx1HY+u/sae6OvFoN9IYhIyNGpqPFZNEBRNYJgmysDsl3UZ+HY5 PBQTFqMpAH1aLx0fso9JMmersmx8njLCUEYMpFMwL7LvEr3t3GdToj2auE5Q kZTgAJx2iJIMXOuM7bQwii4NHeYZdGGGgdRgEuwpfJJPbA1jaRT9r4rUKEk8 ebdaVp5JwNBcg2zFysYHEQHP9J6o9jTjXLIzAgdZNMh53/cLQtR7SJNHuVuI FvIlhGa1c45/Osdkz+RL6Dd2U0J7vufsBiBXg9yZNmQJr6O7SXYDR8KmRNRg qJJBmsK6nUAsdmpsxt2P3bhb8oRuqbPkb1k2xWPjhgtSJJwOeJ9M5uRap2Q+ tHaYhJq1ORBtAsonPtyxXGhmQ0xCSl1eYE5xEiPqTWpnWHOfOU5n3iFTcdjY OiQ/1fPutxW+5Ox2YH3iKEkC47LciG0GvYMDvs+5xQVYWxM3YviuVRV77mcN CHcsdzZX8k5IXgZr3oWeCZxiuCdCZEODPe/q92Ugayf+qPk8hp0SH33xcLwC cpBHVAgpM4kcnBSpTCcwIo44zStm8GasCUvswlON/Tb+3U6Oek7Yr4yB+Ftw 0hGefp1PBp6l+SSl0JAsgsUgZ2piAmd0X2hOSoMtJa9HsyY3L8SrRqOkwHxX QZIpEUJtoou2f7MsEkoqTZegjzp9410RNa+GfWLy1InHSzOR1B6+Gu1a6Zij 2/Nj7qeyKKfzxJSUXSfpA8mqdQDAPXoX7pHrcSRbFmRREHBQ1GhM7uYJI4nn bCIMne/Q0o7OxeWhAo9gZcaPBvYkcKKRHoBFuXwr3gzqQezNyDo+E/EakaGX nH2sA4LlGTAgVlf33kS4bEhz5KfM9acyTe/uC3aX8MPFEU4x+3rcZ1Q7piBB xwSrVdRC8w5wD40K4/RT1Ou+rMjUV3LJrXp1jRTarX+ovv0qUiJW58a4oQMQ +UmTgFqGte6IXujg7sNwSOmuHXQ9Ob27cwcrCYERShaVLa9VHTijHgTH8aDT KmmHvAlyD56+sGmpemvTFFYVPbAOyLz210OhsofSa13cs9dDt2apa0Hg9rDC k7jeY7xifJm86aOkUTyo/dRRK7w/i5VPgdHWrzk9h/2qn8s9+KvwN7Lm59VX XQVhQkUq48rv8Nv9Soyowoy1PtD/hh6qELAaKR/cHg68ta7X2Ya/rUTLHCrz 7TsvNGJVemolSsmHcgeqKDVqZlfjf6ATosEdx3jzUK+vatmg65V68V9dwL8/ cCfso49JhtdmGY5cH/0D8iNdyfdVc3CGLM3BW0VU1s2GYPBhfxA8pR1UavvL aOT+ZprIDCo0/+s7ME1CA8huuNTZ7L1v2MvaV00HjOAe44HYu3X77V8NO1zw qk+O3ll5SnAV6lQTvlm0J674/dWGEIGaEg6OnTaQKUHWo8oIeW5Eo/08EA6G yxtg5l1O17rkXg2Hby9alsFz0v6KtPuCebxdUwDXhSSzN1BeCr/FZL+uAsfE LCNvy8CpUYAHOnfUpqbTdEJxxv3zDnttYAZqX8rSINMX3WM/wab6E3B66iOa 6TFl/7IZ7VFGeF4KdatQAeCmeGmF/L0MNTx/bIhUkGCEcWJ8Pll0pZw57LEt 7lZYv9dLuzeUtHvnnP/OKM2xWyc1kAl+8L3mM6cFpxNSvxTNKqgDa4KlG1Wr gXjN4hsmM8rFecr3sFbVqqvJN2MMZIwKNYQzLG7DggJsbT7SasFbgycucl9n 2DL+WuukVpNjiNVg3bKcj0C+9nXzlfuJ+obBeUXlo4qlGYGW/YVmyL25kdIv uydhlliQBktWLxW2KxQizngixdqyGixh86C6ft/xzvqkSQw+HEpFoM5tLLVW 1BVxJ0BvGIgxcCBWJk95a21uFLxDqvVZoglAGm4hD6LOjm7Q8cqLOVeV61Do ZiVHQ0WncXmWt9GaEI/HsO95kh/mRHTh29PXA+BmlkU2y6ZI2rW8ZG/Yiq6o sjbQ3GLURQdDpBrlvNayP43QT7za2OLWYszrrQbrQE/6cdruLs18atOTGqBp BLSjPLV7k4rzJmbhxTPMffAxR/9Pisl3s2tLj2g8gFtRN0Q9Q19+z4Rxjcde Giw1daO5IzzlYyzM/X96V6890x9ljBtc5kpivPWRsry6BgJSuUVCphFKY042 NskMTFbcV/amfs7xe7FUf/F8zNRfFy4qODKUs8HZ+gaBQeLy1d3NKpaaJjQd kRBwkOsADJDw3qafKAgPTYUNUhzFZItSHHCVzblkgLOB++asKj9ABLmytsBb Sr1GjESrzCfQO59TmN2knacY8/VEcsTLhKqDptaOSfTZ68fxsLWTUbakiSop VSpeJbG/G4VFQaJ6MdCRrOmrhse6i4Bd3TT8ipqGknUUcS5oxNfDs7f4XLOk ZC5VMYlIggpfP64Cw1WLRy1rXSpe+2Fv+2WmvFYPU/rhS5qGQsuqzvMlZPcP SmHRD3WeNqF87sZ485vuETU9+v64+6wL/z884ej47jO/9IzGmZMM2z3on6/L qHdg0qPVjGrgQb7+R8+eGSBVjBoFqRHWeBW56gA/5j/a1NTN7leTZ638qnjs C0S8sKm78Xg1uchSEumeqzzXd++Syjw/116WHrn3Bs7tsUbSA8lIi7qUzWiV FdzkNxaKpCzBH1zX2WQ6MfbuTBKfsYlm3Tia+eQVdfUnEHbg26tXjZ66VZXy YokAgt2KVVxHtWlUmtyNpOvRvChtNwoRzY3JDIXdauH2BV74xjtFmQ+bRcWx Qvq8GV6AS4w9VVbNmdctp1IxKzuf3ePExppl/XSRxeMbKj+RvD09bfn5tjTW OZ1SzWmu0QaCTuKwIApthJLkWMtNhF86BT4koayzbwlA+jjASTJkGUPPDRpm mSkHGj2VVDZ+aipEhdt0kRc0PbrxaBOpc1MH/a3uTxkDDA8jeVdF8FOAdbEy qrilOHGwNWU3qepmy6bbsX4YDH2ZzqMmAcJHaHBHtJHYi3BTgygT5ImkNzcF HhVj4jxAnB4IZBgJc9EkdqHLU6qJWgzevUS8Y2+fuD6G2Rz5DxPoCUjBJMX8 O9Gb7BEYOvY1w4LIy5kWhWl+uH7zpt/StGoKDSt/2tXbWq9t/JMbNcLd1Wk5 DtuZY7P/ofMBU8RzdiMgRVqhT4oQ0uH4NcVsUgpgFj4rTxGtb3AhXdAOwKGQ FVAEvzt50RwsAOyUL4IW4GHklWKkjOjQH3tusukNZatCC6m7x+x0KZ4o0/ST JhNLxkHGKWBys5HkWe9qQUNVNSjNaYcZlRwiIQTOJIuk+kaStgxLO9Ufp6bl lH1ommVS3KzmJXN7mnk9tdyJ2wTW5Pkxl/pfAGLyxhrFEylGgnkX205IvdAY c+A4XotA+Db68cfoijnk6uiKnV9lfsq8TKkzwp/aV6Bc32pCB6UeVF1/dVI2 PFW1hzHhUW1F/BkdI2M/0JeqhuFM/NNZyIHpCc6KOIo7JoNt5xBF3hzcRdVD rO4hDw7H28Ph2M6B0g0jJPplSLjA6A9KG3YQ9d5+LUh4TaqtfcHLfyhgJD8D llF9D7VJrZ2H/Nbb4XQjYEpfKFN6RE5h4pVHh7upG9FShnIN17nOLyMwClU8 AYuiqEZJYF35hO3loOaJFZySf9JduFrbx8GaPty/VU84hs+atZi+SmTvIGhd sTtlbcA683DwNYf7JJOJscd5Sy4PV2E+r5zBGtTWn6/1bnYphB1mqz40gbn0 wbSSN9Q1lK7p48Afde1EDJnpvXkjX5lRXrzuE/WpiB7bbjG7TGQtROxXFiJ0 Q/wbIFLx0lHwZNGwq0q8/gyIVD23hoRVjLHuANdOZYvoO+mjjgKXh9hI8sqr CcnwSyXDVwEZPtqNDMPQV47UCLz0iMIgKnxslS0GERmYUXL8zKkS3QR7uYWG 2YISSLMW2OnsBiOMMWkCxS+01Z72AN1klOXSTU8d/FzycMXMbsB8I9WKTW5q 7MQJNuDkwpPkjlZis8oCk6mqjrAKKFnIUEYWmU94ZL+kq2agvrKBOSj3pvPO fXaL1l4UYilWAX3GjXe44ZNz9oSdU2JZh80vMlvK1YlOJlAGhXZNPAcJ51UZ Tp14jjzZ3oW5KkSDc7VGFyjXW85ZigEMbdycpxBytAAUiONKCSUNTjobZYu5 5OEmT9RNShQXV7oNX6eTSqY9J+eDyQNBIjfnJJp4GYzI6brT/6APks84TYWo J1vyQklXXJwdYbc/4O23Nj1bGyemZH7GaVvFQte0kUfnR+3o4qgzon+XbeCA 2W0dJAIbjw+geUierIiLPu0qUIK4Gy/GIvNhUnvn8O7RrmhudU1LvaTs4ZJj XS12nH+LDoUJbUF/Cs7V7wRLCrq+STAs0NenqVWpUp327R9/kFbA6D40DF83 raa+z62ioefenIVpPshj+KIj5TzhHeyhzVlWZHeczZh34zELVHKmqqyHdTlS 1aH2iW8/DI5aXUDmTwVh2JSCoix586eD6RSh47E/8zybiM2uMmIoJiGuSQs4 bgUTd81jzuEwwn2T53jcMpk6nBNlQps8eGok2XI+jiU0NJWCbhocZtfwylNU KHRaniONTQTZpP3gmt6scwDK8qNTidgqE1HbRRBlnC/rL6zaIp5mbmIOTasO D2CdZ8ZXcjnHSsr/IfXKuNqWFHLFvcLUdN3ICbITW6yAWbS84SxuNR+71UAR 8OZZTpExrDSxDhFH7Nfz++9Xr7tHR+jXI+fNSfOCLRytVnM4fN9hh59ZJuTy zFFoYljO8KzV0mqodKCpeAPAhgOwJk/diP1hXrzG3rljo4SxSGAKLCAaY8JF exZdUQ1rRZ95mO3jUKNsA9v1tUZ1E95DdTzbmh62e1X0sIk/q+lhW5WDKBvc x6WHFR0dR+0BNMhIIubYmQke0OOrrzsHd2EbIPdvhYOrCPsQggEJsg+HD18P DqXHN6h/ygbejaAqQa6uRb2cUW6yE9rC6cVq6/4Bd7Ium5vC9QPxGKH/Of9B D/9Nzv/wp971+Rn3YF9N/trJyi4/O4//DwX5r0RBPmOML1/X18UQcUXZuDuu IcHHkGOzbxUYcmwxhBHkuAJDvmQOXw4H5/WZVOvzX+t6GLL4sIF8Vznq7PYq 6cq+VV0Z3x/IUIe6C+fSWxcTEVqI5xmWmbJ2WpN+nd2iWfOBfDpri0y0LAnc pZA8eFDD7En24ihfdAAoOCemeHSWzMOLxGQhuofVTThhMzqC8nRNNT1VClC9 4LzQ6jVctYE8K2hFlAgRizQWLEKRjd5zmw3Ug0Z5xU64WL0Kq4mFT4JcFT+x uGMCgtMZl7kFiIEsvYij0dNowiqxPEk+OnZmePMQU5og6Es0Uya/RW0R8Wtn fHYOlVQY0LIDk+uQuGe8l7z5hrJpVZF0R8OBXRglxz0ssDNBr5TOv7Jcc8na KhkVpcvJKK7OT9GbY0zSyE7Hz1++fM55biiT/4nzywn9ojtsyz5V13t6pbb8 9/cm16W7VgSjAeEtI6TurLg4i4+w9CMZJZ/YvUtKZ1EdbK3IZfuzzuJSnSOW TrRSgVOlwO1XnT4WwGpSl05HXes31Sc5X+tCcAV4p5JE0h9cX6LX7jm+QZhp KW/S9ZkBWfzvMvwP/aznFryKvzI3On+x9apGl3wEptkBOYe6DyCWi5cV5nFp cwpO6as82CLJl5MilxLbDkfOWdTvk5iyccYYJTH6mBTq0MPFuEbxHJqjSudw nNgP6uEzy7BeBZY+ITIQDt4SqkUOMROgCZRJaJFOQzd+wJS/ZUPRj8kEuLgY qvHmkzj1Um7AoUDXQXUUi1w7hJc+gc+BUwFNiJ6TSYC8YkSzZjAas51hCXSM TVok9wk8/ZBEE6ChXvkaqhFrjgW8DkwqqMEifUCChw6txvn758GboWaJfv7t S6yQbj4c//HHun5+weRJTke/DFtu1MxJ94gTudgT3/K6k2i820n8gF7y8OQ5 gCZ/5XNtnSjCruk3jVk4PoLO2qXnjG+tqQt9ukjHlEOjz75PEvpwjpiKUXs4 XtQcnJ52aGgFBCz9pGoAmgOl2KYs0/Lw85NjSj8zG69poMA7/1QkkmwG96FJ SbRMmu6Tly8cDEIKu2QtP030lsxHiBG4pDDDCBx8QLLbyZNP4Z2EEs8rEkow cb4A2HTuFozTGgJhdceFRB355BY1l9k0KdIpXd3kZLgfj6dpjk662nofyeC+ FLiV5sg4ab3B/W4k6XVTU4NHI9mE/3DiX6QD9CN9TMccVlSgE5fxGpSDQ/TM dfrz2peyHNscZFqKF6aAzEcy7mS3t25wj67Bi+ALa5w4WXbtXgKs7rMxE1ct MwJAnwEBQ6vPHQY3CQ+GxQpJTUvJnuCjHh3gIwQqZul46hUeua2xiXMCHs0m kG/jb9qNFhyeYHCrk+pcnVOlfCI6y4oR0TCDNK/gwkin02SMJiBEv0WG/suU 6mUaLz7yVYIMBP3UARjdxGKxk3noUWMlOXJrmJnFU3tLr4RyvFspEcxKsEfp rUW1O2ANibEbjZaYLZmtMbAgBjhXxaLILMVzukR0TvcpcGsYZEoXH+YrW2Lq m8P8Pp5jChwTNcrGsbaHYlwn1BRCZbugUwbVMf2ax/JN+2QV9Qa9LjRhEOeN azPOlw6jmawT4auoDc30nuWMktZX180jXe6T3ba13pQNHXR64yz4n9MNZYJj ItXP4kW+mUwRg4Y5SPG2tMFLig8cwgSkHsPBahMztU2dGPFov7oeYH5wInJ7 aGvFb/Y8O2DIIrfalLVrpg727JRdQSKEQsi8mYGpS8c+zsTkk1KVMTJwAGtT EIELi+nm2jdGfwNXJQkHY7xzBUAudreI42HOmR27cRssJtL0NoCN7tcl+eF/ 52Mv2lajnh6xto/gnVvOe4Vl5nwLmM3rTmEYFBphaSF2RiQSQ/go3lN4fndc XUlFHQN3URbRTF3cCW/foROHSZYy7D3l/LEx3y2lrk0g4Sv3CgA8pcdH64bg 6tbAJiwX1eRNcTkoy7wsUjbp4yZgjAM6TnAoKdXlKiYJyBkfc75xpRO+lHLn VsLeAC53Uh9+BHC/XdrS7DpjdIWXPmSqMZNtlNSQsIJQHk/MXhiSQx77nASA nxhhespJFo/N5Q4j4BXI3vbx+IEFovfnHJGborAvmGakKV2y5QzYASYW+Qw6 4luTpugEIzsDe1MklxtAczwk5/23AwAG7Ph48uQUwZibeiLDRAymlfW1j4/X Ju/q7vTy2r6Kyq9ToU4VPylvzTqpV1VKs8rXgXncKG4pEQyPv73n7ytKx71q dDoR/Leif+m/VWTf1/63ct42oivs8E8/mCXs4H+My/nxT41oaL5aeV0EvoX+ R+dRmMU3NbOAvwNnTv5Hfxa22O8q7CLyu6j+cdX4858j+M8q6X/MOCaV/+qn 4KP8FW0tg/OLZsHgrIbFpi4UFt/UzGKHHTmumcXalzeLMnZuRM0Sdjq97n5G Imu7+AonNbKz2P4lj3td7O9GqPb54vsTZnYRcn3rypnIbDSt24+NvJ87Edfs +UkdZSEHSOoY6te2tSFAmAbBl5EbRGoNfZR99p4pBa36TJ2tYSy8Z29C2V2Q 3g9FbmOtrLjbDA33uEYPPxCezy/7V8VScpZerjKlLm3ED9pk3Zxsw9RWlEz9 dEG5aXlOHN3Ms+OXdD+9r84DreoEnBm7aXLlWScJqmi1VJnbZodZqYE1WQDr +URyTkd7x1TWpdTpC1b8ceTkLafOFmXU0bcvbSp4+OLl0Ql+QZoy1PRLbCeq 0aPoJ3iOpPZTEW3OJFcjq8pRrIdfO5LB0erKS66absbRk+PODXCKw87VcNi7 zK2SDlv7frWsG5cn1UkLQ5dR6yNMq1Ujq2sqdDNkMwlx6k7gmvX2Q9Ys+UQq EtevNy/1ir1JlVmMhhP7DnKVnzCTVFpUKamdWm7W71mzX2AGFuzVJGEh+d51 4MJEUMqr9wGho0GWYujq2RBN+g/xZKmV15zi2lpUgRSZIJgkj6R2oe1T1tTq Q2UhOA8VW4O0tV6adgGgcPZ+tlcJArbGL+2QvIepXF1dLt88yBO7a/YumMsP /wsINOMdHWI1wHAB4txVirtQcALO7cY7seFSO5xp04ezQUQYxoJRi+v9khs1 jqz9ljPqkxSgbteawPoeehphieU7zRicJ6YPGRh5acu+t6Or3vsWITbWhCcD F2VTMOeTz+MDPK+Hkg+justyrL2ksa7cjTYcjsltOpmEiZKxG9dVfl1J8tjA s80JwW32fC4ZARcYoRyKzrSCy7OomWHl2iUeafkqb4tvJsgIH2dIyuH4/C2d /a3VDuuBGQJv1o7wCIUEKtNgp0PnhTfavjY98wXJHuzL7cRzDPDs1M7P/sN1 nVTwRFU/eJ14Hgk4Dw5mM6p/+uj87D8sfNHKdmwzCK/CEcs/O+mGzdPamYnQ /FNVZ3868KB0ICyS5shscDJOtxM/7yZJW7aTN8eHb07cTqD16mvNxFvfGtjU fcI/7j5hslHdJ3N67T7xzy6Da/YpCl+1GFP/2sqJ8EtyonhjHURvxERqOTKX nlgSUlNspcH8cokP9QhFRflb44ZC/J9PZq1XhJNGs+8Qy/UBVeeobsYemaaa 3HuxLXw6KS1a1Le9fv4f2OyeIp7SQm9Otu+wd7lYAjJOMiE3S6lHUk6nTrHV CgambGqmoheqVXYM1i4HIfQSs3SVOugiBz8y3JabZQ/uyMsBJ8DkqZmfmsz8 I6uGKTWdsJWLY2v27zhpwFjRTib9wEJp7d2SeA31dFLjCIelnUaFoUlNgHe5 4QPxChstMklgWi4/gBk3uR0pZGGDsDYwXWETqhyEIWrE2CIUyJZNmQtHZLMC RO2S7YGc8TlOTBidNoV02CAEJ6ObyYXCczdMJ4XdYRYZENwwy5tboCb2Ul/G k8f4KbfBCVjkAfnVNmcilVQ0OIRYwpgfVl41UpmNs7Qgl2N/o0kps8oJgG7J pyE24AZUreZGLKNNGUsoZw3r6cWqj5Yb7KbXbxuTIXUZWznSTbbnmGcMn5uF 2QSDYEHnV+Y1ueA1DWMISKo1iGhawBO1ce+B68ylLPInPJN15XoD3tDhs6g0 kKxZGHUPJrmNNMF8r8StwyHIsEQYWlv8fJRFnLPHFPp+Macj670cRJwDkvsj Txfea1bdwsdeX5yq4NmA45QAx0pekyUslpFC0YAZ68MxGhTFXcRNS6mTo4ns 5zYEzREF8fhqPVmbzug+foDjz7lj+dwxR01bmywEmuREJgqFi8iatqgwl5Qo QmHAObKloZjw2bLAGOul9hY8VG2RQcgCjfICHjm1sBRZS/25dEnEPlsljgWH 3eiri4om8ywj9ywPfrfeOiz5qGhvM8yAVE4SSexuRkULFEP5YJd+pFrhWCmN 0jU6ZdUvnermzSGw+H5Bde7oA4alomBJhe7wehrBeb7LFrCfU42QxdF6MpWZ Rd+2ZJMkYRphkofVjsfxvLDBtmQ6NX17KZfZFwVNDUTVPJciEYAFDYwOAzr0 4D+NP8K/AUo7FNpK4h0g5rjhhKDsY+k6a2g0Z8l9UQTFGrUB4bsajPIiSRYk RlqbjiWTbVQdLBdkQhOvVXY4yGYp7CJaj3jR72aJmxQUpwULNITQ9RkUr5N4 QdYvrpNpHUNyr5IP+4SJiqWUsInNbjBOsQQua2IE5MsBzBqn+fr9oPNBfyX1 JtAUIJBpfu/QfKLLdaIjEjErONI593wdSVnjJGSrqFxDDrnqFGXNrqj5kam1 sQO8QWlnmFewnaG2jBRrFC6KknUnouqTnNn47IPkDf4AWH1JYaOsnQXqxRZA miMnvMYrniLW83IIpJehzPRy9qEVmThb9DfRdjRXATyZMO2w5EJoId1mCsUP +1K0AZ06WmxVesd/vZdJVIjn24klFX1awbP+p7Vf1crTPIlaedrOcZ08bf9u ITO68jR3krnVhf8UFsQufWFfmXbiy9FkpAzl6GgbOfrLZ/J5MHH+rpzdQSl5 jRQtP/93kKIbmZybqEnkss3EUvJ4SzlZqY5LCmbbslp0dgjlRsHZ5RW/UGzu IU/JZQTk4vZZcErgILUVPBUol7AV/8BZViFcu/REyLzyvuJdIwI3pQKfGO8Z iqYQeo/XliFxgdjbVYvIJbPo3sStxni6RJfWyRNXCkV/ZFYxiw0DrgcnOx52 iTUmlgu89zGS20rWVJMtyWf7mB5/lAH7+puxn+ANGMhVXIFiIf4nBrJm4/Js stQLHdNXwIqr4dw1ph9/AM0nIRItXry3wS10OQCWUdgkyr8vHjQ8J+WB4UoE 4XTmPc3Zyo+OvyN7EumgYYjJ2C2x6AgMdPOK8Ymee8X4eqie11QzA4PrW6+i 74gbbtdH17+Kjp+TCJBijdGTY3leKlXCpAw7zYySnXZbuUpZJtVGYfdLMl3x jLV8MnOSzOkWWaV0jGccEDOPF092H6SbQxpZnyeAsVjkAdIRmsW1FvO2XeTG nDHR05fNOvMYjjfZWbs4KdjMx3gxlu4pJ8ikSBZacZgChqhL0iDRdQ2MPXpq ju5TEDDHjhHrFASLo++/E9fqb18++w4ZMorVIK9YEEYBw9nGa0v0SjIdFAg0 fwo5ajmmnzyZIks5Utpk184QMwoSjSjKhfMkFk7Bp0Yam1chfqTypLzJhOSi D8FOSZR6ijA+gV3bFBmFuoSYj6bSUGqZZmOjCTLYZMSOdNZB7cEjglPggANT og51lvSEEEK5myepKkJlHk3GGCf5jPo8EvWdRQ6RLyOPzlz1H2WrHtGLl53k 0x+cVJp9/t/EN3AzBfoEGCbv3Gf1xquqGBiHJbTaJ8scUnYcDHCD+bCLstWe XV2QrOO4bXtWUFK4SgCMPk7xSU695Tp1oNV30RMUf0OawdwLvUGKUe99zXlQ AVwk2HgazIxjJzqAA2if9H8UIfbF0TMMqODEXFQqQlMeSaqkJ8HT0srbNimR gnxCG8YSlFyX1s89SPKtlX5+RUFSTZtOpQvrQHH0TCvCcMQaZy32aoigKwhi jPFfpTgQK9vI/MQLgfUq71hb3NP76uhZDH2T196r6OfrC+RC4I8XMeY2PLUN b2xDIDOuZyOeBwQKrAqdNsidRPLDzJJPBSDynBk5IQFxYVwJsiVW+kgTf9S+ HXVkR91+WLx9vJF1YKq1UteJFXZrV7B+ATYfOkY92fRNrAUQ/aZsU4dJZt9U wxoluulBeiSvMP1Q3Rt+//0Hsy3ixvKDgZgvXIYZ+qq55Mq8lZXF77wXfu2U IFAxpaLkXamZE1xfCote18z5+PWaiUfj20Hn9PWA3v64vtmBK8Z63x/4MPab GVdEIlpMCrh4YjDPsJktoehvZlhO0TY7kCylB+U9XzfaCukCIGJWBmfF2syc vHSUZaAEyBWKVC+OKiQpF0SlmjNrCzZ841A+vlGR8AlxNlepMmom0x2RV6bv KpywAOLJK+2q1P6+IND1J3FqJnFTfaXXRdGW9IDOLelZabwLFwhNTYfKB1Ql g/fjz5jrVoErkFXEsKC3aDadLzU0FdkEjLaiEg3IBjUNVSSmBkDgaBnb0SS5 LeiLCNfVCriQs/4hpaZne6hX2BukimRyq3pQmUqRzY0NCTNIUuRADEQX+mRD mXROvRLbzoXGN8ySov+caba60TsTu2cr4WnmApSXJdJYMp+xx2KZg0FJ0udg DvX95cB7ro11+XjalIWPYF4Bl3GGUq/EbjNGezwRJ7wTnkyZFyAiS+SLZ7Kz 4lIwQ7vnLLTB1DgpqnGPnHNdqZ16xl/s8arQfgoBVoqx/mP5xZ1g9TZEfHmt /1jXCVx7797++QhO5Z97e/7Hff/jxk6O8bHTPf/jvv9xYycn+Fh/z/+4739c 04lfTerHH+o/wZW3Zir6mt3n8k/5U+3rsxV5bKSVTsoEMnhVPODJRdDHeu+3 KKpzfXMf1dVs5YPvPrdi/fiB13QNf+ZUwnIrStNlvarQ/hpOzOcdgkgJfkuZ q2HsBx3RKIN1Vvayx58edHIPfvUD6vMbo2L2fMTYQczRXH/zw48//PiJ1eOf dHbUydUFdKIqZs9bzXNVOyh3cnVhOjEzwVrVNTORMtZ1MxGuqQ4mluk76DhT inyY9IdHHm4E7K6/cWQzwLf94bHdnYMSJ1XOEl77k+IJIOqnL3UgiwjfvzGJ GezZYrekJcXPOcQ9dxOemVcjqnFEK124NZyg1ZHQsMpareEDyURtpyVXsVbP HT/N4qm4OAFHoP2RFdZNjywxy3y5lcQ+pzAmF3HEUdiv7XaSWGOoipERci2i PSEvFGY30ezozMfMkg2auXH2d+21FZyK8ZvmBffaUW+fB4ObTGVLTklqTMBE 2Fq+qoYcnmbiAWNrlc6ThYrCN8l9/JDiYzUuPRgv3jbh70kyJu8AdWogEDGP yQBw3AD5a6eoFXaCd3dQZgo2hrxPkk8klrvZWcxmkIqEasm23XS0xmhdOgmC zTwc1YQqntABXhwJRh9xGJ4yVq6+m3H55sxJFWE6t+5kvjIzyIRUyXH62SeM x4RgE1z8nSMD3XgMqyxS8q4g9K3CJJl0b0/sJG0r9ggTr4sVtpafRw8hdnmz pZoQW8kf3cwA7RucUt1HZMLe0gwoexev6IkSnJOvlmGYc/GkFwelPR7/aI9t +2OAYzJCecMtJ0bZCQQ9DW6yTonrwAFOkrpedJhxEUDWT2BfwjbyO9N9pS3A wRjNTMoNgJ6TDOJTgR5sUoqNcE8eV/8s34XQbEDoNRDocmGEs0CPSedRSwi4 MQoezhvjWQnnzQhklAjIPO4HSJ0T6xdUj7a6+rhwKtCRMo2OT7y4QwfUT1Kr y67YSfLz3ASRnbx8RhUDFOqaQopXM/ZMUTQw6XALLszn0G80WRp60FyrJm95 26zGTYKRGDb3WbLdL4GJqSwl16c5YE+IRXEheTGUNMe2vLEFAOupj77//tvy kj2RKyjYp1Tbbi7FjHuesqLroF25g82Y555fiwn7kezpVKG+1pDbllxbXCGc yQ3CCeP5rXLTdXdGjNDc720/XnPNdaIZdsp5WHI3hbirZOkbJcsI7n6jeXFD 7tbdFNXhX43aPDysSEIT5gSFXKSTUt0NxphMEswSgyCaINY38LfETxyeaxEQ SQ9jL8lRvFhwuGk4y27jfYY/JA+pKQtQGrbtsDP9djWDIpCocgfmsDf02KYy A+OMwJW1a/LioDXuFuO0EFUX2bRBsyc3OyTP8R2Z4NoaRwd7PzXlRYR4O6ZT LCMB29UgpC8tvmG2ettdRR98wna6GPBA5gllickb1Qtv21wX2ilZvM7//v6f P70b+Ge62+gZ2yqmQ7ocPDxnS7PaFKimZI7lNnsXl53nLdKPiX2hbUia9l65 7Db7mJkNwyWx/U4OaWlpuqeNePxrjOywTQETV6SZiiuyrtT5CArRH3khZj00 pzNdQPpGyFwxlvhl534CJMMYY8g1u1nUa4e2evm6BlH6hAoIq8RpG/D/GQSw qudYT7P5OVbFVD23w/R/1OwuWynEGnaRbz54ay59NDOGWeFE/77nf9z3P+6u PCrpeKo1RV+mCvpiHdAXKoBk9ttqfhzVi2h+AhuS+9pe81OyKH2O5uehEzpp mlltr/n5xmpYPlPz4yp+vkTzYxQ/X6b5qYXJF2h+HN3P/0XNz5erfhrRToqf lsRB1Ct5RiUlT71mp78u0TQyPnSFFAmbPUTsIRexhL0r4Y941wzJ/AMrHqDP VvPNcNAirg0POPlzxyJ97ucNTZsotxhZ2zDzp3+XoQQLHJxk/JPH4hmLH/po gz1IivsF1tCpuGe70U8Jyw6edqkZuKCEzVoNR/9kOBMraSAXUc+KGDbzJhG3 KjZb7Xkqqr2oCbS61W6wNsbJsItKq/reRTViHOm6mC/UcHr8a/4Yzxtlpm/D vB0lnvCRU2u8HMdFzJI6sMiOq6vj+7Zf8vPYx46KbISBQxpdqmIatH2Dhqzr 4c8D8o0aXqN358Cx6lE/UyzQPWY9k/RgPIZKa2noWoTzR3Ml/SRuRqGLUTIn gYyT0jHoCpgA8eWGwW+UnZPErm3ERwfWkyz7uJw7yRBZjrEhXsXkqTHJHjkf TGKkC6QalJMNM0ifcxQJ/DXV3GRLKnh5Dv7E+JH6vV3LFUeVwkDUA0m33eBo Ejyg2/RuyV/5TLelPhymmmuIEdlmAPSDdYKG/qMV4gzRV7jLUlsGLr6ZoKqH krsDYl2s1bhuq24ltl18Exomu05u3RSCrO5/rNHQeupZTc/I7nt1ylpCJfF1 VrfWwHXgxqgkET6YCw+nNBHPUg+NGxQ15cT9aYpTrjwncd3OQ5UaPckAnDPi cj4fTBSlsWul/Pea1UcTcJOvJragoHD31wl94abG16RRnFmSs6eivPYgqamx G1MTwVQ/TI0Wz7pxUOJM9bflaVF1QTbrS8BUVY4SL+XpAyVJxT0TF4iknMxG 7POPWcTrQRTG0TnT+CLxHdBscnJZvfq6SHpzAhJBhPpAf1NNQYnJREeux4k0 oY7YS1q/Yx8Zehz9zF/87VJTnjjxie+HneOT7otnR6h47EXwEDl2e/GFtAj2 trYp6G3FVK4ripMA6ZpSHy8o3NJmvuH0vOLn+ZigZg6Jn0k2ix6e+X02GcO3 wA0tdd/ZLOD8iFiLWUFZtY4rNpePF6PccspsaiqnKHqdPiSsw8P2uFTKAWQT Ndmn204hPz9HVL3HkNp90lvsW3wTvc3D2rILu3XajYO0mnq4JtMUKzUxxJbi ZiWdmQmf9YQuXF+eST4yP7LTTkrojIvvNUlkxYaGk+tyNks1ewD9sFG8OfFh GEUOJ0AU9sFRyTmM16ATKus07DEoDHFHO2bzAFEIuUnOLTjuhrjaih92RTaO AQjoqBw/TojAMeK0jjTXyIt8lM0TsSI5Sdi6NmgXA2OAhZqNrac+nXaTUK0d 8RmwKalGN7lkpPpXihz2OB/NOzInTUR1bi0OSs15ZRSSzll5/fBQWARc5/gv +kK1OaEqYMMoBUaU00iMsgVX5qVb1dkyLpkZpEIrbRtvKy1REsWWE7mXueyu 56qncOFMGXKEhVRSjifAUhN+Ee1bOtbHnMH7UVO+2qcivJj8ipzd8Ftcz76Q 0YoI5/dXrYC0ak05Lepy5Vw9G7MSeznCnTT6ltQdAreOAeGmgM3mLrFYgJ4r zgZNwF6bEFoA66dLJFLg1KjgfGYpDFGXPY2s+mSKRaO+Jg7gjhQoQs1xcCLS iDebMSBq8jIQd1oaTYVq+XVTwdBgPl5mcPlKL0Wdgfosenmwa6ZiE6tItkY2 vCzGRKmRFCprEKbK5tEoBSb+LpGASO7V+c8ki9MKNrWNzSBswb5LZljdXOJj CudgtNfd/qR2oGOjNzyhn7K8coj9QI5lXk/eu9GQUgvObIdol2GzEhMLcbE0 RQjoTMLJ6reEad10nOGIeceZREL5dp+Zz3uCblgCqWvYxzKj6SRTQUJuLgBO yFgbVUMcJXnHegkomj6RRG5RQYq903MtuoBTjbtS3pA3Uk4Nh0W12ZYZWKx4 ish8E7cVMiok6rXVzRZvIimkRRIkSB7YqvZCJ01M5QYbv20DovEykcwXVxec TYQBa6V3G9vDpbIKvSRbtHepXrgUk/kksUF6JpFx1lBXMhR7mUOIfkmVkXcd XH5vMknZPOoJO8yu5qRbI+pIVi9KEGAiTWUI0QCksxRra/DzuSRgZ0s/TBJB KOyEZFIhlo4B266HrEkxIftE6NIDueFTdMElXGgZ3V9ef9/9+2DY6w3dWFbj FMSaMpJhgPOfk9Qh0u8agcQvcMYAQWnDpqIt19miq1pFOrE1eyt4hTkWgVNd zphX5SuFrVn4PXEz9hdk+7CIlXYnElXYqzGjGwbPDTD2qprEU5sDI/TvKUw6 D+EXtVKY1v9qXhx1Plg1q2PxN9y3XDe0jsIOibVxdM5B56agWPPqpNQ3wxPj S3m7QtCZzc4TBQ7+dss1uKIEBPJs4cpuNlgV95KS55jwMbLKu0O4deWc700s RDiddkDecl//gOR5lKQPYnGWfEDCu1N4w90swyQ1xhmnbOAsHCWhUPbAt0Lh LgIiXxmEr3L0pfxGyAwQx6AF47m8ROS6VPClwf21uaZO4QRJ2ic9fkEpk+Zq rr0Lo19YssLEt0YnZZ0ak7GT67XpUSsiMbib5oFXXG4dj9Xby+x9S1O6OU4Y rDLiq92tBm8nHlSC51R5yvRsXo4JSTZq1RSZ3/FypPF7cy4fdkjWAfiQs5VO c72IrtXq55z1s3fHMg8EDN3ShmO5YRYPpXMMoqV0xWZL/V3apq6JZKah28RP TiOaYMlIEKglRDHklbHy4CmD5pjFFnZz5Oc3b9raM+0KRjWeZpL+oZ7HFT1M ms+RZfKdA2Bq3vFeH4e4++ugsouusYVhJpYNL4pz64bWtK2tudRFxAZHJDbO l34f3YqJeiuhBl7MXNiF+fTe2Vt/JSYE4GoYHQWmQMmpUzuRrumidhb8w0ri Qly6xSUmxG6673e87xo5JVAheMR/eMOWrLZeSO2OuEZzbxnH9uENsNhyIe6O HDu9HUS7LKRyFqt1CznxFlK3I6vtF1K3I6udFlK5I7i6Fj3IqOUt5Pm/c0dO vu4ZsV9WLOTF1jsSffmORF+2I6vgs7eQl1vtyA4LcXfkeXBGtl/IhllULOTb /y478t2/c0deVO8Ivt7Gn2BsmEpfyqDpz1vcZrVTkAYb7pEtXtWF0fe/vIud XgeNi7AkjcutlYoOhg8A+1VbwgZfzarKNIaFpMjEas5Ng7Lq+DoXDiX3nYCz U+cdFnO4YoRrU22WhL/W+tRmv9wnRidVqpcqQTwmutgqinr9Oh2ZsWs7IdS5 2sDMCOjqTnrBZioxZtaGo/m3ahh40iKR+IoeBx3xsqeQG2bgUXvmeJ9wDeqc RqLssO5IRt1QPxhFFySzMRt4XFk4q5EwRCQgeyNwjtaUlC3Su3RG6Yu0NPYi 4bSbHHM/HFCZVdpJU0BVZGpR/ZYUCC032xi6CGnRbQIrO/a8bJFrO1otReQ2 w1RoZylv2K1qbj11MFeKQfWApCVFiLLvhx/rHklWWcFR7hgzUGmR6X42bLk2 QXzIm1q77IKhKcXXlHORECWtdrmhTKTjvRk+oPKxVGVKUB3Cnv/ePpI1gAGO s8Pjqisfox2NK8GLDlXLcTpRPV482tELKYRUBXjKXubIfEdaNQm3gE2azvMs AG6b5LSUJWQzwZbIUF66qXG2cQyT2HKLFivyIVwBZrzvryruiAOsNOj9zxtD nHYxD6TM0uVh/6Hr8B8oVd5wVvwPbeE9YNKDij1x5cyPm4QPmFygpTHw9Q/b eWkMO5ewSfjApvw8/9i5Rc0Yg/iJagVVtDiMwgcaqyZlAD2kdKCtsMUhPBI8 sH5Wh3Wzcr9w9+Owdh2VY6y4wS4tDqvmuT3uOmcw4ASOXujljxe+ycsWnbvH fs1l/28mB3QH7EAOSsdo2xZID/gYbWxROkYbW2CtxHfCUES2yOqGFsKLRDu0 +Em4EmzxP2TNzCVs8j9krXYd/13I2ssSWaPDtC1Zg1lc1JhHb9DwyOKBeIiw bt+1bZABiIwrOTkmqylqlBhXL3IVecy0J7FBMd/c53Yge5DJgjjn5nfWRjPK pjeS4to6sqjD2Et5/uVz04Bdrpw2OFeOVCDZxdRcIletWyzuIqZ25AQtD41O g3fANDop/MnIanpWWem2ELdYkAXEDt6BQW5hnocU1r0s9LNKb2qHCF1T0xkF R3TQsaejwnJHgvnVSa3Eb5MbkO+/K00m3HlsfPf8IGYWFWYzY6EqC+9uWmFj DKu1GnZ9X2KdxqGrJLhHqyJiU2Er36Do+JixHXMhtthXkUCD2HYAIn0AEKCJ FgvZyK/nuHpTgla9y6S0zVp4OvmuEUiE9Shg6biVfuqlxZFBUX0bXJ+0h2yy nCaugkSlGJDNxuSn6RYJQdmuwJBejISmrdm3nroy1j557qgKYIQWP4QVYN6+ gP4ui8W1LpUaYbyWYCjKWE0hEeSnKq5c1Gt8kz2YHH00bkyRtGQZReegRUZm 4YxSFaizHXpchilq6Tib1A7LCZodKRndpkB5gVNbTpskDiHjnhOPo7uCzjIj Kn0yAVxGF0DHi1kTlMozHX0GUxWkJuHE2AEIDoCRK3km7ltBZTQWOGMKLqHU 3XyCupTj3oYSKzhheUgUGTuwnNgMy9reTpZIkog8zDzw4/PktqAm4ARdcdNb N6EK+hLlLNKzzdMUkpHksFgPJJkB0epktx2jLzg7y4Ytznv8kQr7YJjYIVnm buN0AotH10JAFnWpysvonFv8CJEjt1oanid3Ia7O1hj8myaCsW4YaHefYuxG zsJ8UEOW3vlVZGc3aecpxn3UGkxR//L6FZz/qUQ1XSLGT3kLrxFfxHv2bgmD wdWH2kctpdPSPgbYxyCJP9Y2n8af0ulyGrZl7xO7DvEW8rY2dNPP3E0VT2iK EIObmhQ9b97ZHsn5zeTktgEHV8N36kw27Ks2yOKVN6nqNAj7uaV4XLyowjud M6lnnEyG4oR07+RON9twtDgeqbG+Q0QDRgGaO8kWLSYiXEBrobHi76U0Ns5t itFON3EO0HIfLWUt1Ywrx90Tzbly/PzbF3hFcqeXRSQb4eheY/nRFlVaJPEU O2CHd7MTpEDLKUrSyexj73Xpp4m5fh4R8QBcHDJFVHZM3tF478Px06u/yQen 4mEzZ9O/n4BzhHUTE74HJT6L/IPe0QCRPye3pSTEVIrt0V6ERxOdcB1AY52o tvSToWIVwYCuF8wcmIQzyripIhOYJtE4AgFh78AokrC8J7ivcIM1ksek3ddZ qU8WJfaiopcYyqE7pZ5OVAzvDr0xs9k+oBdyXcHEK+8f9woS7K73UhaHK7gw 4GaVpC/Gk82FrdlJ8jPTLfGSiMKbJ+aYlze/ImNBQatCr5HRkeWPl+TIQllm zAqJ6Bdcb/lJKoHWeRnpuTtenMC5w7PGhw6zt288do+E1uS2SX6kQQW145ff f4dxdqQ4xQjaKQ6PcWFwsqRwKDEZpjI96l8ZklisgLhulwTiTqq7O1WiMP7r TKto1tIrMqJY2y0R2kKvThS9hkdmkmRMugXaBRCBDfEe/D8J0ij/Sb3MafNg VYOgzbUG/fnskPNYb2bIJYGcqbNLK+m0uAAhRmYeM58h3fgATkUc2TfBmbew 8Nl48rRPlKcwJWFgoCxXEClXDAxo/JH3PQf+mj2jnHLfmZMphpiuZv+8pYiY UEL+rrMa8vwSB3kijSA/YO2FRUlcqmSRpWOX5eToVEJ0omaamkah3LzDTTXE Z5x0DGfJpwPvpoLcGwlR8fCEfTjua3yoFI/ssWo+EUqwFzURv8qemguiyuzg uU4W8EKgyDRB/qyhfcnkYcRsXkxD2MHfyRTncAIavpaMre/sY/xU647XnGVs 1nLM7KE/aNC2tdaG8q16v1VoO02ki76IqoqB17G+B0q8lf68MlqtUPu4Mv/Y P7WPDDc/Mql75ME8ktpHPBXLDz92OuIYM6rrxY6W4J/e2kfoT7H2kaPNj9Cf uO6RiOcOb0abe7lf+whBd7r2EYJusvYRgu4s2gjd9YtONm8A/emvfeQY/6Sb e1nUPbITdJdrHxlunstkM1y+Iu6uf6T2NNrfTr60l/WUwXusTgn6rSpBLyUJ Cjt49IwORVVDuzl4sLLpnV60ldomJxZKWQMh5aECZ20KBHGmmGKGxSJbGILv 5YrxBKEguNOyA9tprjhyg8uI48hGG4LqMLirMFYKuWBU2H7Q96wx0vAsuo7x X/Vm2HUOsAlGdBQfBByWFM8Ok+ZJsXFt9+SToNJZry8htuMU4IPbwFzn7XJy i9W2CLZ3d8ibFIkEGkTie49jUwLIW+XCWUTEGBYJLxN9EDq2uNyD9GJkhLbL gGCYmQLIqDprvWAcZoq0NLCilglIRi1qkPjYdd4qAdpwnkYBgiubJJhkBAEd hDo4yjEjYvRmTxg5DX9gKse9lhcuZYPJWfi0lWjjOwnbIhRzMnAalm5bEKkc Vr/3Vl9GJgWzl65qBmdHlcddSYgmaTMxrYflPDEJO3RhFXNee9bZe6aiNuZu 2ue21iFG84SVQbBbEkNQJuiI5JcfCq+WO6SiSp1tuiQNcijZxJJKIhlrrPUT BZCww5HDpav21kxG/cxISCGHMgNItNL0JOULqTriyVNOOnE/w68MBHIKppRM 82m+OW+AVPSwJe1YMa4F1r579lJNK5YFBqlM+WPWTO1MW/FiwT5DiUDq8nnJ BpjwG8nYxOZIii4KzxEFf76cmpQ+RKRsziE5ILw7uEDdJ+7AxA62VQtDXlmf RokIGppDjRT/qlQX8byHukW+USUs1mqCMQQZMQzbWf3OIvmVU8iLrvJq2Iep ziZUq3Jmysq4lb5zU3oWu6JETpGiGOX3oEqOIIHmBYftz0FqnM4510QorpQ9 gUk8gn2cAzZwcHjD40wczmPldVE2yW78n9fPClg+f5yK1z9Wh0GjyeZGwYRX xFbu0KaH/462aaN41SEk6Bx1UNtifivw34Rcxled2hf6jauCwvQz4H6YASy4 /aqmnIudjbOGGP89Ii/tNWPvR4erf9hGo8hw9J/xP9vP/efs7vQzdjf5jN2d fe7uHn+l3T32d7fzGbtL5eWOd9zdNPo6u7v4nN0dfcbuLj9jd9PP3d2Tr7S7 J1++u/TvyY67G309yuyCdJ1w+d0m4XJUL1zCoO/o0tlU9c9mr6KGNoOPE1qv N7jLZ8Wcp92PEjaqQLK6O4lTvQQcaFTknBk4WLMkbVLqd8nTlS3zmHz4nSjk lo0Tpw40mOMT2sCglSZ0cUOAEhucUM4q6nr+Iy8+Zwauro6DxnbYmF0/+/aX hsQcRDWdGJ5iq7hdQrcvitylZxvX0ebo3fVLPmhccAs7m265D/1UF73bpxar SPwWgY0oZ/ktr9gbsfE9j2oDp/bDeYhSKAxOPDLrbrzYuJZgDP9FEWTPg7Wc +ms5iMIxKtZysn4tq0jGIJhWxPCuBEfWrGW1zVqugrX0fS54tc1ahmvWslq3 lpPt1rLaci1HwVrOjO+r18fatZTG0bXwfwccy1sfyatrqYzuW22/luu687/a fi2159YsxN6+VcG8q3XnlluvZFZr11J7bs1/VdTOX0vtufX6qMCxl3Yt4bk9 d9bSEgK9aS2151YnscVaanHd66NiLd/atYTn9sJZixPHunYttefWIYefvRaP JFbg2Hd2LcfBWl475zbaci2159aj7PSqies1fXzRXVl79rd+rTbxD9v0UceE 7PIiTuaLw3u/PMB3U4jvl8X4VkT4ilm8JtB3SysQztymsY0oO7XNLCdq0TIX Thox8eP08/hY1bfPqxM/jVouzDDGOYA5R47X2men2046Ur8zNx0PafUCD8SO J0dQaHJYVowFpkfV6lERLtUEYw5W1M3P0Vs0W3TUfwimN8HiDeJK52SRQlcG j3A8UvC0hhN7+aQrvYIln6aMPJDw1lMNb20OfjptqW/N82+f//FHRUSreomU ZA8NWNUgWfX30kVrnbEuOgEltsKnOlubDHnpBnFF0s52pA/OAW2mg3W5MPJ1 zAHfmVXBR2ewO5h9qXOJmDlCEPx0anwcncoK6MZe5GZlkiKOAfPd0bNnJCtd wea/arwivTIjV5DoevPEo+awczUc9i7bEaXxQ5IvyaTbUVKMui0tesCOqwja dDJZ5sWilOIcRVk0nVrl9E1iUs6zitspDXe3TMeYtrAk81W/QvrJklsFzZcH QSbu9OzvW0trpQggQ8T9y7f2AsAOTl4PBpEANoLd0g6wa73QaucDV85KR+qa IbvSgft5zQxWsJt/xrRMP+KO/vn5SwNB88VB7SoIBnJv7psLdF9m4H6umYSb oGTDEuo7oCW8fPFffgnfml04ehYsAb7ghES4CI+z6+64BPzHlxpWtRlFDnyu CLOUHCCnimq/v1EmORI5rKKvYnHlL/Arj9ciTlBngMfxNHJnUNlB5S5Ujl86 jfUdeKfxuPY0rpnBtnhQ18HWpxE7+Lp4cLTabQkHLh4cCah2OY3VeLD1EqqP 0w5LqO9gy9NYTVJ2WkLVa4fTWNdB3S9byhYHjVq+O+ALKqqg0yFS9tskNYEv 1nDdl+i2TAls4Zy94zI9CSdBoe6a1wn6rwCefcuBS5QJmFltrTaQUVUI9H7R mFG2es/ZOM2lpFgVbYL4buP8nhKGsNsut2dp1pQ1iZ8aD/FCmGaaTa4Jheyn dnTPpTqCCTGX7uSIbVjxRHl35AJvKIiKynIRw8teCm/SjyYcoMLXOEivUpcm h13NOIVNKfs2LrnpChM1KXJI6V+bJcf072eyMZ06yWuwI4/ubE5hY1y3xlFQ sAD9dyigeetEN2uzENVmunGFiS2T3QSZbtjrrirZjdNKEE9BWcQqV4igVNG9 JoASwQBYXSqlFRQw9kPP8AsvX7B4Ih0a1xc/dav6hay1UzmBD3X4ut6hpjKe mQNkKGQCB6+Obt4xtJksTlXRzWLrQ/qyOT6axSjalVsb+CdI2aTwNj7KIOws 51gxfOGULJAHKQwijGaKfrIVE0x2ePHOMZaylub59laC3XmL6W4VRC3lOjZu YNnLten4QrpRyi2XbLnJzzX+xe4kR70IxpF0jcdKM8lrWXj1UmLfQ9h2dAxC by+knloqRDpxYpr12TLOu+DLBVQR+smoyVMiIb0CMBQw6WpS2Dv2SSJgqbaA Opj6+ccf4ycbOXlNT+OUPHyImui/mFF808Hg8rpFJQIo2MdCopkvp+qJeCvj 4q/cA/quMuX3m7W67thud6UhEf1tt07ct3rbzhfJNF1OW2Wsp75g4yhZWQIn ILm9xdxx3oPSDdfzQl2Gxtdy9GE6sy5vhzgjQgfcyuWU1IzGNdRMTCfgESgO M2RHxLYbdFPCYfeCUJc0f18UWck7rc5CffxMA+IKk8CMU5HfkvmbgCYdaoyX LItvuYc45ThzfkZRHitlsaPeTDQli4RI/s0TVabTniVsmeB+TnBvcU+b05vx iahmFKsTAbmxQPL8yvDDW2QbigzzLbbCxou/EY/Ze4Ub3zlSjQwHOciL7BHD sMmpNDmtbTIJm/SlSb+2SWqabL2W0e5NErfJ6bnifOforHZi1LK30ygacLTr vmzdxIbMxLuPMirv/vGG3b8v7/7xht2flnf/eMPuJ7vv/mz33S/Ku3+8Yfej nUahgKj+7vuS7r7722Uzizbs/smG3V+Wd/9kw+6n5d0/2bD7u52Xr3j2T846 X3H3T3Zvstson0H5o7UueMfPdorv2j5973sb8c+8qIQtMBsSjx/iWRHfsUml XLUHIxiMla/MRbRs5Y8yX2eeFq6U4zk2MhK8+kqGhUu+lbgTCdV2WI2QLbty OAbDjgnr4PMOksLG1EoJlmJDZCjZAnE6FH1BARgoLD2yLCFFcLUQjc/PtyOT utfyP7w4G4o1zSSn0iVNs7aHCkYxgEWX8oVQlgm34J+Rb8julI6Kcqj08dGa UOnyqxQ8XX5ZFmoDs1XizjYeOY8767JvBz8sTSqZLUtvVuIjtJHZqmqygdmq arI1s2XdXLYmuLbJRmarPLGtmS07ytbM1r7jYfLvY7aC3a9ntmp3v57Zqt39 emardve3YbaC3d+G2Qp2fx2zVbP70U6jbM1sBbv/b2K2Nu/+yYbdr2e2ane/ ntniJlF597dB/n/L2T/5qru/NbMV7P42Tej19Zmto92ZLYxz+Mm5Pb9GTL29 Z49r4zHXhF+K+tuo6aligWqZuWqqRmeui800gZlkMlHFnxubqSp7Cc7kcmqm 4DpzIvFCfdGwG34E4ze9yoxsNKoOzyR+zUkZR0qkIk8mtxg7i6X4xNNr8uQq a0u2oVIEKfGvayNCq8JBA65n23DLlcE9RtnPit9Z2SOyKWoJQ7M6pfgkS+0e O/oeo6Ko15U7xHBT+RdxWDUNJpsKqJFJ3plS6k3p1JnSafWURttMqS5eUztJ tplmZbBmLTT7ztT71VM/2hWa0a7QlCk5Mgt6paL3G6U9Kk8p2jr6jJm+Lww9 k2ttW9T1WtT6BsjLriy2K9sO2CPB9Y2jaIN7wXXnKwpr5SDGbrdb30UJOY8d 5EwEwzdPpC7WVHjA7TD8cwFM/x5vBrBFnf7XQJ3UznHtXC3qAD9IBHlrUIx2 BcVyV1xLd8W1wsG1rRpEn4uJJyGZ/BxMPHEwMdoVE6PPwsSTLcBvUTH64gt4 He94bLx/tmYd1/KKNgyxkkfUH6sSmZAnPRVJF1d65jXLj9bl1ow4O8sWoaft tele2n52PnHmICWbG5t788TOHo6/DHriSJTuNLtBDxzt93Y540zpxAj6Naa1 +NjtrbKC76+cWF37peOMQzKQU0vKKfT8qCXOJIsr2kZtbTKJBiAHGOyksnpW u9K9R4tn9fU5yexPWjbqUHoLtXDRBe1CDvvxg1v6Cc3UzlcvJc83QtBxmHE6 Rreen04pG9GmOlbQzw3BBzjkyTJPHxLgtDMJCeHVkceE77/ESlTjo+N5G7gu aUX8ERMXzThPk7q9xyb7EU+mpgRAUXcI0KRM3aO+FXWnml7IFFkPNbXkYmGk q9JjVq96o7jiZQFy6i8oYpg0NJQy/jYFQcLm8ZH8mCnGl3OiLU4O1FXdPAUu SJSAONXUnvcgrb1NA2pyxQcpdnNO9qpui6PYmND1kElidHWSKpIpSJHo+LdI EC/YRS1QrXPEg5MZP6YqBpy3lI4rA3k0Wi4ILcUsQJN+JETvuI4MN7htdWr/ rSpHIOhhIM8x4AYA0UlclwCSY/thOn2J4tGU+nISvXTcNSn227IbkjMumWXL u3t2WpAxPAW/k5qNPB/mkmw499IOoe8SBW98QI4epHi+AUi219AusvsAbfjG iP00q8T4qRLa5XC9vGfvuKX2ZfUEzfJ3jCwgKiPEFsktEgWOa5JseEAfKa89 JYTGiRinRc07PDhnf6AFnl5oK0RHCSvMCsjK4knCzHKmAzl6FllLku+tOXzz DraNcpgtErg+f2OSAW3mMJPRkmNrjAed5rrFmcq+PCLEbzgnGpuKgsk4k29j gBB5ppETIGsDGFJP2LUJpdLTicns1f0Lto7tLPAIrAXIEs/GkE/jvokoV7En lNQcVTPOBWkD1hJMppsklE87o6Tb6PYkqhkYQIKgJLs9R60JjQJMpQoKpUwV 9nrGXr+jpMGkUGGNhnOpyC0hrlJY7aa8gFwrNeDsZ5iLfF6kUzrj+rCvrGJn M0q/oE2mSbHA2D3eKIzCiycjr8RhdVfW6YxixxApX0OXmFgYrpMiGyFLdvl6 0NIR0C7o3dljTJ83NRo4ccyle0PRPGAUcklmTBSb93qBNKCSUaIbiJ2MK7Y+ HJzQ1yJrbrrWbl2yb64q0hxKuOK+yXBIUZxyhgSkgiK6O9nCug1StrGe6Vu7 o0ZS9cEoCatQQPR9Jsnb1fWAAgorFq0+4HSumdiartF1kBOiAT1u4s2N1zyn +sOD0VK/wh5saH6PZ/V6+POg8/5cwgBPjp99zzfD8Np++/3xC6yKWSxnMySh I0lEzZGkSuYEMExp4CJAfIr1inT8K7vRhb1d2zyPvd6e5LA0R8uMZgGOOysY z0jNbU+3bYvhs+aa6SogLibJp05vglnli/uprvjkxTNYsQTxEr3C87SQc9Ap nuZJcG45gXg2Ez6DvXmRXJCnOHfldMQlZQr0ipd+3vb6cGfywf7998vz8/Pv nh13j3rnwK9S38Rijk2PNAyeJYM8Tvd3SXa3iOf3sM6G1CGRA22rrxj/aaV0 mJVvOTO3gVKACVw2kk4fv99TpOwYpNyLxnERU+0Yt2AAPv3m5OfBlfE0fssO Em9Ort5qSO73R98dC5NOzx9XPX/sPH/8PRvYe5M8a1eepvCIMMU07glwuAAL Ta0yPi8zL1J3ktwWmkGS9OOURVLSveJ1KyEoecFpYjnZazK6n2WT7O4pah4/ O34unrRD1sCrfMUxEBIxwjxJRdWvf2U5MibILyHqSgOi3tWXiEiayhMOzqVQ m+uegjA24ikZLnh8Ts1K24Z2jjxXp+W254phMMcIjNhHHTlD6Ilg4wsuzZLH TMunCdjrLdxLcmjsZR6msCKHf4rqwCBy43LTLs3T6aPyAi4DpRUk/zw+ARxl WZNSVTqR3rFoEwz1Z6as+rKnxRG7wkgZG0IM1FbJFovOCwPGAd4/6HS/LBiE 5xL63Rz0z/VcvHj+/JnW5Qg7wGuZLjHjQU3cSYJh41wRr8urrWHaDYbmnOYA M7I6MPV6FZwi6iT7oGl/a3UqtnIg9iCDUbrcG5z+ffaImyjnmcjsYgREraDj XLWjHHu/PgWsZ60q56ra4qVJTKhwqDl4ok/bFED34wqe7fQqwlFXm3v48Uc1 Cde2XqstdGbujHKwaWx83ul3tWmklf/8JwvbNf0bGU6fx5dvFAl2x1nNygp+ TuuW18Qfm/fh1M61587VZpby48I1yNPdhzIkpWkJTqugm1LJ1orWrnp1w1iV u+T3VvFyoWi/zTwQSnas8ouh2Oex7Q5qa7N94bk6KEHR2cFS6xABVpUzP3Vn flCdhs6MFsKpDJyV+3wJ7ro1B+aveehg8x67h5X/H8yW4XpWEel7EI5bPlQO XKu3fMPLzDxU559UBPNWqF6uE1YAoO74PHrPt9uGorN1uUDawV2c3yODwAnd SWYi3kguUPSrrRCd8ApouhxSom9bwDuni25QwFbkihtHeHOvaFdgK4/GMjAr SahiFwyAcBqck7pKcnt6aUE183sFP+g8S7Wh1kb6hvcrXaoSR4QqZdIoY9Wl bGm5Kik6xvFNpGC+rRLnRXXiueh6NgQBiGcsoL3RogRlF19UxtuKaKa+URjl 23W4aeRNAQguAKpVdh6r3XbGth7a3vTX7Oh6r9/nZa/fXfJzkT/vqtuNwv/q Died6Vf6qdc3P8h3pSSk2iAwO3ZtJ9UNVqWEaZsbeGRymwZMqK6G0ZEHtfC6 2DhCicZyg3LCtg0N6qEU3MWboRRe/Vutwd6hqyooHXsl5/H9j4bsbhjB4w97 3pSqoVRmKFfroVTmITdAqYqJ3GoN1Q0MlE48KH3WCBVr+MpQqt7pCihxVp/P 3elTb0oulJ6XoLQztm4NpSiq3Yf1J65649acuK13en0DA6UXX0aXwtdGKFU2 2K+4H+qSu6x2v4FCNu+5snl+1gO4JdFktcbWtms5rdo855XOqiZiKtTyVOvF hPnwgp+CfOhdL5MjsVAmF6PJsFin7NJSJ6hHVcMDKaVqMjCSScNJwljKwEjL dRgSSWxYwZBgV4EPhGVIXlSFIe2WMlSCjHZhS4ywsQtr4jbamj2RRtc7sSjS 6IIbBUltNzTqU6OVbqfn91nb6HseKUhbq+S5ptGL2umtafTcn97pVtM72WJ6 JeoebTG90h1y5U/PcX1smTmW7sJh7fQOTMvSfbhhevYfl/s58qd3Vjm9cE3R euitaqFXz0OUd9hgeT0fUdOoHsvXNNqA5dVr2oDlwXCrrbB8VYkRAZafB9M7 qMSIeiyP/Om5XFI9GgWN3DUFWH4RUFw7Rxd69Vge+YO4+7TN9EqNjv3pva6a Xt1IddMrvdxGu5Hl3Vgi06iCLapPeaeNdr0JQ+boRS1ztIkx2pYtcvyuBmKK OXxrfK6i37+pttYQQ3VqUuVcO/4MEtxOzo9cj1CdtnKxHt5mi6mY8LPZQ/Jk a7UBylwN34mChlB92Jd6ggk6AZDuhhUqNk+P50zhW9SIO+qc9Y0uj+q8R2d9 tR1lM8xqBnPKC8zpS8H2jkLLuLpipNMkz6iXWcSaIOnjPn5I1FqeSZY7df6B h1ivhQW39ecKy9Q7yrXHNq9cTb0VDiVt43gx6Kh3KBm13YRxND30yaDJysxJ Pef3f9bHvVjEXDwTnRdTp1w7dIcKUR0vh11AcxjnY+Kh2zoSqbloMJPZQHYS /ewIEzVh2CdyKhuZL0pOxWqkT2ndmuMsd8x3EtOPK/T63gw+2RVEqvtYwvmw ACYsNXpIk8eow30Ty+t2XXLRDQCnjgUMf9XIFhYD9AFADVMVsrQATIENwyxR ICiDpQj2puulnzaUBrf1yCG1ZRLkfYuPHxv6U8n5VSlC6r4l0hcaJ/T5A/87 /egI9wdeL6vo6uKo540Cz/3p/+vt2roaOZL0e/+KWl4MY4lGqJtus+vdw33w 0FhG9Nh+mXMKVEBNCxWrkqAZe/7Zvu0f2/jilpmlEtAerzVn3EKVlZfIyMi4 x+CgtxPdiYODzZ0/mV7h9HAzfuH3m0vL78/CJX1Be+FF7YYXn+2FF+Uv/K5z Wfj5SbgkvwlfEU2xtxcNhT3aTfdo90/NPaBlcV2Y32kurXet6+Tcc93g0t58 uQ2rHbrtn+d6sdt8YS50GPtfPJdncPeFvdAe9eNz1E/P0R86F/vFfk16+s29 8KrsIP3Bc3kGd1/YC/ao7Rz194I88UfNxX5Zcgcs7eWZ++iFp/FLPq/gg0ky giZkvWrWollaWSYkZB0igHchCbVxl8ak70yyyFb9wZ7uRIUNnyn1clLA9dp9 2ULyz5WfVoTbZG9PLgO/lIEqvXCLc7tSUJ49k6Q/sD/m2B3zz52YDYd/Prpi DlfChGY3iIZJTLvses1lQzixKEfpnB4Glho9oCY0PyBwsGe2Zr++rz6p32yY 2zqbp3Ot2M6+VcyDoh+SPzQNsCUt7qQLjRh09D6+F4VlDEdWaGp2aw7Nq/ir QIldA2a1d9+9zSWaKoBF+MliVCeSDCtjtdy0epQxe3kB9zeahAHbeEMMh54G HM6RX8DWbK9L0Rv3M8b6qjvx+ZQkxPkFXBdYG4sZ8Io0YEMzfd9VtEfdWdXl L/ELKYsKhwHmmGk+xqfmdV1dlnwebNY5sjxYFXVMlcRKkj3v82kpy8d7Ei1Q SQ4vSS8uCa68iA/nptaIG0aqPNRTVyyIZEBBHCwwQEaRqCvzVt6ZY8UQd69d EIZasELXvQLMYZfaaxBMXFjU+fIG+ovzx4XkvNBh3McwGodzg2f1LeKHrgBp dW7A36Lqr+vyQhxIbPoSoudHKvgkTItrfX2JuHguwnEKO5GlzbE6xs1nC9Wb 1IyK6EX3cyQtA2y0ws94OUjco+KWAcdJTKKjxRj940JaEbdRxGTB/V5YeNSM 02Z14dO0v1dy+vu9v8fCX7RB9fzWi89HSGuzYyoFX3nGRT3cHhOwAtlihREX X3dXsAUr+3u9FQatOeU0Z0ZdRsup9aXNFcOe0vxCi884wLWUD/JZ2D5bdwLd bT3kM5L8Gt6zTJpHC5AWCPF0MSWeQrb6PptPiHqtWSKZafUQBwpxvLmmAh/P byftk4n2XmaU3zKd1zTS2va6AlQk2736rLM+QXUcC2lvUAv4Op+OxoXQB5fZ QbIETff3OCHgrDALGWRkMYypFQ4vC83WJWlKGTpRROpo/LD10WmqHjoWgnOR 16WqbVj6lvuNqcuhkJNx+amQPDbR5ou9roSL/OfylsaETzCPXwIZ8klBpGT8 2ESxAMIEr2XXOKLPtpPJS531erKBUbBrsmRbr2gSFtZsa7FlZ6u9fsAIQHZZ DGUUCZCHJD+gmEym4STFPvYcjtWuedNoGXsFWVg0LmdAX9l4KVoxPiEM/nLC sSbusu2AM0JsHvd3U2qKI1cjgGLM1yAzBZe55Nn+9ZAA+/q8MmYUOpBf5d9N /bePf895N5S6kODZ9cwt8v/thP/chmiKrojJnbyW1CYoOPlrxoWGZLBeb50L 82TamFOu9fixvbPpjbPN9bdxY87Q9UYev0veQc8b3jOYTiXOIUEW3UbY/3PF rX3Gg+yDHOJV0RT/tKY+j7/88l/H3f31sphddWdFXnf5mx5OKT/SnVyU3cec ffH1wHFkJp0FuVvsvLi6KrpiWikJuMQJLu5wZzF7RHuImCTNC1kvlgFhXVq+ jFAJbtoInC0VYTV3YEbYRc/1k3HEayMbf8BijlGiK7t5fMuZzzT3HJa0djul yqJAHcW4D52H0BaOW6dTzsdN74Q2Ei+tqaHdgXWgoAsqxwUg6Q6rgrdjC/OQ KynoJwdGYtudMI7o1F6mfOv5aVBfW5545owfSsmYOi1sFcLMeCGIXDg/7Zow 8qLQMKKKbux6fqHkJqHuKHtDMySOgJYtTCq6msCSL8jHc0C0b3lVenzVV3ir W+d33XL0lRCzq5Ahg0O33my8Z6cEHPtmKYsAecnTZvXgWwG+KrTx4gGxcUZb RVgQ7tbeFFy0jAttxLnDW6Ga8guD//hREWz0hGngAFdrtL3xqVOWllZxNR9b HzhhzA+2xdOzUUNSC8jllTpAs5zot6Ws9YaZ/3hVYktgatNgMzXhg9tzaC7y 6vHB+WH2887pUbafz1iUk6g7TFSi94YkJwGf9y34W2tGbn6jwaLPdrP5VDdv thBdemmSiG48MfP5SDmbL6OQerSJKNbzO3PFTlnwgGwtlHKRGROqGvNYglfB prKAobr/XqZTkFnEZcTpylErYaNSoWxaEqeSIbKUxR6OZk5TUYyrh66JfT6R iFVXp6GKVQBRfFbg+DgIDKy3iNjax2o0CDPscSRpGh/bSR8ih4rErul0Rday mGDJaGghtf0NjmTNIwd3VUA0OJ31xE4FkkM48RtuSo4Z4wwRMeh0G6OYAOOS 1R38ynn7WLhp4LxOJ+CvFnlSlLOBJcYvgljIPoGdlnBACSMOM4TVcVKoUK85 TPL59a2qHOrCg+zs+hcSWCZ6D+PolF8goaMs7uX8oyyIHYWvPJw3AcxXGrM9 v5y1EPIQs9sIyoUvX7A9e84NJdZP25+hJ4pugWDpri9v6IvbhYlOKK0ubp8N LPyA2AtXhmgeFpX4Pb8NB2TaKUtN4nVOlwDNge9BN2AmFz5zCDxFGm+oc91k 6PQ5x875wb/75eQTkaCYeDoiKzdlAAbvWyQ7lQpNOkLW286GyDoC7OYA0cOQ YmR1ODhck+Bja9LMQuLVwC5pLTFvd3w0UNWJeUUKchHoWbepocCpQCaGdiVN yD7SafSl5dwY0MySKFaCgHi9PTCKNF3ghTOamhPjym24rMiw0jlESDuiyDEp jjNaqHqknLBEaJ1IBKxo13gyyt2EakAGWvQJHZRmpfB0DopfsZx1Pc/pyMyK wnhOV664Tbi2cCK+haF9GHO+Ixofl3Zh6TnuSuEFQlGoMAzB1KN+WO2WKH3i SF7a0WlVu/Kl5UicsYJVY2Gs6CEtkSnHRNPbGrW4L/kuX+BYOlECDdM7kFyL 62XK3LLkNyKyV95B9SMuG2yRd8YrFQFCjiZPx5u4TIBj7YpmIWJbhZrIvmHe k3xcXfNFWrlWXpJkgBCwj4Me2QvQQIjw4E2i0u0K53zWvstx6WreJ8FU32wm KDZn22vkgrAtRrKwyUjWPNLdsg1fzDaHJzuRNlf5v7BinulTSSz0pDfybkDt 1XjLKStolh6aruyy6VJlU4WWtb3tJRzo5IsaVAjJOeO/K5tz3g0gP6YRVcFs FGQkGKWj6FH9kTPC2GllKCD3AtISo2Y9cQZM3tUb5X4+nrAev/CUBY720NJe q7igaEzoShKqeLu8rqKcfcLIRWx6rYYQpqeTKJFYpEy5KDiBGBJVgFyG+8FU +n1VKMldRndCJ3Zw1zpeIzDMbFMwmbBWws5nnA60Xg4GlM1t3C4DzojDprXD 8jO9HruFBZIhN4W+KGasp9PCSKadJDmM2u8wyPIkA8QbPGYr3Gqlkz1ARw+T iepf5Y6ZIYcN8x75RA49H47yVmAoOrfAHFa3t/MJmwihCpDtzLwyXJvGVg/5 aF742UVCGz5cU3BWYF1ztxK45QsCsl+FeG0lXtuKcfzIJ6XlOFXSSkJCIxVA N/KWmhSE7zVyyK1yWrYR0m0bYyAyo1W95R2Ico3QYjnbiCK3TCq+O3S6SZJz ZbFb9YWMmZzngkHqqXvYnAhmWFkgX8jqtFi75PQUoo8BOmZ65i/DmdfASkt4 IUhk1i6/jBm+cuVMp6zX8vwqpueHiNRRubMxBFt5IBZD6paLFOMVDUmKyQ7m wTmFWsQq0RUFZkIMDy38REwRvccgocf9MeVo4U8iLgldPqsItjSIL6KotVNS hneQWFu3vmndMbVSotyG5fzvQdFQB6Wj+8h50vxUa3elAdsyJ9hKVO+x8vOK XqxsWGXepKkWWphmamIxPf2magDN4pJq86E5clOaFIh+s9ju56jdI7WDjv5H nRHGUeJj6QcJ+ih/rCY1U66IbHupBOeJxSyw4DGhirhBH2MBrpM2t9qOyKLI 8RleVQuYmPpmYpRTngtm843199nRxV3dBmAlGcuomaAiLxjltwFRJPMLxtKl tKbNXsa/0V7yZOjX3qbNTN0bbolQay1lplcjKShLuBfqeMvZ+0NtEGIwYFOC DLalhoLYBrEhj/UdwNzMCo3Gfe5rix/3mzaIt+s9axxsEI9fZoP42WwQxw0z Dwtq++qL+yABf1ckAYDTEaUJtpnl2Cu9dUoIyoyc56rqFJxC+iVL1GepfIhA GVY3Nr79iEBEbJd2WPvE/jnDwTK0bRIhPmOSqBUYzCfH9KSMTNMp2IiRqOtE USfwyS9q85CGONHICNuJrSBtWJ2POUMf+xUR/YN5Qszc15XQ6BV4zK50Ghds dK3X0UlIRECrV85iPg8tvXunrj9O1eVBhbwMIu3gsF5eCJEnwCGieBMisK9W +YjkjzFkUhOUdDHiGwDX1aeBtbX+5rfAyq6l3/T67oq41rifAm72T49y+0/d DiBaD3cyB9/iZbEjJkgYWrz0kAf2ZCz3rkzEVMecilW92TXVxqdJ9eA8azkL J1L7XX6ohDvzq2ksCRObNvQ4R0o+ETcc0GCzY2iaFN13Z+ykonMrZmBlWBhg is2NvcEEzqnBUo03CSxZSaIzSOBhlnO8ANAEuNB3h42Y5ZaARphsTTVqm78b 485rw4JEXddvCGTw+mmVxsTZMIiK2WbH+0hls1Qca+G4xQ3ixUz3Uo6bMejl TPcyjtuY8Rcz3a0ct8nNL2S6l3HcQTvxQqb7aZbbzC/Pcd1mlIFsqpvggjdW 5Tttmh3/AQl80Atwl9WtDWE7RVMDiKHGsdjTOhDsiEGX1edQuY04d6fkwnbI 3cPupcouczQoJ1ckpU+CmT54fEYmILVdgFiBqrEaUUwNamqvzJgzKkmuLC+4 mLqhtCRcnRNMfV1sQ2eyMuPs+m5txelX2xCJw1DOzKaP3dGUTTnoA2aQy0gr w5hzX5WjXNgUUyJb4s+opoFAqQGOyF+L050KyIhWifWI1dpSKAsSAewZ9U01 HjUvqA6THlVCgh/iihQ6YtSxDQ4Tjsj+Yz4qBAS2KnHcGvg09AMApgRBsmDO 5pMiIAJ7WE4K0XNM7Ue3BaEjXkW46NmMykCTv1kDL8qtOF9qHec4RZb99CQN 1drzZr1PTCtNIjFqZKknKhSldWn6OpooO6OK5VKC+oJ/NH2FoHEJW615WSd3 hlALJQtI2qs0sKF8zlVtGZDFjMiwBBQ4JUZ72PWUulJlo/rKIrdw4emJm6Y3 wM8LzWJ1155lN3fVZgo00QbT2cHNjsS1nM6XdyZWQtnmEJQ4y5UQuG5MMOtI bWZGCAZLOFWcPz/WvaKv73c+BLLl6nF1JcNNP8mV8VNq5znRPBKPKP+jzzY3 azF1HLnEr4oacYstiGt8Cytv5GlDVY9myvFa8hVbLmuPH6qtYh1Artgj6cwK HnOW15+Yaco5hCDRNb8SUYqdEFldDYTg9tjDy8q0Xit0xY1XVJb2BWsWeZiS tSOzY/FFCrUmv8CGdiIDc5odzVVy3YcMd9F9qflnmywXvP2kq7AgmSB7mGO4 5Wm/+dMFCeH9DQEVnkla6nuw94DQtARGnZd1YqEDTEwji6P1idS+XzAS50yp JX6h4HPMHZR1pQ4ybelTRD4RBYWbtbxYQhqxbW4pqXpYLPwLcxAiQZtR5lGk LGpYS5RK2nWATn6dQ+fCc39tc/OY0ZYZ+P7L8Xi3+Q5adjdAIjbiHq8VD3zP esEMnFp5cVZV44DLri/uuncGNzAaBZeAQHlwWxWfZ9pTCLxmPEbVhujQKcFn 60WjmS00v8vZJw3+eotntKbL+xLaZYIgzhmjdtBvQy1nU74q8pmbCeXGyEej qVK3cipM/PoiZQDX/5CLJoEIF0Z2/xjRgqnAoFOGxuJSiN204NSNOrTHE8wv lJxFMelZ5prP5Ni2IjnPSbecRq9n0aDamQ7twQTifTxWPpdXpS1VBLJyF56d Hxc5jCyCCMG+GDnVAFXYegZlpgeVa1Lpzfdb0CTqX+96b/AXLU1dX/pv39oV vgBuRQkenZVAj5P8Vm9NOAA5TVU4Nm1/Ki2yPqbQTRsZzWX1olm0h5izdu9d Pwa0MyBBgUV/sq1oxrfarAjhIBOaK8E4n126l4CI13TGtINF246yda8jbxXh 3iyqXPm6FEkSFYvplm3wwhKyz1iN2RFnEy5ckuWhuleWRUeJjcsSBhaL7E0s 9O0X1BsbYOZ3lWXrP/2Q+vioHIEM/Imvj2jxBBwicM/FAxnzkg1l58HX7PsX XQ8mTmglmXZiLAFYynzw+pXYh4yq2clnGO4taEVkwvbetC/O8+kbKFzvCrFW tGldJcHdcrSS5TOVS8CbGOv6br3vjCtDZs3R/oNhOB1XrkiTpZQh8a0wSzqu Pr5VdHJ2uTHOXE8Lr3Fkl0OoXsNgvKkmFXuonWuwUz6JxDXQqOHJ98QWTspZ NbWKTcRNKhyV1ATn0mYCfr95vum/e7voda5LZQ+NryBTdB/4yI/zR3s9+TF4 MBDzNrtcz3Yrce9GxS3R2+e8utd3qKx8b3umQiofLALdTTUy0vTuHXviMTsK WYaOCGuKTRK05tqRFtlgB9XBvL4xCrb1htnOaHm2rwvbisLSn6XkmIUOtu0s K7B4L3GRSYUIaNz0tlfMTk7mF/o1yizqgGgYRLkfcLYcUEuwnTDCwGvHfflE QWjPILsSN3rH/P+QSLPSy+wYHI6m91D3vfoy74KhL7VClmk77ER6CBSt9fzU ZILVuihUlaIvaPW9XOUgYt+qUsUIw3R1t1KioXb13GUGamsVS9gsZgn6UquW TKBjRjr8orSFLzAwbOOkPFTCpbBSfl6CSE2KuFpImJxS30s6dKB9jyE02K88 lisFKrfl9dSqcCFE6bps4RIS+kyinFThIBanugNZ6UHZ1HPIl1fqPyzaGV97 9ndCNcCLeMPGpcpEMrWeicRVqWlW3nJnJpAX2oJkXhxPHERzDSRJp8Y80vU1 4sqw5td1hFtGczD/mgbK1bdUDIdG9syJvfbDRkg6mM/M2YaVTwQZ2l0sxPQ9 8LwP51bqRTRgsCqxTS6AjwAuU2OltxB6abytK1xT7rN1hwVHpKwGn5W4CJtE NyzI+hbvSX8T6SjVYJzALVQMWqyxJh72gJi47Dv/zAWG5ACyAx1NRSrd4QbL zrjeZa38wBUQ/CpR8VeR9qbnN+Cb/tZb4Q2ip+uwemqDrS3kwzZWOVqE3HkG 7ShYPpZR+GikzKTskihx44zeoiqYzdSSxU7yONjxmHHxKRC6453THZSLDTVp osRYvg9eJfMWGdPBHfJ7Sk6k4iCtfc75RJu9RWDZwAL/jfVdb/pJKZXrYlJA /1xbL0mdnIhl4kiUSxOXGjJWx6pUcWE/swmFym5pp9uvXu1FIjFLX9HoCqbt V9u0OBO6vIX5O4TUU4CP2Q2D1l2KrrXWowL/b0HUlr9VK9nqtiaePkxb2gox /vLLM2Uc6ZYR+EE9prCUcWnrONJtDh+Tmd5yWPGgAD6Hreq40lqSBvg8dAfq WFmFalnidmCiPrGR+eUntRLBzW2EkCu4ePHwGn0mdhTE2jK6orwNNYNBJS0m J/5z5+xmQ9iuYewRO8ydqtChhCEo4mpn3MBe+U3LdL2WQozBmyXgjjMYzDYR ZOfjWNMjN7iDgC4Wiaq+L3N+w5xHI9nIipA5Cr06PTjf+/70MDM1IPgxXsjZ wTB+8n4D9Y2M332m+2y1t6a5MapXXOZWsDiOfmY/OOMLh8M/6zhvNt9uYu/P T4Ye4PFmSysrvfrh4/GeMcYbGxvmQ7S66cOxPeJ2zlJfimPrhGPsGqErFnh5 0VahZ4KA7/sMBlf3MN0L9xoMJ5cz60AqHvpRs+7pVwchzcnqkt4Ro6ziJ5v0 TY3B5VVdjdTWiReECxhp3OSMMxVsL94nLOkpSXVVkVx9jLFJedKgeki54Und DeYTP+B0jp1ERdpArTyIA73j3MFChVyOGS2bRkqPem03Bj5TULcTCeQRiC2C GlXGl+Wsk0AenpluKiizE+BUmWhVKadSrlh6TOM+YeTRIATapfltqqpVh1A4 Sk2kgLLIK6a7gvUZoaWdaDIcXx48Y8UKoBQbGFM7/ielBZnkyESh4LBSHnRA mbDjgJB4+g/2iZ9h8sAc9sFV31m79S7KySi5FzI6yCOUfhOvO4I0B27G94eI msTmGA83KoSts6le3hSXn8w64QkddNF3U5KdxsU1m0zM459Wx44VSCYuwV2L 28U2PJxJEQ659qA9UwUO4S6iJME3XEkgbS7sES0SnlvXlqWcoMSBlQkXyri9 gKHGcbxdByvWS9kONUKaxtkKZkpwXO468BPaqXF2wB50Wq1veHKwZoLYZMS6 s4J49ce7QNIWg8yiipL/T/e61jCmS07qZnZ1UpZGB3WFIwufmTBV3BHGNEFg 1chIppJMjsrrOAfG8eCV6ppVkJLj8lXY3GH3dDjcOeZaRUwv7ro31RUXDrSQ srjO5APb44QHnjL91Q4I2Wf1K9Z6kmg70jQMQIXB/ZYrvLWA4CSYEL1rrh0r /AfsJWBAHkLql4UEIK8ebiqWIwMyx4x26hAmoumV6W7d0UGiGDSdaq6Z8NfZ EQr8O/KcssVRmX0sUd/B8zGCfXGIZiqNi82aa06DncjZXYAkt1nC/xbm8DSv rYtXxtzQC9O5YGkU3O7VPl8MHVvxGFcuq5pG+S1xHMY6CB0aSyV3qwAA7eBw CV8fGWDEz7JZP9QUEIGdQQnWFlmRmbC4WBRviXavij6/fGmUaLS4Iuw6XCEC BwFimsf2VL/J2QLqyzqc5reFePsR/pq81h0YU0lT+ms5ZUZoQLSUS68a57w6 GEAtvLZiXFev1zMqtbKj8o5cZ0No0MTrm4bZPRq8/jAg3ux48ETv2nekv91K Zdc195Sj4Sb5+BHJZ3QffIH09xcNp0vpv++57Atb4bQgJhA6zcXKlstEv6iW +aI0H/QXKX8pGkqnzWmJ9rlc9McD1Bi2KmbiRcCuuVhQdArSfLZyi7OAw6wk X3Edu9jVgFLSfX9dzspbVizFzn3s3SnyRKyy9+tZcmRM23jHsIHfpH4jCt/f AtHzg8iiRue02+1mF3RsIdKneQJPWJfAVHdHqC5WgWTcPLxdyofuzCCq0vut bvFZ/Kr3PQg/od1qMFanJItvDoKXeNay54vdFiGhxEhFfjB5xrmGDiXNnjj5 h7CAXq+tGoh9Tg+DVdg/4pNYjLzpKse3i1FCW6+JXQ3WBrm60Pg/2hJG2uc/ w9P/RGPJePmC/6Dxr5/ps730P7PZaLQ9os+vX9xzy5x7m+/5lkqnL2b52YwX 3iW58RyRJmi3xk9G/MGTfZIK3+iTRnbKXq89L6Xd/wfh2hdWKUbBpwsoEiXn w1OoeifBAKGvnNmCfZBwSxBqfrMl17HSvxhTX6n5dc7mYc9jciiJoDTngfqN TjSyJ+BSko0Aoq8tsJGbJGZz0D9d5RLZGM+yv8mzlI6+2erSH3xpuROGni09 KJ4BfMF/qKHjrNyrL1FS+XlSCyhSqGnKGxXn6YQsUClivNedUG2whWqBUFnC m2JSXCnYbbLG0elSwAET+NlXhqt5mwlD7BM+3ZCLXaqFg0mJ1u800aTeLHbT auTlh7hd52U3uHzRGsRhOwSICF1PcEtsureiRJyZ97H6koXOOsr2cmdSBNKR IkEE6i5GxKK27DXs+3kIMbWRkZVvsxWiZTsrws2a9kquO7/oOKuOuD0zHVXc Dr5VdNf7qOIpZ+49vOzNjY3e9uji/Xa+vbG9/fqbLfPKwNi7KwKsJwZn39lo /PaBl456oaOqGsB2hFMDsrPdg9ZhqLezFb/Hd7Liwy5NbpUoVnej1yH61N2g T08UWKHhbvZBLLAsiE4nmuGFGINr4j0+HFfna9ZL33vpr3l4wOKQUVycAiNd 51TMN4Rx8N0dmeNl0uiXCOjbvY2NbVpBBBH56Z9sehb8+mV7A79hhf8MyS6k Z05fBjBVl7MCFCVZPa3QHPx4mX3u1Rdqa/AjsXyefZpAP50n/yT6zdrdI+n1 GhPuy4TxfMlET4hHwnn6RzGtQmaEaaFxk4GChsD0xiHKxUSsDj3fvN00vsAZ g3gFhGbZKk7UWtb6iZdmbXfXnkiy/gWfdCa8wa9xJz8xhdBIZrA8Dfwzn191 BgudfE03e/o/pMgGnjOyfNtbe0EnS/PVt8xXO2FO5d6zi3/NvMvXIXU+l4D2 Ck2Ssjs0vhc+pzHKr80xox/um4/TGgfVt9HnT982Pgs/hE9lnZweZnHpJpSE S2YyiCs7nWy+Pul/vS4fLIve/t1m8jvAhCf6t4XdcQEh2p2/Le7O35wL/dfx ZPFxG8aCxgm+9tde1MmXfKyTBUrYcnoXSGN0eP+1z6us0orj2SoLvZ3s6HzQ /ahC5yIzEL/KOekXcsovckbGxe+HX4yb55u9nZ+PmfniKXaexNHLaTV5vBV+ b+fiAgEB7pVTfJ51c/pNGP/+0WCwjS/bWX86yo5gXJblDWgA+qO+Ke9AMOBG xm+8PdrTF94eZXsIj+NffzgOvyKz7PGEU/BXU8lFs7mjj3ck+In+kQfW2Q40 azcMjL1yejkvZbS9A32+Z3ftwehahtw7PrNn1e1tOcM9dhxJCGdI6csNh80+ hqU9OvUupq6akSeVv8U5ciFnqV8gPx74i2KAgXivjz7aowJpSMdsp/g4sQV9 7IZ3Gw1aO+t+XNr8I5Qqoe2+wVKMBIwQ8mDfF7MfhU/tFxOUKg0rE4eG/aFP cD91dnYHl71qVGQD4D+/UewNzmz7i8mNRN7uSf3RwfyCmCLajFFZCW+IXKr8 2uHxrr4UJSGLd3A3r6Xl0eDMFnCk7g8D0fJKv/HOXJ9ar9enNM1d6eDcloSu 9IizVka1mdaq+/HpdgLzO4f58ZF1zGsriZU9IljBgzHpmj1ttOUJm5A3l2kG pX2/2b7/dPvhwFtfEPUaSnWvEceOcgtQb22ynFWXloMTgzaXvHALbtw1/PRF ptKmTbWWPB02nkrYDD86GzSenampkUlPGfWx19aJHZaxIvnAKIVzN04pBk4p BkX+qZ1I/OBH5Id5bgbRGK/Odmw/BOd2xOoRb8KZI/SZere0YjOi7qydLTkK 5U0RZ7ivTWXR8YlU2kqXjjXxVKm3+VT1EOGUDk92Gu3EbrcDv2HOqiGtvm9t 9b05EksruaKspUQLN72ox6rd2KkRZcSeQxE8pJ/heby81zbm+eOdDnTms5FM lgpZfXi/1f44g9MMK/DFR8swyNJaME2XRweNRwfBuVManIYGauKJ9/yjvc+E 4eC/5+Wdw9Ipd4NQfxwcLjxIz83Hs5MTm/PHMVF9QpBxyQbHk+qBDqIE6u15 Hit78a8njqZGLkQdvTMt8mTigb48RVf+enbYaGUQBm8R6LY0/mlx9IPPM5gx ZOaLEwGzgsDWcTG6lmKTv2yLa24x+nblKh/XxYolAGWB/wZuAOJFyZnRJHZ0 8olYo2mZT7LDHG7/ney7ipD2z/mYxNZJJzsnoZfDKIY5wpmPpsV19qGc1p8e O9nZ//7PqLymfTgqyotOdlpefhojfHJ/PftQTadl3XEebz+flITWdLdewoF3 PC472W6V/TjvZD/N6SgTWOh+uhYr0X5xUU3zm2x3Op+gUAKUbJiChByBJ5Mo rKRwB7955UkjGZWtxgoccEOQF3uxINoYq2dby3clHf1KtyYBhwd2S0VF6DQm 7oOsU/Fwc+tuZ3yfTytCPDq6Ob/wAQD/cLk7hSevdTmdXXdHviAC1s8V8YxX 89uSQEnfRnm08GxW33dzTnSL1rQx5W01u3nMfiwll4f1imI3odcOYTw9PLim bfKiMPCEjLrCCN9VdXFHDHQ+rh6KR29IfHzcF5ZC49KYl+Wk/lSGPAB3dWjX BMd39MbRvETc4Mjf2Nlf0vpgWn7K/gI38E72F0CQUHCczwllYSlV9KDzW42j eR4fDI+8v/8D8YJMOfcxAgA=[rfced] Abbreviations. (To view the updates to this section, which was moved to Section 2.2, we suggest using the alternative diff file: https://www.rfc-editor.org/authors/rfc9889-alt-diff.html) a) FYI, we updated the expansion of GPRS to use "General" rather than "Generic". Original: Generic Packet Radio Service Updated: General Packet Radio Service b) FYI, this entry appeared in the original, but it was not used elsewhere in the document, so it has been removed. UE: User Equipment c) The abbreviation "DM" appears in Figure 7 but not elsewhere in the document. Will readers know this abbreviation (perhaps "data model")? May we add the expansion to the list of abbreviations in Section 2.2? d) "AMF" appears in Figure 8 but not elsewhere in the document. How should this be expanded? e) Will readers understand "LxVPN"? It only appears once in the document. May we update for clarity as follows? Original: The correlation between an LxVPN instance and a Network Slice Service is maintained using "parent-service- id" attribute (Section 7.3 of [RFC9182]). Perhaps: The correlation between an L3VPN/L2VPN instance and a Network Slice Service is maintained using "parent-service- id" attribute (Section 7.3 of [RFC9182]). f) FYI, we have added expansions for the following abbreviations per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each expansion in the document carefully to ensure correctness. MACsec: Media Access Control Security MNO: Mobile Network Operator --> <!-- [rfced] Terminology a) "DC1" and "DC2" (no space) are used in the text in Section 7, but "DC 1" and "DC 2" (with space) are used in Figure 30 and Tables 1 and 2. Should these be consistent? If so, let us know which form is preferred. b) Please review the names of domains and let us know if any updates are needed for consistency. Some examples: Provider Orchestration Domain (Figure 3) provider orchestration domain Provider Network Orchestration domain Customer Orchestration Domain (Figure 3) Customer Site Orchestration domain 3GPP orchestration domain 3GPP domains Orchestration (Figure 6) provider and customer TN domains customer and provider orchestration domains c) We note capitalization inconsistencies in the terms below throughout the text. Should these be uniform? If so, please let us know which form is preferred. transport network Transport Network mobile network Mobile Network d) We see a few instances of "5Q QoS". Should these be updated to "5G QoS"? e) Should "Slice Services" (uppercase) in these sentences be updated to "slice services" (lowercase)? It seems that "slice service" is lowercase in general text and capitalized in the terms "Network Slice Service" and "5G Slice Service". Original: The objective of Transport Network Slicing is to isolate, guarantee, or prioritize Transport Network resources for Slice Services. ... Putting in place adequate automation means to realize Network Slices (including the adjustment of Slice Services to Network Slices mapping) would ease slice migration operations. f) Should "slice" be lowercase or uppercase in these contexts? Transport Network Slice TN slice 5G Network Slice 5G slice g) In general text, we see both "Network Slice" (uppercase) and "network slice" (lowercase). We suggest using the lowercase form when used on its own (the capitalized form is used consistently in the terms "RFC 9543 Network Slice", "Network Slice Service", and "5G Network Slice"). This seems to follow the usage in RFC 9543. Let us know your thoughts. Some examples are below. Examples of uppercase "Network Slice": A TN slice might be considered as a variant of horizontal composition of Network Slices mentioned in Appendix A.6 of [RFC9543]. ... The use of VPNs for realizing Network Slices is briefly described in Appendix A.4 of [RFC9543]. Examples of lowercase "network slice": The document is not intended to be a BCP and does not claim to specify mandatory mechanisms to realize network slices. ... * Providers may want to enable differentiated failure detect and repair features for a subset of network slices. --> <!-- [rfced] Please review the "Inclusive Language" portion of the online Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> and let us know if any changes are needed. Updates of this nature typically result in more precise language, which is helpful for readers. Note that our script did not flag any words in particular, but this should still be reviewed as a best practice. --> <!-- [rfced] We made the following changes regarding the <aside> element. The <aside> element is defined as "a container for content that is semantically less important or tangential to the content that surrounds it" (https://authors.ietf.org/en/rfcxml-vocabulary#aside). a) We placed the following note in Section 5.2.2 in the <aside> element. Original: Note: The numbers indicated in Figure 23 (S-NSSAI, 5QI, DSCP, queue, etc.) are provided for illustration purposes only and should not be considered as deployment guidance. Updated: | Note: The numbers indicated in Figure 23 (S-NSSAI, 5QI, DSCP, | queue, etc.) are provided for illustration purposes only and | should not be considered as deployment guidance. b) The following text in Section 3.3.5 appears in the <aside> element. We added "Note:". Original: | In order to keep the figures simple, only one AC and single- | homed CEs are represented. Also, the underlying bearers are | not represented in most of the figures. However, this document | does not exclude the instantiation of multiple ACs between a CE | and a PE nor the presence of CEs that are attached to more than | one PE. Updated: | Note: In order to keep the figures simple, only one AC and single- | homed CEs are represented. Also, the underlying bearers are | not represented in most of the figures. However, this document | does not exclude the instantiation of multiple ACs between a CE | and a PE nor the presence of CEs that are attached to more than | one PE. --> <!-- [rfced] Please review all the SVG figures in the HTML/PDF outputs to ensure that they convey the same information as the ascii-art in the TXT output. We have included some notes below about particular figures. If changes are needed, please either update the SVG in the XML file directly or provide updated SVG for the affected figure(s). a) Note that "===" appears as a solid double line in the SVG in the HTML and PDF outputs. Are any updates needed for this sentence in Section 3.3.5? Original: For example, the bearer is illustrated with "===" in Figures 4 and 5. b) Figure 4: Do the boxes labeled "SW" and "PE" appear correctly in the SVG? c) Figure 5: Do the boxes labeled "CE", "Mngd CE", and "DC GW" appear correctly in the SVG? d) Figures 12, 15, and 16: - In the SVG, the lines do not extend all the way to the boxes labeled "PE". - The "+" signs that appear in the ascii-art do not appear in the SVG. Note that Figure 12 has a legend that includes "+", but "+" does not appear in the SVG. - Figure 12: Please consider changing each asterisk to a different character and running aasvg again to get new SVG. It seems "+*" together does not appear as you intended in the SVG. Please see issue #20 for aasvg (https://github.com/martinthomson/aasvg/issues/20) where using a Unicode character is a suggested workaround. e) Figure 23: - The boxes in the SVG that contain "5QI=", "DSCP=", and "TN QoS Class" are not closed in the SVG. Will these be confusing for readers? - In the "NF-A" box, a pipe character is spaced over. We can fix it in the ascii-art, but we are unable to fix it in the SVG. f) Figures 24 and 25: - Do the boxes for Slice 1, Slice 2, and Slice 3 look okay in the SVG? They are missing some corners. - Do the boxes under "Slice Policer" in Figure 25 look as expected in the SVG? g) Figure 26: - The bottom right of the figure looks off, i.e., "/|\" in the txt output. Should it be moved over one space to the left? We can fix this in the ascii-art if needed, but we are unable to fix the SVG. - The "..." in the txt output does not seem to be reflected in the SVG output. There is a solid line with ".." in the SVG. h) Figure 27: Does the ">>" in the ascii-art appear as expected in the SVG? i) Figure 30: The filled-in dot in the SVG overlaps letters in the PE boxes. This should be updated. Please see the note above regarding Figure 12 for more information, assuming this SVG was created using aasvg. j) Figure 32: - Does the arrow "v" above the "^" above "MIot (SST=3)" look as expected in the SVG? - Do the PE and NF boxes look okay in the SVG? --> </rfc>