[DMM] 3GPP CSIPTO

Alper Yegin <alper.yegin@yegin.org> Mon, 01 September 2014 07:50 UTC

Return-Path: <alper.yegin@yegin.org>
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 21DB11A0172 for <dmm@ietfa.amsl.com>; Mon, 1 Sep 2014 00:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.306
X-Spam-Level: **
X-Spam-Status: No, score=2.306 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_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 XZ2WrRXovtgQ for <dmm@ietfa.amsl.com>; Mon, 1 Sep 2014 00:50:54 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F19E51A0174 for <dmm@ietf.org>; Mon, 1 Sep 2014 00:50:51 -0700 (PDT)
Received: from [192.168.2.49] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mreueus002) with ESMTP (Nemesis) id 0Lyk9B-1YSGcC3eQZ-01694w; Mon, 01 Sep 2014 09:50:50 +0200
From: Alper Yegin <alper.yegin@yegin.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3BF31B92-2924-4D21-8527-039FD3569A30"
Date: Mon, 01 Sep 2014 10:50:50 +0300
Message-Id: <D051368C-46EB-47A0-AA6A-BD55E664C7C2@yegin.org>
To: dmm@ietf.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:1yadhGa4EBTMmlqPUhD0nee39O9zam/xhpVj4TUvOyQ 2v/85ZUbKrUUrpc7eVBwDPvRXOnk3Q8wgJm/X2N8sL3FmVlkyp SpFY6l1tJMFPNSH5vMdb8AaiLSQX6TuT4X7sRUd2uvykGYTN08 ZJQWRZWHTEjhTVvnFCIKALqlghHJexCZI3I1joz0AqfyXSdDEj uRd9PFxqtYHV0ppTsJhsknzaiLtcMz4uL2WDTF+TQUAEmVUGiS yGbSbVF6PPpMVAY+waIk4n+cAklVjNWw1ghg8JWGIEt/cmh5QN VE/Gh3f/I99yukXExatwzZNrym2wEX+/b9GU90gk6284yLW9zg RLs0NxuSVJnIsfvVApR4+HWSJYrGABu7SA3iVHLs48FFSi7Rxo K60bxpk7OQQ5A==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/c_1s1IVV9_nXct_7-X4P3fyxWSE
Subject: [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 07:50:56 -0000

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):


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.