< draft-geng-teas-network-slice-mapping-02.txt   draft-geng-teas-network-slice-mapping-03.txt >
Network Working Group X. Geng Network Working Group X. Geng
Internet-Draft J. Dong Internet-Draft J. Dong
Intended status: Informational Huawei Technologies Intended status: Informational Huawei Technologies
Expires: January 14, 2021 R. Pang Expires: August 26, 2021 R. Pang
China Unicom China Unicom
L. Han L. Han
China Mobile China Mobile
T. Niwa T. Niwa
KDDI Individual
J. Jin J. Jin
LG U+ LG U+
C. Liu C. Liu
China Unicom China Unicom
N. Nageshar N. Nageshar
Individual Individual
July 13, 2020 February 22, 2021
5G End-to-end Network Slice Mapping from the view of Transport Network 5G End-to-end Network Slice Mapping from the view of Transport Network
draft-geng-teas-network-slice-mapping-02 draft-geng-teas-network-slice-mapping-03
Abstract Abstract
Network Slicing is one of the core featrures in 5G. End-to-end Network Slicing is one of the core featrures in 5G. End-to-end
network slice consists of 3 major types of network segments: Access network slice consists of 3 major types of network segments: Access
Network (AN), Mobile Core Network (CN) and Transport Network (TN). Network (AN), Mobile Core Network (CN) and Transport Network (TN).
This draft describes the procedure of mapping relationship between 5G This draft describes the procedure of mapping 5G end-to-end network
end-to-end network slice and transport network slice defined in IETF. slice to transport network slice defined in IETF. This draft also
This draft also intends to expose some gaps in the existing network intends to expose some gaps in the existing network management plane
management plane and data plane to support inter-domain network slice and data plane technologies to support inter-domain network slice
mapping. Further work may require cooperation between IETF and 3GPP mapping. Further work may require cooperation between IETF and 3GPP
(or other standard organizations). The definition of data model, (or other standard organizations). Data model specification,
signaling protocol extension and new encapsulation are out of the signaling protocol extension and new encapsulation definition are out
scope of this draft. of the scope of this draft.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 2, line 12 skipping to change at page 2, line 12
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 14, 2021. This Internet-Draft will expire on August 26, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 40 skipping to change at page 2, line 40
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Network Slice Mapping Structure . . . . . . . . . . . . . . . 4 3. Network Slice Mapping Structure . . . . . . . . . . . . . . . 4
3.1. Requirements Profile . . . . . . . . . . . . . . . . . . 5 3.1. Requirements Profile . . . . . . . . . . . . . . . . . . 5
3.2. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Relevant functions . . . . . . . . . . . . . . . . . . . 6 3.3. Relevant functions . . . . . . . . . . . . . . . . . . . 6
4. Network Slice Mapping Procedure . . . . . . . . . . . . . . . 7 4. Network Slice Mapping Procedure . . . . . . . . . . . . . . . 7
4.1. Network Slice Mapping in Management Plane . . . . . . . . 8 4.1. Network Slice Mapping in Management Plane . . . . . . . . 8
4.2. Network Slice Mapping in Control Plane . . . . . . . . . 9 4.2. Network Slice Mapping in Control Plane . . . . . . . . . 9
4.3. Network Slice Mapping in data plane . . . . . . . . . . . 10 4.3. Network Slice Mapping in Data Plane . . . . . . . . . . . 10
4.3.1. Data Plane Mapping Considerations . . . . . . . . . . 10 4.3.1. Data Plane Mapping Considerations . . . . . . . . . . 10
4.3.2. Data Plane Mapping Design . . . . . . . . . . . . . . 10 4.3.2. Data Plane Mapping Options . . . . . . . . . . . . . 10
5. Network Slice Mapping Summary . . . . . . . . . . . . . . . . 15 5. Network Slice Mapping Summary . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
9. Normative References . . . . . . . . . . . . . . . . . . . . 15 9. Normative References . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
Driven by the new applications of 5G, the concept of network slicing Driven by the new applications of 5G, the concept of network slicing
is defined to provide a logical network with specific capabilities is defined to provide a logical network with specific capabilities
and characteristics. Network slice contains a set of network and characteristics. Network slice contains a set of network
functions and allocated resources(e.g. Computation, storage and functions and allocated resources(e.g. computation, storage and
network resources). According to [TS28530], a 5G end-to-end network network resources). According to [TS28530], a 5G end-to-end network
slice is composed of three major types network segments: Radio Access slice is composed of three major types network segments: Radio Access
Network (RAN), Transport Network (TN) and Mobile Core Network (CN). Network (RAN), Transport Network (TN) and Mobile Core Network (CN).
Transport network is supposed to provide the required connectivity Transport network is supposed to provide the required connectivity
between AN and CN, which specific performance commitment. For each between AN and CN, with specific performance commitment. For each
end-to-end network slice, the topology and performance requirement end-to-end network slice, the topology and performance requirement
for transport network can be very different, which requires transport for transport network can be very different, which requests transport
network to have the capability of supporting multiple different network to have the capability of supporting multiple different
transport network slices. transport network slices.
A transport network slice is a virtual (logical) network with a A transport network slice is a virtual (logical) network with a
particular network topology and a set of shared or dedicated network particular network topology and a set of shared or dedicated network
resources, which are used to provide the network slice consumer with resources, which are used to provide the network slice consumer with
the required connectivity, appropriate isolation and specific Service the required connectivity, appropriate isolation and specific Service
Level Agreement (SLA). A transport network slice could span multiple Level Agreement (SLA). A transport network slice could span multiple
technology (IP, Optical) and multiple administrative domains. technology (IP, Optical) and multiple administrative domains.
Depending on the consumer's requirement, a transport network slice Depending on the consumer's requirement, a transport network slice
could be isolated from other concurrent transport network slices, in could be isolated from other concurrent transport network slices, in
terms of data plane, control plane and management plane. Transport terms of data plane, control plane and management plane. Transport
network slice is being defined and discussed in IETF. network slice is being defined and discussed in IETF.
Editor's Note: The work of Editor's Note: The definition of transport network slice will align
with [I-D.ietf-teas-ietf-network-slice-definition].
The procedure of end-to-end network slice instance creation, network The procedure of end-to-end network slice instance creation, network
slice subnet instance creation and network slice instance termination slice subnet instance creation and network slice instance termination
in management plane are defined in [TS28531]. The end-to-end network in management plane is defined in [TS28531]. The end-to-end network
slice allocation is defined in ETSI [ZSM003]. But there is no slice allocation is defined in ETSI [ZSM003]. But there is no
specifications about how to map end-to-end network slice in 5G system specifications about how to map end-to-end network slice in 5G system
to transport network slice. This draft describes the procedure of to transport network slice. This draft describes the procedure of
mapping 5G end-to-end network slice into transport network slice in mapping 5G end-to-end network slice into transport network slice in
management plane, control plane and user plane. management plane, control plane and user plane.
5G end-to-end network slice mapping is treated as an independent
mechanism from 5G end-to-end QoS mapping. The latter is not covered
by this version.
2. Terminologies 2. Terminologies
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The following terms are used in this document: The following terms are used in this document:
NS: Network Slice NS: Network Slice
NSI: Network Slice Instance NSI: Network Slice Instance
NSSI: Network Slice Subnet Instance NSSI: Network Slice Subnet Instance
NSSAI: Network Slice Selection Assistance Information NSSAI: Network Slice Selection Assistance Information
S-NSSAI: Single Network Slice Selection Assistance Information S-NSSAI: Single Network Slice Selection Assistance Information
AN: Access Network AN: Access Network
skipping to change at page 4, line 39 skipping to change at page 4, line 44
TNSII: Transport Network Slice Interworking Identifier TNSII: Transport Network Slice Interworking Identifier
TNSI: Transport Network Slice Identifier TNSI: Transport Network Slice Identifier
PDU: Protocol Data Unit PDU: Protocol Data Unit
Editor's Note: Terminologies defined in 3GPP, e.g.,Network Slice Editor's Note: Terminologies defined in 3GPP, e.g.,Network Slice
Subnet Management Function(NSSMF), Network Slice Subnet Subnet Management Function(NSSMF), Network Slice Subnet
Instance(NSSI) and Network Slice Selection Assistance Instance(NSSI) and Network Slice Selection Assistance
Information(NSSAI), is used in the end-to-end network slice mapping, Information(NSSAI), are used in the end-to-end network slice mapping,
which may not be used necessarily within the transport network. which may not be used necessarily within the transport network.
3. Network Slice Mapping Structure 3. Network Slice Mapping Structure
The following figure shows the necessary elements for mapping end-to- The following figure shows the necessary elements for mapping end-to-
end network slice into transport network slice. All these network end network slice into transport network slice. All these network
slice elements are classified into three groups: requirements/ slice elements are classified into three groups: requirements/
capabilities, identifiers and relevant functions. capabilities, identifiers and relevant functions.
+-----------------+ +-----------------+
skipping to change at page 5, line 38 skipping to change at page 5, line 38
V V V V ----------------- V V V V -----------------
/\ +-----+ +-----+ +-------+ Data /\ +-----+ +-----+ +-------+ Data
/AN\ -----| PE |-----...-----| PE |----| UPF | Plane /AN\ -----| PE |-----...-----| PE |----| UPF | Plane
/____\ +-----+ +-----+ +-------+ /____\ +-----+ +-----+ +-------+
|-->TNSII<--|------>TNSI<-------|-->TNSII<--| |-->TNSII<--|------>TNSI<-------|-->TNSII<--|
3.1. Requirements Profile 3.1. Requirements Profile
In order to satisfy a tenant's request for a network slice with In order to satisfy a tenant's request for a network slice with
certain characteristics, creating a new network slice or using certain characteristics, creating a new network slice or using
existing network slice instance is constrained by the customer's existing network slice instance is constrained by the requirement
requirement and the capability of the network slices. profile and the capability of the network slices.
o Service Profile: represents the properties of network slice o Service Profile: represents the properties of network slice
related requirement that should be supported by the network slice related requirement that should be supported by the network slice
instance in 5G network. Service profile is defined in [TS28541] instance in 5G network. Service profile is defined in [TS28541]
6.3.3. 6.3.3.
o TN Network Slice Profile: represents the properties of transport o TN Network Slice Profile: represents the properties of transport
network slice related requirement that should be supported by the network slice related requirement that should be supported by the
transport network slice in a 5G network. Slice Profile is defined transport network slice in a 5G network. Slice Profile is defined
in [TS28541] 6.3.4. TN Network slice profile is newly defined in in [TS28541] 6.3.4. TN Network slice profile is newly defined in
this draft. this draft.
3.2. Identifiers 3.2. Identifiers
Network slice related identifiers in management plane, control plane Network slice related identifiers in management plane, control plane
and user(data) plane play an important role in end-to-end network and data(user) plane play an important role in end-to-end network
slice mapping. slice mapping.
o Single Network Slice Selection Assistance Information(S-NSSAI): o Single Network Slice Selection Assistance Information(S-NSSAI):
end-to-end network slice identifier in control plane, which is end-to-end network slice identifier in control plane, which is
defined in [TS23501]; defined in [TS23501];
o Network Slice Instance(NSI) Identifier:end-to-end network slice o Network Slice Instance(NSI) Identifier:end-to-end network slice
identifier in management plane, which is created in NSMF; NSI is identifier in management plane, which is created in NSMF; NSI is
is set of Network Function instances and the required resources is set of Network Function instances and the required resources
(e.g. compute, storage and networking resources) which form a (e.g. computing, storage and networking resources) which form a
deployed Network Slice, which is defined in [TS23501]; ; deployed Network Slice, which is defined in [TS23501]; ;
o Transport Network Slice Instance(TN-NSSI) Identifier: transport o Transport Network Slice Instance(TN-NSSI) Identifier: transport
network slice identifier in management plane, which is created in network slice identifier in management plane, which is created in
TN NSSMF; TN-NSSI is newly defined in this draft. TN NSSMF; TN-NSSI is newly defined in this draft.
o Transport Network Slice Interworking Identifier (TNSII): network o Transport Network Slice Interworking Identifier (TNSII): network
slice identifier which is used for mapping end-to-end network slice identifier which is used for mapping end-to-end network
slice into transport network slice in user plane. TNSII is newly slice into transport network slice in data plane. TNSII is a new
defined in this draft. concept introduced by this draft, which can be instantiated with
existing data plane identifiers and doesn't necessarilly request
new encapsulation. TNSII could be pre-allocated as a global
identifier.
o Transport Network Slice Identifier(TNSI): transport network slice o Transport Network Slice Identifier(TNSI): transport network slice
identifier in data plane(user plane). TNSI is newly defined in identifier in data plane(user plane). TNSI is newly defined in
this draft. this draft.
The relationship between these identifiers are specifies in the The relationship between these identifiers are specifies in the
following sections. following sections.
3.3. Relevant functions 3.3. Relevant functions
skipping to change at page 8, line 22 skipping to change at page 8, line 23
Transport Network Slice Profile between the specified endpoints (AN/ Transport Network Slice Profile between the specified endpoints (AN/
CN edge nodes) and sends the TN NSSI Identifier to NSMF. CN edge nodes) and sends the TN NSSI Identifier to NSMF.
6. NSMF acquires the mapping relationship between NSI and TN NSSI. 6. NSMF acquires the mapping relationship between NSI and TN NSSI.
7. NSMF matains the mapping relationship between NSI and S-NSSAI and 7. NSMF matains the mapping relationship between NSI and S-NSSAI and
the mapping relationship between TN NSSI and TNSII, which could be the mapping relationship between TN NSSI and TNSII, which could be
used to set up mapping relationship between S-NSSAI and TNSII. used to set up mapping relationship between S-NSSAI and TNSII.
8. When a PDU session is set up between AN and CN, an S-NSSAI is 8. When a PDU session is set up between AN and CN, an S-NSSAI is
slected for the PDU session. selected for the PDU session.
9. AN/CN edge nodes encapsulate the packet using TNSII, according to 9. AN/CN edge nodes encapsulates the packet using TNSII, according
the selected S-NSSAI. Network Slice could also be differentiated by to the selected S-NSSAI. Network Slice could also be differentiated
physical interface, if different network slices are transported by physical interface, if different network slices are transported
through different interface; through different interface;
10. The edge node of transport network parses the TNSII from the 10. The edge node of transport network parses the TNSII from the
packet and maps the packet to the corresponding transport network packet and maps the packet to the corresponding transport network
slice. It may encapsulate packet with TNSI. The nodes in transport slice. It may encapsulate packet with TNSI. The nodes in transport
network transit the packet inside the corresponding transport network network transit the packet inside the corresponding transport network
slice according to TNSI. slice according to TNSI.
The procedure of end-to-end network slice mapping involves the The procedure of end-to-end network slice mapping involves the
mapping in three network planes: management plane, control plane and mapping in three network planes: management plane, control plane and
skipping to change at page 9, line 37 skipping to change at page 9, line 38
mechanism should be out of scope in the draft) mechanism should be out of scope in the draft)
TN NSSMF sends the selected or newly allocated TN NSSI identifier to TN NSSMF sends the selected or newly allocated TN NSSI identifier to
NSMF. The mapping relationship between NSI identifier and TN NSSI NSMF. The mapping relationship between NSI identifier and TN NSSI
identifier is maintained in both NSMF and TN NSSMF. identifier is maintained in both NSMF and TN NSSMF.
YANG data model for the Transport Slice NBI, which could be used by a YANG data model for the Transport Slice NBI, which could be used by a
higher level system which is the Transport slice consumer of a higher level system which is the Transport slice consumer of a
Transport Slice Controller (TSC) to request, configure, and manage Transport Slice Controller (TSC) to request, configure, and manage
the components of a transport slices, is defined in the components of a transport slices, is defined in
[I-D.wd-teas-transport-slice-yang]. [I-D.wd-teas-transport-slice-yang]. The northbound Interface of IETF
network slice refers to [I-D.wd-teas-ietf-network-slice-nbi-yang].
4.2. Network Slice Mapping in Control Plane 4.2. Network Slice Mapping in Control Plane
There is no explicit interaction between transport network and AN/CN There is no explicit interaction between transport network and AN/CN
in the control plane, but the S-NSSAI defined in [TS23501] is treated in the control plane, but the S-NSSAI defined in [TS23501] is treated
as the end-to-end network slice identifier in the control plane of AN as the end-to-end network slice identifier in the control plane of AN
and CN, which is used in UE registration and PDU session setup. In and CN, which is used in UE registration and PDU session setup. In
this draft, we assume that there is mapping relationship between this draft, we assume that there is mapping relationship between
S-NSSAI and NSI in the management plane, thus it could be mapped to a S-NSSAI and NSI in the management plane, thus it could be mapped to a
transport network slice . transport network slice .
Editor's note: The mapping relationship between NSI defined in Editor's note: The mapping relationship between NSI defined in
[TS23501] and S-NSSAI defined in [TS23501] is still in discussion. [TS23501] and S-NSSAI defined in [TS23501] is still in discussion.
4.3. Network Slice Mapping in data plane 4.3. Network Slice Mapping in Data Plane
If multiple network slices are carried through one physical interface If multiple network slices are carried through one physical interface
between AN/CN and TN, transport network slice interworking between AN/CN and TN, transport network slice interworking
identifier(TNSII) in the data plane needs to be introduced. If identifier(TNSII) in the data plane needs to be introduced. If
different network slices are transported through different physical different network slices are transported through different physical
interfaces, Network Slices could be distinguished by the interface interfaces, Network Slices could be distinguished by the interface
directly. Thus TNSII is not the only option for network slice directly. Thus TNSII is not the only option for network slice
mapping, while it may help in introducing new network slices. mapping, while it may help in introducing new network slices.
4.3.1. Data Plane Mapping Considerations 4.3.1. Data Plane Mapping Considerations
skipping to change at page 10, line 38 skipping to change at page 10, line 41
people, we think the concept of "network instance" is a 'neither people, we think the concept of "network instance" is a 'neither
Necessary nor Sufficient Condition' for network slice. Network Necessary nor Sufficient Condition' for network slice. Network
Instance could be determined by S-NSSAI, it could also depends on Instance could be determined by S-NSSAI, it could also depends on
other information; Network slice could also be allocated without other information; Network slice could also be allocated without
network instance (in my understanding) And, TNSII is not a network instance (in my understanding) And, TNSII is not a
competitive concept with network instance.TNSII is a concept for the competitive concept with network instance.TNSII is a concept for the
data plane interconnection with transport network, network instance data plane interconnection with transport network, network instance
may be used by AN and CN nodes to associate a network slice with may be used by AN and CN nodes to associate a network slice with
TNSII TNSII
4.3.2. Data Plane Mapping Design 4.3.2. Data Plane Mapping Options
The following picture shows the end-to-end network slice in data The following picture shows the end-to-end network slice in data
plane: plane:
+--+ +-----+ +----------------+ +--+ +-----+ +----------------+
|UE|- - - -|(R)AN|---------------------------| UPF | |UE|- - - -|(R)AN|---------------------------| UPF |
+--+ +-----+ +----------------+ +--+ +-----+ +----------------+
|<----AN NS---->|<----------TN NS---------->|<----CN NS----->| |<----AN NS---->|<----------TN NS---------->|<----CN NS----->|
The mapping between 3GPP slice and transport slice in user plane The mapping between 3GPP slice and transport slice in user plane
skipping to change at page 15, line 30 skipping to change at page 15, line 31
+---------+ | +---------+ +---------+ | +---------+
| | | | | |
| | | | | |
Control +-----V-----+ | +----------+----------+ Control +-----V-----+ | +----------+----------+
Plane | S-NSSAI | | | | Plane | S-NSSAI | | | |
+-----------+ | | | +-----------+ | | |
| +----V----+ +----V----+ | +----V----+ +----V----+
+----------->| TNSII |<--------->| TNSI | +----------->| TNSII |<--------->| TNSI |
User | /Port |<--------->| | User | /Port |<--------->| |
Plane +---------+ +---------+ Plane +---------+ +---------+
|
6. IANA Considerations 6. IANA Considerations
TBD TBD
Note to RFC Editor: this section may be removed on publication as an Note to RFC Editor: this section may be removed on publication as an
RFC. RFC.
7. Security Considerations 7. Security Considerations
skipping to change at page 16, line 6 skipping to change at page 16, line 12
The authors would like to thank Shunsuke Homma for reviewing the The authors would like to thank Shunsuke Homma for reviewing the
draft and giving valuable comments. draft and giving valuable comments.
9. Normative References 9. Normative References
[GST] "Generic Network Slice Template", [GST] "Generic Network Slice Template",
<https://www.gsma.com/newsroom/all-documents/generic- <https://www.gsma.com/newsroom/all-documents/generic-
network-slice-template-v2-0/>. network-slice-template-v2-0/>.
[I-D.contreras-teas-slice-nbi] [I-D.contreras-teas-slice-nbi]
Contreras, L., Homma, S., and J. Ordonez-Lucena, Contreras, L., Homma, S., and J. Ordonez-Lucena, "IETF
"Considerations for defining a Transport Slice NBI", Network Slice use cases and attributes for Northbound
draft-contreras-teas-slice-nbi-01 (work in progress), Interface of controller", draft-contreras-teas-slice-
March 2020. nbi-03 (work in progress), October 2020.
[I-D.ietf-teas-ietf-network-slice-definition]
Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J.
Tantsura, "Definition of IETF Network Slices", draft-ietf-
teas-ietf-network-slice-definition-00 (work in progress),
January 2021.
[I-D.wd-teas-ietf-network-slice-nbi-yang]
Bo, W., Dhody, D., Han, L., and R. Rokui, "A Yang Data
Model for IETF Network Slice NBI", draft-wd-teas-ietf-
network-slice-nbi-yang-01 (work in progress), November
2020.
[I-D.wd-teas-transport-slice-yang] [I-D.wd-teas-transport-slice-yang]
Bo, W., Dhody, D., Han, L., and R. Rokui, "A Yang Data Bo, W., Dhody, D., Han, L., and R. Rokui, "A Yang Data
Model for Transport Slice NBI", draft-wd-teas-transport- Model for Transport Slice NBI", draft-wd-teas-transport-
slice-yang-02 (work in progress), July 2020. slice-yang-02 (work in progress), July 2020.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 17, line 4 skipping to change at page 17, line 24
Xuesong Geng Xuesong Geng
Huawei Technologies Huawei Technologies
Email: gengxuesong@huawei.com Email: gengxuesong@huawei.com
Jie Dong Jie Dong
Huawei Technologies Huawei Technologies
Email: jie.dong@huawei.com Email: jie.dong@huawei.com
Ran Pang Ran Pang
China Unicom China Unicom
Email: pangran@chinaunicom.cn Email: pangran@chinaunicom.cn
Liuyan Han Liuyan Han
China Mobile China Mobile
Email: hanliuyan@chinamobile.com Email: hanliuyan@chinamobile.com
Tomonobu Niwa Tomonobu Niwa
KDDI Individual
Email: to-niwa@kddi.com Email: tomonobu.niwa@gmail.com
Jaehwan Jin Jaehwan Jin
LG U+ LG U+
Email: daenamu1@lguplus.co.kr Email: daenamu1@lguplus.co.kr
Chang Liu Chang Liu
China Unicom China Unicom
Email: liuc131@chinaunicom.cn Email: liuc131@chinaunicom.cn
Nikesh Nageshar Nikesh Nageshar
Individual Individual
Email: nikesh.nageshar@gmail.com Email: nikesh.nageshar@gmail.com
 End of changes. 34 change blocks. 
44 lines changed or deleted 65 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/