Skip to main content

Connecting 3GPP slices through IETF Network Slice services
draft-contreras-teas-3gpp-ietf-slice-mapping-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Luis M. Contreras , Ivan Bykov , Jose A. Ordonez-Lucena
Last updated 2022-09-08 (Latest revision 2022-03-07)
Replaced by draft-gcdrb-teas-5g-network-slice-application
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-gcdrb-teas-5g-network-slice-application
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

3GPP is introducing the concept of slicing as a primary way of service delivery. Slicing at 3GPP implies the differentiation of services in terms of performance expectations as well as the connection of different network entities also potentially differentiated per slice. With that aim, 3GPP is defining a number of logical constructs with the intent of being served with specific characteristics, determined by different QoS profiles. This document describes the connectivity of 3GPP slices through IETF Network Slice services taking into account that specific service level objectives, and identifies gaps existing nowadays on both 3GPP and IETF specifications for an straightforward mapping of parameters between both environments.

Authors

Luis M. Contreras
Ivan Bykov
Jose A. Ordonez-Lucena

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)