Skip to main content

Mapping 5G slice to Transport Network slice with UDP Source Ports
draft-ietf-dmm-tn-aware-mobility-32

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, dmm-chairs@ietf.org, dmm@ietf.org, draft-ietf-dmm-tn-aware-mobility@ietf.org, rfc-editor@rfc-editor.org, satoru.matsushima@gmail.com, tojens.ietf@gmail.com
Subject: Document Action: 'Mobility-aware Transport Network Slicing for 5G' to Informational RFC (draft-ietf-dmm-tn-aware-mobility-25.txt)

The IESG has approved the following document:
- 'Mobility-aware Transport Network Slicing for 5G'
  (draft-ietf-dmm-tn-aware-mobility-25.txt) as Informational RFC

This document is the product of the Distributed Mobility Management Working
Group.

The IESG contact persons are Tommy Jensen and Éric Vyncke.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/


Ballot Text

Technical Summary

   Network slicing in 5G enables logical networks for communication
   services of multiple 5G customers to be multiplexed over the same
   infrastructure.  While 5G slicing covers logical separation of
   various aspects of 5G infrastructure and services, user's data plane
   packets over the Radio Access Network (RAN) and Core Network (5GC)
   use IP in many segments of an end-to-end 5G slice.  When end-to-end
   slices in a 5G System use network resources, they are mapped to
   corresponding Transport Network (TN) slice(s) which in turn provide
   the bandwidth, latency, isolation, and other criteria required for
   the realization of a 5G slice.

   This document describes mapping of 5G slices to TN slices using UDP
   source port number of the GTP-U bearer when the TN slice provider is
   separated by an "attachment circuit" from the networks in which the
   5G network functions are deployed, for example, 5G functions that are
   distributed across data centers.  The slice mapping defined here is
   supported transparently when a 5G user device moves across 5G
   attachment points and session anchors.

Working Group Summary

   The WGLC was productive with no opposition and only non-controversial
   feedback with significant support. The document was revised in
   response to these and Linda's GENART review. 

Document Quality

   This document had years of productive WG revisions incorporating
   significant changes, including greatly simplifying the document and
   expanding the security considerations. It does not describe a new
   protocol that would require interoperability testing, but describes
   how to map 5G slices onto Transport Network slices. No
   implementations are claimed.

Personnel

   The Document Shepherd for this document is Satoru Matsushima. The
   Responsible Area Director is Tommy Jensen.

RFC Editor Note