< draft-nsdt-teas-transport-slice-definition-03.txt   draft-nsdt-teas-transport-slice-definition-04.txt >
teas R. Rokui teas R. Rokui
Internet-Draft Nokia Internet-Draft Nokia
Intended status: Informational S. Homma Intended status: Informational S. Homma
Expires: January 13, 2021 NTT Expires: March 13, 2021 NTT
K. Makhijani K. Makhijani
Futurewei Futurewei
LM. Contreras LM. Contreras
Telefonica Telefonica
J. Tantsura J. Tantsura
Apstra, Inc. Apstra, Inc.
July 12, 2020 September 9, 2020
IETF Definition of Transport Slice IETF Definition of Transport Slice
draft-nsdt-teas-transport-slice-definition-03 draft-nsdt-teas-transport-slice-definition-04
Abstract Abstract
This document describes the definition of a slice in the transport This document describes the definition of a slice in the transport
networks and its characteristics. The purpose here is to bring networks and its characteristics. The purpose here is to bring
clarity and a common understanding of the transport slice concept and clarity and a common understanding of the transport slice concept and
describe related terms and their meaning. It explains how transport describe related terms and their meaning. It explains how transport
slices can be used in combination with end to end network slices, or slices can be used in combination with end to end network slices, or
independently. independently.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 13, 2021. This Internet-Draft will expire on March 13, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
skipping to change at page 2, line 33 skipping to change at page 2, line 33
4.1.1. Minimal Set of SLOs . . . . . . . . . . . . . . . . . 5 4.1.1. Minimal Set of SLOs . . . . . . . . . . . . . . . . . 5
4.1.2. Other Objectives . . . . . . . . . . . . . . . . . . 7 4.1.2. Other Objectives . . . . . . . . . . . . . . . . . . 7
4.2. Transport Slice Endpoints . . . . . . . . . . . . . . . . 8 4.2. Transport Slice Endpoints . . . . . . . . . . . . . . . . 8
4.2.1. Transport Slice Connectivity Types . . . . . . . . . 9 4.2.1. Transport Slice Connectivity Types . . . . . . . . . 9
4.3. Vertical Composition of Transport Slice . . . . . . . . . 9 4.3. Vertical Composition of Transport Slice . . . . . . . . . 9
4.4. Horizontal Composition of Transport Slice . . . . . . . . 11 4.4. Horizontal Composition of Transport Slice . . . . . . . . 11
5. Transport Slice Structure . . . . . . . . . . . . . . . . . . 11 5. Transport Slice Structure . . . . . . . . . . . . . . . . . . 11
5.1. Stakeholders . . . . . . . . . . . . . . . . . . . . . . 13 5.1. Stakeholders . . . . . . . . . . . . . . . . . . . . . . 13
5.2. Transport Slice Controller Interfaces . . . . . . . . . . 14 5.2. Transport Slice Controller Interfaces . . . . . . . . . . 14
5.3. Transport slice Realization . . . . . . . . . . . . . . . 15 5.3. Transport slice Realization . . . . . . . . . . . . . . . 15
6. Relationship with End-to-End Network Slicing . . . . . . . . 15 6. Isolation in Transport Slices . . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6.1. Traffic Isolation . . . . . . . . . . . . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 6.2. Dedicated Resources . . . . . . . . . . . . . . . . . . . 15
9. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 17 7. Relationship with End-to-End Network Slicing . . . . . . . . 15
10. Informative References . . . . . . . . . . . . . . . . . . . 17 8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
Appendix A. Discussions . . . . . . . . . . . . . . . . . . . . 19 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
A.1. On Isolation Requirements In a Transport Slice . . . . . 19 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 11. Informative References . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
A number of use cases benefit from establishing network connectivity A number of use cases benefit from establishing network connectivity
providing transport and assurance of a specific set of network providing transport and assurance of a specific set of network
resources. In this document, as detailed in the subsequent sections, resources. In this document, as detailed in the subsequent sections,
we refer to this connectivity and resource commitment as the we refer to this connectivity and resource commitment as the
transport slice. Services that might benefit from the transport transport slice. Services that might benefit from the transport
slices include but not limited to: slices include but not limited to:
skipping to change at page 7, line 41 skipping to change at page 7, line 41
Maximal occupancy for a transport slice should be provided. Since it Maximal occupancy for a transport slice should be provided. Since it
carries traffic for multiple flows between the two endpoints, the carries traffic for multiple flows between the two endpoints, the
objectives should also say if they are for the entire connection, objectives should also say if they are for the entire connection,
group of flows or on per flow basis. Maximal occupancy should group of flows or on per flow basis. Maximal occupancy should
specify the scale of the flows (i.e. maximum number of accommodatable specify the scale of the flows (i.e. maximum number of accommodatable
flows) and optionally a maximum number of countable resource units, flows) and optionally a maximum number of countable resource units,
e.g IP or MAC addresses a slice might consume. e.g IP or MAC addresses a slice might consume.
With these objectives incorporated, a customer sees transport slice With these objectives incorporated, a customer sees transport slice
as a dedicated network for its exclusive use. Achieving this may as a dedicated network for its exclusive use. Achieving this may
require different types of isolation techniques in provider networks require explicit request for different types of isolation in provider
as described in Appendix A.1. networks as described in Section 6.
Additional description of slice attributes is covered in a broader Additional description of slice attributes is covered in a broader
context of 'Generic Network Slice Template' in context of 'Generic Network Slice Template' in
[I-D.contreras-teas-slice-nbi]. [I-D.contreras-teas-slice-nbi].
4.2. Transport Slice Endpoints 4.2. Transport Slice Endpoints
The transport slice endpoints are the conceptual entities that The transport slice endpoints are the conceptual entities that
perform any required conversion, or adaptation, and forwarding of the perform any required conversion, or adaptation, and forwarding of the
user traffic. The characteristics of the transport slice endpoints user traffic. The characteristics of the transport slice endpoints
skipping to change at page 15, line 20 skipping to change at page 15, line 20
The Network controller(s) export the connectivity and resource The Network controller(s) export the connectivity and resource
mappings to the TSC. The network controller abstracts the details of mappings to the TSC. The network controller abstracts the details of
underlying resources from the TSC. underlying resources from the TSC.
The realization can be achieved in the form of either physical or The realization can be achieved in the form of either physical or
logical connectivity through VPNs, a variety of tunneling logical connectivity through VPNs, a variety of tunneling
technologies such as Segment Routing, SFC, etc. Accordingly, technologies such as Segment Routing, SFC, etc. Accordingly,
endpoints may be realized as physical or logical service or network endpoints may be realized as physical or logical service or network
functions. functions.
6. Relationship with End-to-End Network Slicing 6. Isolation in Transport Slices
6.1. Traffic Isolation
This section will describe the scope and use of term isolation.
6.2. Dedicated Resources
This section explains the scope and use of term dedicated resource in
the context of transport slices.
7. Relationship with End-to-End Network Slicing
An end-to-end (E2E) network slice is a complete logical network that An end-to-end (E2E) network slice is a complete logical network that
provides a service in its entirety with a specific assurance to the provides a service in its entirety with a specific assurance to the
customer. A transport slice concerns with those assurance aspects customer. A transport slice concerns with those assurance aspects
only within the transport networks. Consider Figure 5, where a only within the transport networks. Consider Figure 5, where a
network operator has an E2E network slice that traverses multiple network operator has an E2E network slice that traverses multiple
technology-specific networks. Each of these networks might use any technology-specific networks. Each of these networks might use any
number of technologies, including but not limited to IP, MPLS, Fiber- number of technologies, including but not limited to IP, MPLS, Fiber-
Optics (e.g. WDM, DWDM), Passive Optical Networking (PON), Optics (e.g. WDM, DWDM), Passive Optical Networking (PON),
Microwave, etc. Microwave, etc.
skipping to change at page 17, line 9 skipping to change at page 17, line 17
with a specific network SLOs, e.g. a secure connection with an E2E with a specific network SLOs, e.g. a secure connection with an E2E
latency less than 5ms, from End User-x (EU-x) to End User-y (EU-y). latency less than 5ms, from End User-x (EU-x) to End User-y (EU-y).
EU-x maybe a 5G user equipment such as an infotainment unit in a car, EU-x maybe a 5G user equipment such as an infotainment unit in a car,
CCTV, or a car for autonomous driving, etc. and EU-y in 5G is 5G CCTV, or a car for autonomous driving, etc. and EU-y in 5G is 5G
application server, IMS, etc. application server, IMS, etc.
In Figure 5, "E2E NS" is that logical network with requested SLO In Figure 5, "E2E NS" is that logical network with requested SLO
between EU-x to EU-y and is associated with a customer and a specific between EU-x to EU-y and is associated with a customer and a specific
service type. service type.
7. Security Considerations 8. Security Considerations
Not applicable in this memo. Not applicable in this memo.
8. IANA Considerations 9. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
9. Acknowledgment 10. Acknowledgment
The entire TEAS NS design team and everyone participating in those The entire TEAS NS design team and everyone participating in those
discussion has contributed to this draft. Particularly, Eric Gray, discussion has contributed to this draft. Particularly, Eric Gray,
Xufeng Liu, Jie Dong, and Jari Arkko for a thorough review among Xufeng Liu, Jie Dong, and Jari Arkko for a thorough review among
other contributions. other contributions.
10. Informative References 11. Informative References
[HIPAA] HHS, "Health Insurance Portability and Accountability Act [HIPAA] HHS, "Health Insurance Portability and Accountability Act
- The Security Rule", February 2003, - The Security Rule", February 2003,
<https://www.hhs.gov/hipaa/for-professionals/security/ <https://www.hhs.gov/hipaa/for-professionals/security/
index.html>. index.html>.
[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,
"Considerations for defining a Transport Slice NBI", "Considerations for defining a Transport Slice NBI",
draft-contreras-teas-slice-nbi-01 (work in progress), draft-contreras-teas-slice-nbi-01 (work in progress),
March 2020. March 2020.
[I-D.ietf-teas-enhanced-vpn]
Dong, J., Bryant, S., Li, Z., Miyasaka, T., and Y. Lee, "A
Framework for Enhanced Virtual Private Networks (VPN+)
Services", draft-ietf-teas-enhanced-vpn-05 (work in
progress), February 2020.
[I-D.ietf-teas-sf-aware-topo-model]
Bryskin, I., Liu, X., Lee, Y., Guichard, J., Contreras,
L., Ceccarelli, D., and J. Tantsura, "SF Aware TE Topology
YANG Model", draft-ietf-teas-sf-aware-topo-model-05 (work
in progress), March 2020.
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE) O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-22 (work in Topologies", draft-ietf-teas-yang-te-topo-22 (work in
progress), June 2019. progress), June 2019.
[I-D.nsdt-teas-ns-framework]
Gray, E. and J. Drake, "Framework for Transport Network
Slices", draft-nsdt-teas-ns-framework-02 (work in
progress), March 2020.
[NFVGST] ETSI, "NFVI Compute and Network Metrics Specification",
February 2018, <https://www.etsi.org/deliver/etsi_gs/NFV-
TST/001_099/008/02.04.01_60/gs_nfv-tst008v020401p.pdf>.
[PCI] PCI Security Standards Council, "PCI DSS", May 2018, [PCI] PCI Security Standards Council, "PCI DSS", May 2018,
<https://www.pcisecuritystandards.org>. <https://www.pcisecuritystandards.org>.
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681, Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,
September 1999, <https://www.rfc-editor.org/info/rfc2681>. September 1999, <https://www.rfc-editor.org/info/rfc2681>.
[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network [RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network
Address Translator (Traditional NAT)", RFC 3022, Address Translator (Traditional NAT)", RFC 3022,
DOI 10.17487/RFC3022, January 2001, DOI 10.17487/RFC3022, January 2001,
skipping to change at page 19, line 38 skipping to change at page 19, line 18
Stage 2 (Release 16)", September 2019, Stage 2 (Release 16)", September 2019,
<http://www.3gpp.org/ftp//Specs/ <http://www.3gpp.org/ftp//Specs/
archive/23_series/23.501/23501-g20.zip>. archive/23_series/23.501/23501-g20.zip>.
[TS33.210] [TS33.210]
3GPP, "3G security; Network Domain Security (NDS); IP 3GPP, "3G security; Network Domain Security (NDS); IP
network layer security (Release 14).", December 2016, network layer security (Release 14).", December 2016,
<https://portal.3gpp.org/desktopmodules/Specifications/ <https://portal.3gpp.org/desktopmodules/Specifications/
SpecificationDetails.aspx?specificationId=2279>. SpecificationDetails.aspx?specificationId=2279>.
Appendix A. Discussions
A.1. On Isolation Requirements In a Transport Slice
Transport slices are perceived as if slice was provisioned for the
customer as a dedicated network with specific SLOs. These committed
SLOs for a given customer should be maintained during the lifetime of
the slice, even in the face of potential disruptions. Such
disruptions include sudden traffic volume changes either from the
customer itself or others, equipment failures in the service provider
network, and various misbehaviors or attacks.
The service provider needs to ensure that its network can provide the
requested slices with the availability agreed with its customers.
Some of the main technical approaches to ensuring guarantees are
about network planning, managing capacity, prioritizing, policing or
shaping customer traffic, selecting dedicated resources, and so on.
One term that has commonly been used in this context is "isolation"
and is also discussed in the [I-D.ietf-teas-enhanced-vpn].
A transport slice customer may ask for traffic separation, selection
of dedicated resources, or interference avoidance from other traffic.
The term "isolation" can refer to any or all of them. For instance,
dedicated resources can help assure that traffic in other slices does
not affect a given slice. Similarly, VPN technologies can provide
traffic separation, and interference avoidance may be provided by
mechanisms such as technical approaches mentioned in the previous
paragraph (network planning, capacity management, etc). Moreover,
these are some of the examples of a particular realization of the
requirement for guarantees; other mechanisms may also be used.
Authors' Addresses Authors' Addresses
Reza Rokui Reza Rokui
Nokia Nokia
Canada Canada
Email: reza.rokui@nokia.com Email: reza.rokui@nokia.com
Shunsuke Homma Shunsuke Homma
NTT NTT
 End of changes. 14 change blocks. 
72 lines changed or deleted 31 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/