Re: [DMM] 3GPP CSIPTO

Marco Liebsch <Marco.Liebsch@neclab.eu> Mon, 01 September 2014 13:25 UTC

Return-Path: <Marco.Liebsch@neclab.eu>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC4C1A0407 for <dmm@ietfa.amsl.com>; Mon, 1 Sep 2014 06:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level:
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I86vKTs4PlCC for <dmm@ietfa.amsl.com>; Mon, 1 Sep 2014 06:25:23 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A9811A0406 for <dmm@ietf.org>; Mon, 1 Sep 2014 06:25:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id F235C107D7C; Mon, 1 Sep 2014 15:25:20 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mnnIJW4fpe-P; Mon, 1 Sep 2014 15:25:20 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id CD5DC107D38; Mon, 1 Sep 2014 15:25:16 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.182]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Mon, 1 Sep 2014 15:25:16 +0200
From: Marco Liebsch <Marco.Liebsch@neclab.eu>
To: Alper Yegin <alper.yegin@yegin.org>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] 3GPP CSIPTO
Thread-Index: AQHPxbmCbyq4sm/UWUmphplsxG5zipvsE8Lg
Date: Mon, 01 Sep 2014 13:25:16 +0000
Message-ID: <69756203DDDDE64E987BC4F70B71A26D919A33D5@PALLENE.office.hd>
References: <D051368C-46EB-47A0-AA6A-BD55E664C7C2@yegin.org>
In-Reply-To: <D051368C-46EB-47A0-AA6A-BD55E664C7C2@yegin.org>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.6.1]
Content-Type: multipart/alternative; boundary="_000_69756203DDDDE64E987BC4F70B71A26D919A33D5PALLENEofficehd_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/UUm5FiJAcNZL9Eds98qvPXrGlVs
Subject: Re: [DMM] 3GPP CSIPTO
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 13:25:26 -0000

Hi Alper,

thanks for posting the update. One clarifying question on the following service requirement:

'The 3GPP system shall minimize the number of connections of a UE without disrupting the
UE's services, e.g. to ensure economical use of network resources'

Can this be understood as the number of connections, which is to be minimized, is equal to the
number of mobility session and associated IP addresses?

Is this to minimize the states in the network, or is the intention to limit the control-plane
signaling with the mobile device to setup/teardown the connection?

Thanks for your feedback in advance,
marco



From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Alper Yegin
Sent: Montag, 1. September 2014 09:51
To: dmm@ietf.org
Subject: [DMM] 3GPP CSIPTO

Dear DMMers,

Here's an update on 3GPP SA1 CSIPTO work...

Two weeks ago there was an SA1 meeting (SA1#67), and in that meeting SA1 has completed the CSIPTO normative work.
As you might remember, SA1 is in charge of defining service requirements.

The next step for CSIPTO is to initiate a work item in SA2.


And here's a copy-paste of the normative requirements (accepted doc is S1-143607.zip<http://www.3gpp.org/ftp/tsg_sa/WG1_Serv/TSGS1_67_SophiaAntipolis/docs/S1-143607.zip>):


Some types of services (e.g. streaming services, VOIP, VPN, HTTPS-Based Services) cannot tolerate a change of IP address of the UE without disruption of the service.

SIPTO can be performed with or without coordination between the UE and the network. The following requirements apply to coordinated SIPTO:

-     The 3GPP system shall be able to support multiple connections that are associated with the same defined IP network where each connection may or may not support IP address preservation.

-     The 3GPP system shall be able to determine if an IP flow requires IP address preservation or not. Based on this determination, the 3GPP network shall be able to offload selected IP traffic in coordinated manner between UE and the network, in order to minimize service disruption.
-      The 3GPP system shall be able to detect when a connection becomes suboptimal and decide when to establish a new optimal connection to the same defined IP network or use an existing connection.
Note 1:      The definition of optimal and suboptimal can be based on a number of implementation criteria like geography, topology and load balancing etc.
-     The 3GPP system shall minimize the number of connections of a UE without disrupting the UE's services, e.g. to ensure economical use of network resources.
-     The 3GPP system shall be able to ensure that the actual average aggregate bit rate for IP flows of packet data network connections associated with the same packet data network does not significantly exceed the subscribed aggregate maximum bit rate for this packet data network when two connections are used with the same defined IP network.

Note 2:  Requirements for Coordinated SIPTO do not apply to IMS.