rfc9889v2.txt		rfc9889.txt
	skipping to change at line 14 ¶		skipping to change at line 14 ¶
	Category: Informational R. Roberts, Ed.		Category: Informational R. Roberts, Ed.
	ISSN: 2070-1721 Nokia		ISSN: 2070-1721 Nokia
	J. Lucek		J. Lucek
	Juniper Networks		Juniper Networks
	M. Boucadair, Ed.		M. Boucadair, Ed.
	Orange		Orange
	L. Contreras		L. Contreras
	Telefonica		Telefonica
	October 2025		October 2025
	Realization of Network Slices for 5G Networks Using Current IP/MPLS		A Realization of Network Slices for 5G Networks Using Current IP/MPLS
	Technologies		Technologies
	Abstract		Abstract
	Network slicing is a feature that was introduced by the 3rd		Network slicing is a feature that was introduced by the 3rd
	Generation Partnership Project (3GPP) in Mobile Networks.		Generation Partnership Project (3GPP) in Mobile Networks.
	Realization of 5G slicing implies requirements for all mobile		Realization of 5G slicing implies requirements for all mobile
	domains, including the Radio Access Network (RAN), Core Network (CN),		domains, including the Radio Access Network (RAN), Core Network (CN),
	and Transport Network (TN).		and Transport Network (TN).
	skipping to change at line 134 ¶		skipping to change at line 134 ¶
	and how such slices are stitched to Transport Network resources in a		and how such slices are stitched to Transport Network resources in a
	customer site in the context of Transport Network Slices (Figure 1).		customer site in the context of Transport Network Slices (Figure 1).
	The realization of an RFC 9543 Network Slice (i.e., connectivity with		The realization of an RFC 9543 Network Slice (i.e., connectivity with
	performance commitments) involves the provider network and partially		performance commitments) involves the provider network and partially
	the AC (the Provider Edge (PE) side of the AC). This document		the AC (the Provider Edge (PE) side of the AC). This document
	assumes that the customer site infrastructure is over-provisioned and		assumes that the customer site infrastructure is over-provisioned and
	involves short distances (low latency) where basic QoS/scheduling		involves short distances (low latency) where basic QoS/scheduling
	logic is sufficient to comply with the Service Level Objectives		logic is sufficient to comply with the Service Level Objectives
	(SLOs).		(SLOs).
	|------------------TN Slice------------------|		|------------Transport Network Slice---------|
	RFC 9543 Network Slice		RFC 9543 Network Slice
	.-----SDP Type 3----.		.-----SDP Type 3----.
	| .- SDP Type 4-. |		| .- SDP Type 4-. |
	| | | |		| | | |
	v v v v		v v v v
	+------------+ +---------------+ +------------+		+------------+ +---------------+ +------------+
	| Customer | | Provider | | Customer |		| Customer | | Provider | | Customer |
	| Site 1 | | Network | | Site 2 |		| Site 1 | | Network | | Site 2 |
	| | +-+--+ +-+--+ | |		| | +-+--+ +-+--+ | |
	skipping to change at line 248 ¶		skipping to change at line 248 ¶
	3GPP: 3rd Generation Partnership Project		3GPP: 3rd Generation Partnership Project
	5GC: 5G Core		5GC: 5G Core
	5QI: 5G QoS Indicator		5QI: 5G QoS Indicator
	A2A: Any-to-Any		A2A: Any-to-Any
	AC: Attachment Circuit		AC: Attachment Circuit
			AMF: Access and Mobility Management Function
	CE: Customer Edge		CE: Customer Edge
	CIR: Committed Information Rate		CIR: Committed Information Rate
	CS: Customer Site		CS: Customer Site
	CN: Core Network		CN: Core Network
	CoS: Class of Service		CoS: Class of Service
	skipping to change at line 270 ¶		skipping to change at line 272 ¶
	CU: Centralized Unit		CU: Centralized Unit
	CU-CP: Centralized Unit Control Plane		CU-CP: Centralized Unit Control Plane
	CU-UP: Centralized Unit User Plane		CU-UP: Centralized Unit User Plane
	DC: Data Center		DC: Data Center
	DDoS: Distributed Denial of Service		DDoS: Distributed Denial of Service
			DM: Data Model
	DSCP: Differentiated Services Code Point		DSCP: Differentiated Services Code Point
	eCPRI: enhanced Common Public Radio Interface		eCPRI: enhanced Common Public Radio Interface
	FIB: Forwarding Information Base		FIB: Forwarding Information Base
	GPRS: General Packet Radio Service		GPRS: General Packet Radio Service
	gNB: gNodeB		gNB: gNodeB
	skipping to change at line 427 ¶		skipping to change at line 431 ¶
	3.2.1. 5G Network Slicing		3.2.1. 5G Network Slicing
	In [TS-28.530], the 3GPP defines 5G Network Slicing as an approach:		In [TS-28.530], the 3GPP defines 5G Network Slicing as an approach:
	| where logical networks/partitions are created, with appropriate		| where logical networks/partitions are created, with appropriate
	| isolation, resources and optimized topology to serve a purpose or		| isolation, resources and optimized topology to serve a purpose or
	| service category (e.g. use case/traffic category, or for MNO		| service category (e.g. use case/traffic category, or for MNO
	| internal reasons) or customers (logical system created "on		| internal reasons) or customers (logical system created "on
	| demand").		| demand").
	These resources are from the TN, RAN, CN domains, and the underlying		These resources are from the TN, RAN, and CN domains together with
	infrastructure.		the underlying infrastructure.
	Section 3.1 of [TS-28.530] defines a 5G Network Slice as:		Section 3.1 of [TS-28.530] defines a 5G Network Slice as:
	| a logical network that provides specific network capabilities and		| a logical network that provides specific network capabilities and
	| network characteristics, supporting various service properties for		| network characteristics, supporting various service properties for
	| network slice customers.		| network slice customers.
	3.2.2. Transport Network Slicing		3.2.2. Transport Network Slicing
	The term "Transport Network Slice" refers to a slice in the Transport		The term "Transport Network Slice" refers to a slice in the Transport
	skipping to change at line 716 ¶		skipping to change at line 720 ¶
	'-+---+---'		'-+---+---'
	| |		| |
	v |		v |
	.-------------. |		.-------------. |
	| 3GPP domains | |		| 3GPP domains | |
	.----------+ Orchestration +-)---------------------------.		.----------+ Orchestration +-)---------------------------.
	| | (RAN and CN) | | |		| | (RAN and CN) | | |
	| '-------------' | |		| '-------------' | |
	| v |		| v |
	| .-----------------------------------------------. |		| .-----------------------------------------------. |
	| | TN Orchestration | |		| | Transport Network Orchestration | |
	| | +--------------+ +-----------+ +--------------+ | |		| | +--------------+ +-----------+ +--------------+ | |
	| | |Customer Site | |RFC9543 NSC| |Customer Site | | |		| | |Customer Site | |RFC9543 NSC| |Customer Site | | |
	| | |Orchestration | | | |Orchestration | | |		| | |Orchestration | | | |Orchestration | | |
	| | +--------------+ +-----------+ +--------------+ | |		| | +--------------+ +-----------+ +--------------+ | |
	| '---|-------------------|---------------------|-' |		| '---|-------------------|---------------------|-' |
	| | | | |		| | | | |
	| | | | |		| | | | |
	| v v v |		| v v v |
	+--|----------+ +-----------------+ +-------|--+		+--|----------+ +-----------------+ +-------|--+
	| | | | Provider | | | |		| | | | Provider | | | |
	skipping to change at line 738 ¶		skipping to change at line 742 ¶
	| +--+ +----+ AC | | | | AC | NF |<-+ |		| +--+ +----+ AC | | | | AC | NF |<-+ |
	| |NF+....+ CE +------+ PE | | PE +------+ (CE)| |		| |NF+....+ CE +------+ PE | | PE +------+ (CE)| |
	| +--+ +----+ | | | | +-----+ |		| +--+ +----+ | | | | +-----+ |
	| | +----+ +----+ | |		| | +----+ +----+ | |
	| Customer | | | | Customer |		| Customer | | | | Customer |
	| Site | | | | Site |		| Site | | | | Site |
	+-------------+ +-----------------+ +----------+		+-------------+ +-----------------+ +----------+
	RFC 9543		RFC 9543
	|-----Network Slice---|		|-----Network Slice---|
	|--------------------TN Slice-------------------|		|-------------Transport Network Slice-----------|
	Figure 6: 5G End-to-End Slice Orchestration with TN		Figure 6: 5G End-to-End Slice Orchestration with TN
	The various orchestrations depicted in Figure 6 encompass the 3GPP's		The various orchestrations depicted in Figure 6 encompass the 3GPP's
	Network Slice Subnet Management Function (NSSMF) mentioned, for		Network Slice Subnet Management Function (NSSMF) mentioned, for
	instance, in Figure 5 of [NS-APP].		instance, in Figure 5 of [NS-APP].
	3.4.2. Transport Network Segments and Network Slice Instantiation		3.4.2. Transport Network Segments and Network Slice Instantiation
	The concept of distributed PE (Section 3.3.4) assimilates the CE-		The concept of distributed PE (Section 3.3.4) assimilates the CE-
	skipping to change at line 835 ¶		skipping to change at line 839 ¶
	single 5G Enhanced Mobile Broadband (eMBB) network slice. It is		single 5G Enhanced Mobile Broadband (eMBB) network slice. It is
	important to note that this mapping can serve as an interim step		important to note that this mapping can serve as an interim step
	to M-to-N mapping. Further details about this scheme are		to M-to-N mapping. Further details about this scheme are
	described in Section 3.6.		described in Section 3.6.
	M-to-1 mapping: Multiple 5G Network Slices may rely upon the same		M-to-1 mapping: Multiple 5G Network Slices may rely upon the same
	Transport Network Slice. In such a case, the Service Level		Transport Network Slice. In such a case, the Service Level
	Agreement (SLA) differentiation of slices would be entirely		Agreement (SLA) differentiation of slices would be entirely
	controlled at the 5G control plane, for example, with appropriate		controlled at the 5G control plane, for example, with appropriate
	placement strategies. This use case is illustrated in Figure 9,		placement strategies. This use case is illustrated in Figure 9,
	where a User Plane Function (UPF) for the Ultra-Reliable Low-		where a UPF for the Ultra-Reliable Low-Latency Communication
	Latency Communication (URLLC) slice is instantiated at the edge		(URLLC) slice is instantiated at the edge cloud, close to the gNB
	cloud, close to the gNB CU-UP, to improve latency and jitter		CU-UP, to improve latency and jitter control. The 5G control
	control. The 5G control plane and the UPF for the eMBB slice are		plane and the UPF for the eMBB slice are instantiated in the
	instantiated in the regional cloud.		regional cloud.
	M-to-N mapping: The mapping of 5G to Transport Network Slice		M-to-N mapping: The mapping of 5G to Transport Network Slice
	combines both approaches with a mix of shared and dedicated		combines both approaches with a mix of shared and dedicated
	associations.		associations.
	In this scenario, a subset of the Transport Network Slices can be		In this scenario, a subset of the Transport Network Slices can be
	intended for sharing by multiple 5G Network Slices (e.g., the		intended for sharing by multiple 5G Network Slices (e.g., the
	control plane Transport Network Slice is shared by multiple 5G		control plane Transport Network Slice is shared by multiple 5G
	Network Slices).		Network Slices).
	In practice, for operational and scaling reasons, M-to-N mapping		In practice, for operational and scaling reasons, M-to-N mapping
	would typically be used, with M much greater than N.		would typically be used, with M much greater than N.
	+---------------------------------------------------------------+		+---------------------------------------------------------------+
	| 5G Slice eMBB |		| 5G Network Slice eMBB |
	| +------------------------------------+ |		| +------------------------------------+ |
	| +-----+ N3 | +--------------------------------+ | N3 +-----+ |		| +-----+ N3 | +--------------------------------+ | N3 +-----+ |
	| |CU-UP+------+ TN Slice UP_eMBB +-------+ UPF | |		| |CU-UP+------+Transport Network Slice UP_eMBB +-------+ UPF | |
	| +-----+ | +--------------------------------+ | +-----+ |		| +-----+ | +--------------------------------+ | +-----+ |
	| | | |		| | | |
	| +-----+ N2 | +--------------------------------+ | N2 +-----+ |		| +-----+ N2 | +--------------------------------+ | N2 +-----+ |
	| |CU-CP+------+ TN Slice CP +-------+ AMF | |		| |CU-CP+------+ Transport Network Slice CP +-------+ AMF | |
	| +-----+ | +--------------------------------+ | +-----+ |		| +-----+ | +--------------------------------+ | +-----+ |
	+------------|------------------------------------|-------------+		+------------|------------------------------------|-------------+
	| |		| |
	| Transport Network |		| Transport Network |
	+------------------------------------+		+------------------------------------+
	Figure 8: 1-to-N Mapping (Single 5G Network Slice to Multiple		Figure 8: 1-to-N Mapping (Single 5G Network Slice to Multiple
	Transport Network Slices)		Transport Network Slices)
	+-------------+		+-------------+
	skipping to change at line 884 ¶		skipping to change at line 888 ¶
	| |UPF_URLLC| |		| |UPF_URLLC| |
	| +-----+---+ |		| +-----+---+ |
	| | |		| | |
	+-------|-----+		+-------|-----+
	|		|
	+---------------+ +-------|----------------------+		+---------------+ +-------|----------------------+
	| | | | |		| | | | |
	| Cell Site | | +-----+--------------------+ | +--------------+		| Cell Site | | +-----+--------------------+ | +--------------+
	| | | | | | | Regional |		| | | | | | | Regional |
	| +-----------+ | | | | | | Cloud |		| +-----------+ | | | | | | Cloud |
	| |CU-UP_URLLC+-----+ | | | +----------+ |		| |CU-UP_URLLC+-----+ Transport Network | | | +----------+ |
	| +-----------+ | | | TN Slice ALL +-----+ 5GC CP | |		| +-----------+ | | | Slice ALL +-----+ 5GC CP | |
	| | | | | | | +----------+ |		| | | | | | | +----------+ |
	| +-----------+ | | | | | | |		| +-----------+ | | | | | | |
	| |CU-UP_eMBB +-----+ | | | +----------+ |		| |CU-UP_eMBB +-----+ | | | +----------+ |
	| +-----------+ | | | +-----+ UPF_eMBB | |		| +-----------+ | | | +-----+ UPF_eMBB | |
	+---------------+ | | | | | +----------+ |		+---------------+ | | | | | +----------+ |
	| +--------------------------+ | | |		| +--------------------------+ | | |
	| | +--------------+		| | +--------------+
	| Transport Network |		| Transport Network |
	+------------------------------+		+------------------------------+
	skipping to change at line 935 ¶		skipping to change at line 939 ¶
	dedicated Transport Network Slice for the user plane (TNS-UP2). The		dedicated Transport Network Slice for the user plane (TNS-UP2). The
	control plane of the first 5G Network Slice is also updated to		control plane of the first 5G Network Slice is also updated to
	integrate the second slice; the Transport Network Slice (TNS-CP) and		integrate the second slice; the Transport Network Slice (TNS-CP) and
	Network Functions (NF-CP) are shared.		Network Functions (NF-CP) are shared.
	The model described here, in which the control plane is shared among		The model described here, in which the control plane is shared among
	multiple slices, is likely to be common; it is not mandatory, though.		multiple slices, is likely to be common; it is not mandatory, though.
	Deployment models with a separate control plane for each slice are		Deployment models with a separate control plane for each slice are
	also possible.		also possible.
	Section 6.1.2 of [NG.113] specifies that the eMBB slice (SST-1 and no		Section 6.1.2 of [NG.113] specifies that the eMBB slice (SST=1 and no
	Slice Differentiator (SD)) should be supported globally. This 5G		Slice Differentiator (SD)) should be supported globally. This 5G
	Network Slice would be the first slice in any 5G deployment.		Network Slice would be the first slice in any 5G deployment.
	(1) Deployment of first 5G slice		(1) Deployment of first 5G Network Slice
	+---------------------------------------------------------------+		+---------------------------------------------------------------+
	| First 5G Slice |		| First 5G Network Slice |
	| |		| |
	| +------------------------------+ |		| +------------------------------+ |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	| |NF-CP+------+ CP TN Slice (TNS-CP) +------+NF-CP| |		| |NF-CP+------+ TNS-CP +------+NF-CP| |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	| | | |		| | | |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	| |NF-UP+------+ UP TN Slice (TNS-UP1) +------+NF-UP| |		| |NF-UP+------+ TNS-UP1 +------+NF-UP| |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	+----------------|------------------------------|---------------+		+----------------|------------------------------|---------------+
	| |		| |
	| Transport Network |		| Transport Network |
	+------------------------------+		+------------------------------+
	(2) Deployment of additional 5G slice with shared control plane		(2) Deployment of additional 5G Network Slice with shared Control
			Plane
	+---------------------------------------------------------------+		+---------------------------------------------------------------+
	| First 5G Slice |		| First 5G Network Slice |
	| |		| |
	| +------------------------------+ |		| +------------------------------+ |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	| |NF-CP+------+ CP TN Slice (TNS-CP) +------+NF-CP| |		| |NF-CP+------+ TNS-CP +------+NF-CP| |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	| SHARED | (SHARED) | SHARED |		| SHARED | (SHARED) | SHARED |
	| | | |		| | | |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	| |NF-UP+------+ UP TN Slice (TNS-UP1) +------+NF-UP| |		| |NF-UP+------+ TNS-UP1 +------+NF-UP| |
	| +-----+ | +--------------------------+ | +-----+ |		| +-----+ | +--------------------------+ | +-----+ |
	+----------------|------------------------------|---------------+		+----------------|------------------------------|---------------+
	| |		| |
	| Transport Network |		| Transport Network |
	| |		| |
	+----------------|------------------------------|---------------+		+----------------|------------------------------|---------------+
	| | | |		| | | |
	| +------+ | +--------------------------+ | +------+ |		| +------+ | +--------------------------+ | +------+ |
	| |NF-UP2+-----+ UP TN Slice (TNS-UP2) +-----+NF-UP2| |		| |NF-UP2+-----+ TNS-UP2 +-----+NF-UP2| |
	| +------+ | +--------------------------+ | +------+ |		| +------+ | +--------------------------+ | +------+ |
	| | | |		| | | |
	| +------------------------------+ |		| +------------------------------+ |
	| |		| |
	| Second 5G Slice |		| Second 5G Network Slice |
	+---------------------------------------------------------------+		+---------------------------------------------------------------+
	Figure 10: First and Subsequent Slice Deployment		Figure 10: First and Subsequent Slice Deployment
	Transport Network Slice mapping policies can be enforced by an		Transport Network Slice mapping policies can be enforced by an
	operator (e.g., provided to a TN Orchestration or 5G NSO) to		operator (e.g., provided to a TN Orchestration or 5G NSO) to
	determine whether existing Transport Network Slices can be reused for		determine whether existing Transport Network Slices can be reused for
	handling a new Slice Service creation request. Providing such a		handling a new Slice Service creation request. Providing such a
	policy is meant to better automate the realization of 5G Network		policy is meant to better automate the realization of 5G Network
	Slices and minimize the realization delay that might be induced by		Slices and minimize the realization delay that might be induced by
	skipping to change at line 1151 ¶		skipping to change at line 1156 ¶
	+------+ | +-+----+ Provider +---+--+ | +-----+ | +------+		+------+ | +-+----+ Provider +---+--+ | +-----+ | +------+
	| | v | | | | v | | v | |		| | v | | | | v | | v | |
	| x------x * | | * x------x x.......x |		| x------x * | | * x------x x.......x |
	| NF x------x * PE | | PE * x------xL2/L3x.......x NF |		| NF x------x * PE | | PE * x------xL2/L3x.......x NF |
	| x------x * | | * x------x x.......x |		| x------x * | | * x------x x.......x |
	| | | | | | | | | |		| | | | | | | | | |
	+------+ AC +--+---+ Network +---+--+ AC +-----+ +------+		+------+ AC +--+---+ Network +---+--+ AC +-----+ +------+
	| |		| |
	+------------------+		+------------------+
	x Logical interface represented by a VLAN on a physical interface		x Logical interface represented by a VLAN on a physical interface
	* SDP
			* SDP
	Figure 12: Example of 5G Network Slice with VLAN Handoff		Figure 12: Example of 5G Network Slice with VLAN Handoff
	Providing End-to-End Connectivity		Providing End-to-End Connectivity
	Each VLAN represents a distinct logical interface on the ACs and		Each VLAN represents a distinct logical interface on the ACs and
	hence provides the possibility to place these logical interfaces in		hence provides the possibility to place these logical interfaces in
	distinct Layer 2 or Layer 3 service instances and implement		distinct Layer 2 or Layer 3 service instances and implement
	separation between slices via service instances. Since the 5G		separation between slices via service instances. Since the 5G
	interfaces are IP-based interfaces (with the exception of the F2		interfaces are IP-based interfaces (with the exception of the F2
	fronthaul interface, where eCPRI with Ethernet encapsulation is		fronthaul interface, where eCPRI with Ethernet encapsulation is
	skipping to change at line 1332 ¶		skipping to change at line 1338 ¶
	BGP VPN BGP VPN BGP VPN		BGP VPN BGP VPN BGP VPN
	COM=1, L=A" COM=1, L=A' COM=1, L=A		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=2, L=B" COM=2, L=B' COM=2, L=B
	COM=3, L=C" COM=3, L=C' COM=3, L=C		COM=3, L=C" COM=3, L=C' COM=3, L=C
	<-----------><-------------><------------>		<-----------><-------------><------------>
	nhs nhs nhs nhs		nhs nhs nhs nhs
	VLANs		VLANs
	service instances service instances representing		service instances service instances representing
	representing slices representing slices slices		representing slices representing slices slices
	| | |		| | |
	+---+ | +--------------+ +-|--------|----------+		+---+ | +-------------+ +-|--------|----------+
	| | | | Provider | | | | |		| | | | Provider | | | | |
	| +-+--v-+ +-+---+ +--+--+ +-+-v----+ v +-----+ |		| +-+--v-+ +--+--+ +--+--+ +-+-v----+ v +-----+ |
	| | # | | * | | * | | #<><>x......x | |		| | # | | * | | * | | #<><>x......x | |
	| | NF # +------+ * PE| |PE * +------+ #<><>x......x NF | |		| | NF # +------+ * PE| |PE * +------+ #<><>x......x NF | |
	| | # | AC | * | | * | AC | #<><>x......x | |		| | # | AC | * | | * | AC | #<><>x......x | |
	| +--+---+ +-+---+ +---+-+ +-+------+ +-----+ |		| +--+---+ +--+--+ +--+--+ +-+------+ +-----+ |
	| CS1| | Network | | L2/L3 CS2 |		| CS1| | Network | | L2/L3 CS2 |
	+----+ +---------------+ +---------------------+		+----+ +-------------+ +---------------------+
	x Logical interface represented by a VLAN on a physical interface		x Logical interface represented by a VLAN on a physical interface
	# Service instances (with unique MPLS labels)		# Service instances (with unique MPLS labels)
	* SDP		* SDP
	Figure 15: Example of MPLS Handoff with Option B		Figure 15: Example of MPLS Handoff with Option B
	MPLS labels are allocated dynamically in Option B deployments, where,		MPLS labels are allocated dynamically in Option B deployments, where,
	at the domain boundaries, service prefixes are reflected with next-		at the domain boundaries, service prefixes are reflected with next-
	hop self (nhs), and a new label is dynamically allocated, as shown in		hop self (nhs), and a new label is dynamically allocated, as shown in
	skipping to change at line 1413 ¶		skipping to change at line 1419 ¶
	<------ <------ <------		<------ <------ <------
	BGP LU BGP LU BGP LU		BGP LU BGP LU BGP LU
	CS2, L=X" CS2, L=X' CS2, L=X		CS2, L=X" CS2, L=X' CS2, L=X
	<-----------><--------------><---------->		<-----------><--------------><---------->
	nhs nhs nhs nhs		nhs nhs nhs nhs
	VLANs		VLANs
	service instances service instances representing		service instances service instances representing
	representing slices representing slices slices		representing slices representing slices slices
	| | |		| | |
	+---+ | +--------------+ +-|--------|----------+		+---+ | +-------------+ +-|--------|----------+
	| | | | Provider | | | | |		| | | | Provider | | | | |
	| +-+-v-+ +-+---+ +--+--+ +-+-v----+ v +-----+ |		| +-+-v-+ +--+--+ +--+--+ +-+-v----+ v +-----+ |
	| | # | | * | | * | | #<><>x......x | |		| | # | | * | | * | | #<><>x......x | |
	| |NF # +-------+ * PE| |PE * +------+ #<><>x......x NF | |		| |NF # +-------+ * PE| |PE * +------+ #<><>x......x NF | |
	| | # | AC | * | | * | AC | #<><>x......x | |		| | # | AC | * | | * | AC | #<><>x......x | |
	| +--+--+ +-+---+ +---+-+ +-+------+ +-----+ |		| +--+--+ +--+--+ +--+--+ +-+------+ +-----+ |
	| CS1| | Network | | L2/L3 CS2 |		| CS1| | Network | | L2/L3 CS2 |
	+----+ +---------------+ +---------------------+		+----+ +-------------+ +---------------------+
	x Logical interface represented by a VLAN on a physical interface		x Logical interface represented by a VLAN on a physical interface
	# Service instances (with unique MPLS label)		# Service instances (with unique MPLS label)
	* SDP		* SDP
	Figure 16: Example of MPLS Handoff with Option C		Figure 16: Example of MPLS Handoff with Option C
	This architecture requires an end-to-end Label Switched Path (LSP)		This architecture requires an end-to-end Label Switched Path (LSP)
	leading from a packet's ingress node inside one customer site to its		leading from a packet's ingress node inside one customer site to its
	egress inside another customer site, through a provider network.		egress inside another customer site, through a provider network.
	skipping to change at line 1702 ¶		skipping to change at line 1708 ¶
	* PIR: Peak Information Rate (i.e., maximum bandwidth)		* PIR: Peak Information Rate (i.e., maximum bandwidth)
	These parameters define the traffic characteristics of the slice and		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.		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		Based on these parameters, the provider network's inbound policy can
	be implemented using one of following options:		be implemented using one of following options:
	* 1r2c (single-rate two-color) rate limiter		* 1r2c (single-rate two-color) rate limiter
	This is the most basic rate limiter, described in Section 2.3 of		This is the most basic rate limiter, described in Section 2.3 of
	[RFC2475]. At the SDP, it meters a traffic stream of a given		[RFC2475] (though not termed “1r2c” in that document). At the
	slice and marks its packets as in-profile (below CIR being		SDP, it meters a traffic stream of a given slice and marks its
	enforced) or out-of-profile (above CIR being enforced). In-		packets as in-profile (below CIR being enforced) or out-of-profile
	profile packets are accepted and forwarded. Out-of-profile		(above CIR being enforced). In-profile packets are accepted and
	packets are either dropped right at the SDP (hard rate limiting)		forwarded. Out-of-profile packets are either dropped right at the
	or re-marked (with different MPLS TC or DSCP TN markings) to		SDP (hard rate limiting) or re-marked (with different MPLS TC or
	signify "this packet should be dropped in the first place, if		DSCP TN markings) to signify "this packet should be dropped in the
	there is congestion" (soft rate limiting), depending on the		first place, if there is congestion" (soft rate limiting),
	business policy of the provider network. In the latter case,		depending on the business policy of the provider network. In the
	while packets above CIR are forwarded at the SDP, they are subject		latter case, while packets above CIR are forwarded at the SDP,
	to being dropped during any congestion event at any place in the		they are subject to being dropped during any congestion event at
	provider network.		any place in the provider network.
	* 2r3c (two-rate three-color) rate limiter		* 2r3c (two-rate three-color) rate limiter
	This was initially defined in [RFC2698], and an improved version		This was initially defined in [RFC2698], and an improved version
	is defined in [RFC4115]. In essence, the traffic is assigned to		is defined in [RFC4115]. In essence, the traffic is assigned to
	one of the these three categories:		one of the these three categories:
	- Green, for traffic under CIR		- Green, for traffic under CIR
	- Yellow, for traffic between CIR and PIR		- Yellow, for traffic between CIR and PIR
	skipping to change at line 1942 ¶		skipping to change at line 1948 ¶
	| |5QI=65 +->+DSCP=46 +----->+DSCP=46 +---+ | '------------' |		| |5QI=65 +->+DSCP=46 +----->+DSCP=46 +---+ | '------------' |
	| '-----' '-------' | | | '-------' | | |		| '-----' '-------' | | | '-------' | | |
	| .-----. .-------. | | | .-------. | | |		| .-----. .-------. | | | .-------. | | |
	| |5QI=7 +->+DSCP=10 +----->+DSCP=10 +-----+ |		| |5QI=7 +->+DSCP=10 +----->+DSCP=10 +-----+ |
	| '-----' '-------' | | | '-------' | |		| '-----' '-------' | | | '-------' | |
	+------------------------+ | '----------' |		+------------------------+ | '----------' |
	+--------------------------------------+		+--------------------------------------+
	Figure 23: Example of 3GPP QoS Mapped to TN QoS		Figure 23: Example of 3GPP QoS Mapped to TN QoS
	In current SDO progress of 3GPP (Release 17) and O-RAN, the mapping		In current SDO progress of 3GPP (Release 19) and O-RAN, the mapping
	of 5QI to DSCP is not expected to be in a per-slice fashion, where		of 5QI to DSCP is not expected to be in a per-slice fashion, where
	5QI-to-DSCP mapping may vary from 3GPP slice to 3GPP slice; hence,		5QI-to-DSCP mapping may vary from 3GPP slice to 3GPP slice; hence,
	the mapping of 5G QoS DSCP values to TN QoS Classes may be rather		the mapping of 5G QoS DSCP values to TN QoS Classes may be rather
	common.		common.
	Like in the 5QI-unaware model, the original IP header retains the		Like in the 5QI-unaware model, the original IP header retains the
	DSCP marking corresponding to 5QI (5G QoS Class), while the new		DSCP marking corresponding to 5QI (5G QoS Class), while the new
	header (MPLS or IPv6) carries the QoS marking related to TN QoS		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		Class. Based on the TN QoS Class marking, per-hop behavior for all
	aggregated 5G QoS Classes from all RFC 9543 Network Slices is		aggregated 5G QoS Classes from all RFC 9543 Network Slices is
	skipping to change at line 1987 ¶		skipping to change at line 1993 ¶
	of rates per class gives the rate per slice).		of rates per class gives the rate per slice).
	* Rate per slice (CIR or CIR+PIR), and rates per prioritized		* Rate per slice (CIR or CIR+PIR), and rates per prioritized
	(premium) traffic classes (CIR only). A best-effort traffic class		(premium) traffic classes (CIR only). A best-effort traffic class
	uses the bandwidth (within slice CIR/PIR) not consumed by		uses the bandwidth (within slice CIR/PIR) not consumed by
	prioritized classes.		prioritized classes.
	In the first option, the slice admission control is executed with		In the first option, the slice admission control is executed with
	traffic class granularity, as outlined in Figure 24. In this model,		traffic class granularity, as outlined in Figure 24. In this model,
	if a premium class doesn't consume all available class capacity, it		if a premium class doesn't consume all available class capacity, it
	cannot be reused by a non-premium (i.e., best effort) class.		cannot be reused by a non-premium class (i.e., best-effort).
	Class +---------+		Class +---------+
	policer +--|---+ |		policer +--|---+ |
	| | |		| | |
	5Q-QoS-A: CIR-1A ------<>-----------|--> S | |		5Q-QoS-A: CIR-1A ------<>-----------|--> S | |
	5Q-QoS-B: CIR-1B ------<>-----------|--> l | |		5Q-QoS-B: CIR-1B ------<>-----------|--> l | |
	5Q-QoS-C: CIR-1C ------<>-----------|--> i | |		5Q-QoS-C: CIR-1C ------<>-----------|--> i | |
	| c | |		| c | |
	| e | |		| e | |
	BE CIR/PIR-1D ------<>-----------|--> | A |		BE CIR/PIR-1D ------<>-----------|--> | A |
	skipping to change at line 3178 ¶		skipping to change at line 3184 ¶
	discussion on the benefits of structuring an address plan around both		discussion on the benefits of structuring an address plan around both
	services and geographic locations for more structured security		services and geographic locations for more structured security
	policies in a network.		policies in a network.
	Figure 32 uses the example from Figure 31 to demonstrate a slicing		Figure 32 uses the example from Figure 31 to demonstrate a slicing
	deployment, where the entire S-NSSAI is embedded into IPv6 addresses		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		used by NFs. Let us consider that "NF-A" has a set of tunnel
	termination points with unique per-slice IP addresses allocated from		termination points with unique per-slice IP addresses allocated from
	2001:db8:a::/96, while "NF-B" uses a set of tunnel termination points		2001:db8:a::/96, while "NF-B" uses a set of tunnel termination points
	with per-slice IP addresses allocated from 2001:db8:b::/96. This		with per-slice IP addresses allocated from 2001:db8:b::/96. This
	example shows two slices: "customer A eMBB" (SST=1, SD-00001) and		example shows two slices: "customer A eMBB" (SST=1, SD=00001) and
	"customer B MIoT" (SST=3, SD-00003). For "customer A eMBB" slice,		"customer B MIoT" (SST=3, SD=00003). For "customer A eMBB" slice,
	the tunnel IP addresses are auto-derived as the IP addresses		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		{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		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		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		simply adds {:0300:0003} as the last two octets. Leading zeros are
	not represented in the resulting IPv6 addresses as per [RFC5952].		not represented in the resulting IPv6 addresses as per [RFC5952].
	2001:db8:a::/96 (NF-A) 2001:db8:b::/96 (NF-B)		2001:db8:a::/96 (NF-A) 2001:db8:b::/96 (NF-B)
	2001:db8:a::100:1/128 2001:db8:b::100:1/128		2001:db8:a::100:1/128 2001:db8:b::100:1/128
	| |		| |
	| + - - - - - - - - + eMBB (SST=1) |		| + - - - - - - - - + eMBB (SST=1) |
	| | | | |		| | | | |
End of changes. 33 change blocks.
	59 lines changed or deleted		65 lines changed or added
This html diff was produced by rfcdiff 1.48.