Re: [5gangip] To initiate user-plane study work in 3GPP

<Dirk.von-Hugo@telekom.de> Wed, 18 October 2017 17:17 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAFB01270AB for <5gangip@ietfa.amsl.com>; Wed, 18 Oct 2017 10:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.319
X-Spam-Level:
X-Spam-Status: No, score=-4.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 Ndg7gezo5pL6 for <5gangip@ietfa.amsl.com>; Wed, 18 Oct 2017 10:17:27 -0700 (PDT)
Received: from MAILOUT21.telekom.de (MAILOUT21.telekom.de [80.149.113.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D432113303F for <5gangip@ietf.org>; Wed, 18 Oct 2017 10:17:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1508347047; x=1539883047; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=DsMjOtE2RPACs60O/yQyyZ/0VVYa8a3mP5KWQEuFZZI=; b=kbgOs06wVgIOujTEiulOwPCbkXYWQsRYsIGMAAa+X/+kEuop4NsboKI9 X0cfSGkDwvakMRCUpcxa9pqMXN2sjcx8Kqn8eQ0aVjrlOhGKsuAYCLHWB 9dfhQpN8t/b0a5sN1qmRETkP6k2Qb0sUEkzXKJM8RGVZdExi+SGcFWzTV 51yiWZHP/BTV+sXRMwuX/Erns2iZfnvgttaFoWXGgr4D8jOR+Iv79DDAm fn8Y3zd7sTWwyFKkWw5Wyqn80VxabxF9QPoLHgTim8VEBKZqWBix8+77n czod4hbEWfOEaQ6cvitCPmKOFjHvHZq94kJG3rUQNQJhsMBrqls58qT0+ Q==;
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Oct 2017 19:17:23 +0200
X-IronPort-AV: E=Sophos;i="5.43,397,1503352800"; d="scan'208";a="51522221"
Received: from he105828.emea1.cds.t-internal.com ([10.169.119.31]) by QDEC97.de.t-internal.com with ESMTP/TLS/AES256-SHA; 18 Oct 2017 19:17:23 +0200
Received: from HE105831.EMEA1.cds.t-internal.com (10.169.119.34) by HE105828.emea1.cds.t-internal.com (10.169.119.31) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 18 Oct 2017 19:17:23 +0200
Received: from HE105831.EMEA1.cds.t-internal.com ([fe80::68a7:ffa4:81be:3178]) by HE105831.emea1.cds.t-internal.com ([fe80::68a7:ffa4:81be:3178%26]) with mapi id 15.00.1347.000; Wed, 18 Oct 2017 19:17:23 +0200
From: Dirk.von-Hugo@telekom.de
To: satoru.matsushima@gmail.com, d.lake@surrey.ac.uk, uma.chunduri@huawei.com, rgm@htt-consult.com, sarikaya@ieee.org
CC: 5gangip@ietf.org
Thread-Topic: [5gangip] To initiate user-plane study work in 3GPP
Thread-Index: AQHTRl8kO1VTQxQGSEuyCLqfy+cYcaLmx9GAgAEXSYCAAIyuAIAABpeAgAAD3wCAAL1gAIAApGoQ
Date: Wed, 18 Oct 2017 17:17:23 +0000
Message-ID: <65b9aefbd54c480581fc584e2e55f5a9@HE105831.emea1.cds.t-internal.com>
References: <65B34A9D-6138-440F-8A33-ABC9A7AB4652@gmail.com> <CAC8QAceHG2iExRJ0KKFgrcpDrAOWaFT1sF5CA7zOg1VR8mAkVg@mail.gmail.com> <819e62e3-4d51-aaab-08da-040088283e5f@htt-consult.com> <DB3PR0602MB3756D85AE09BAD19F2B812D5B54C0@DB3PR0602MB3756.eurprd06.prod.outlook.com> <25B4902B1192E84696414485F57268541351434C@sjceml521-mbs.china.huawei.com> <DB3PR0602MB3756866950B6B9C3B9F6FEA1B54C0@DB3PR0602MB3756.eurprd06.prod.outlook.com> <6DCCEE35-50F8-410E-A685-76A369BEA91F@gmail.com>
In-Reply-To: <6DCCEE35-50F8-410E-A685-76A369BEA91F@gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.17.11]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/heeadLUM5cbs9H2gMjfIqCpXTSE>
Subject: Re: [5gangip] To initiate user-plane study work in 3GPP
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Oct 2017 17:17:31 -0000

Dear all,
I completely agree that we (i.e. at IETF community) should start work on potential protocol or framework solutions for 3GPP - even before 5G requirements (in architecture documents) are fully specified which as Georg in Prague pointed out https://datatracker.ietf.org/meeting/99/materials/slides-99-edu-sessk-3gpp-ietf-collaboration-on-5g/ is expected for end of this year.
And I also think that a major role will play Identity / Locator Separated protocols like LISP, ILNP, ILA ... supporting multiple types of mobility by choosing correspondingly adapted configurations ... which would fit to service-tailored network slicing ideas. 
Thanks!
Best Regards
Dirk 
-----Original Message-----
From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of Satoru Matsushima
Sent: Mittwoch, 18. Oktober 2017 11:11
To: d.lake@surrey.ac.uk; uma.chunduri@huawei.com; rgm@htt-consult.com; <sarikaya@ieee.org>
Cc: 5gangip@ietf.org
Subject: Re: [5gangip] To initiate user-plane study work in 3GPP

Behcet, David, and Uma,

Thank you for your comments. Those are really informative. And yes I agree that we need to work with 3GPP. That’s why the WID out there.

While there’s no clear facts on future networking in 5G, I wrote up the text in justification with facts which at least IPv6 adoption has been growth and IAB recommend SDOs to review existing standards work in IPv6-only environment. 

Cheers,
--satoru




> 2017/10/18 6:52、d.lake@surrey.ac.ukのメール:
> 
> Uma
>  
> I agree that X2 is a complication but this is only used temporarily to provide a fast switch-over during a mobility event.  In terms of end-to-end communication, even during an X2 event, the topology and use of a tunnel anchored at the centre remains.
>  
> The issue is not the protocol but the time the underlying equipment takes to update the tunnel path.
>  
> At the moment (note – AT THE MOMENT!) the use-case which requires the most expeditious switch-over and is least tolerant to packet drops due to mobility events is VoLTE and it survives very well in current S1 and X2 handover systems.
>  
> I think this - “I am not sure who is “we”  (I would see that as 3GPP).”   - may be where we are struggling!  Until we have a use-case which patently fails using the current anchored GTP system, we are going to find it very hard to have an alternative solution considered.
>  
> We need to work with 3GPP on this….
>  
> David
>  
>  
>  
> From: Uma Chunduri [mailto:uma.chunduri@huawei.com] 
> Sent: 17 October 2017 14:39
> To: Lake D Mr (PG/R - Elec Electronic Eng) <d.lake@surrey.ac.uk>; rgm@htt-consult.com; sarikaya@ieee.org; satoru.matsushima@gmail.com
> Cc: 5gangip@ietf.org
> Subject: RE: [5gangip] To initiate user-plane study work in 3GPP
>  
> David,
>  
> Agree mostly on what you said.  2 comments though..
>  
>  
> > Mobility events are handled quickly and with minimal packet loss
>  
> I don’t think so. It’s an overhead for RAN mobility (X2 tunnels creation and additional control signalling for the same) and similar complication for UPF mobility.
>  
> > However, for NEW 5G use-cases such as Ultra-Low Latency and edge-based services we should be considering whether GTP is the correct choice provided we can meet the commercial and regulatory requirements of the MNOs in terms of LI and charging.
>  
> I am not sure who is “we”  (I would see that as 3GPP).
>  
>  
> But it’s good to put proposals  to show what layer 3 mobility entails -  like the one Bob mentioned below or  what Dino indicatedhttps://www.ietf.org/mail-archive/web/5gangip/current/msg00571.html
>  
>  
> --
> Uma C.
>  
> From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of d.lake@surrey.ac.uk
> Sent: Tuesday, October 17, 2017 2:15 PM
> To: rgm@htt-consult.com; sarikaya@ieee.org; satoru.matsushima@gmail.com
> Cc: 5gangip@ietf.org
> Subject: Re: [5gangip] To initiate user-plane study work in 3GPP
>  
> Bob
>  
> This is the key statement for me:
>  
> “A study group would have to work out what services GTP provides”
>  
> Both in this group and related efforts (e.g. IDEAS at IETF, NGP at ETSI), we need to consider how it is that mobile networks are built.
>  
> In terms of P2P, traffic on today’s mobile networks is predominantly anchored at a central point, not P2P despite the associated engineering inefficiencies.   There are very good reasons for this:
>  
> 	• It makes LI very easy to implement
> 	• It makes association of traffic with user clear allowing simple billing mechanisms
> 	• Mobility events are handled quickly and with minimal packet loss
>  
> In terms of the major use-cases today (voice over LTE and mobile broadband) as they move to 5G, I really don’t see any need to change the underlying tunnelling protocol because It Works. 
>  
> However, for NEW 5G use-cases such as Ultra-Low Latency and edge-based services we should be considering whether GTP is the correct choice provided we can meet the commercial and regulatory requirements of the MNOs in terms of LI and charging.
>  
> David
>  
> From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of Robert Moskowitz
> Sent: 17 October 2017 05:52
> To: sarikaya@ieee.org; Satoru Matsushima <satoru.matsushima@gmail.com>
> Cc: 5gangip@ietf.org
> Subject: Re: [5gangip] To initiate user-plane study work in 3GPP
>  
> Behcet and Satoru,
> 
> Last year I did a study of GTPv1U and worked out a different approach that would better support P2P communications without the need of a home proxy agent.  You can see part of it in:
> 
> draft-moskowitz-hip-ipnhip-02.txt
> 
> But I learned that there is tremendous resistance to any change away from GTP, even a partial change.  A study group would have to work out what services GTP provides.  Which services it does well and which it does poorly.  Then how to better meet the service needs today and going forward.
> 
> Bob
> 
> On 10/16/2017 04:12 PM, Behcet Sarikaya wrote:
> Hi Satoru,
> 
> Thanks for the info.
> 
> Can you please explain the objective items in your WID?
> 
> It seems like according to TR 29.891 that you mentioned, Release 15 user plane protocol is GTPv1U and control plane protocol for SBA is HTTP.
> 
> Regards,
> Behcet
>  
> On Mon, Oct 16, 2017 at 4:13 AM, Satoru Matsushima <satoru.matsushima@gmail.com> wrote:
> FYI. I’d submit a contribution to propose a new study item which is to initiate user-plane protocol study work in 3GPP CT4 WG.
> 
> http://www.3gpp.org/ftp/tsg_ct/WG4_protocollars_ex-CN4/TSGCT4_80_Kochi/Docs/C4-175098.zip
> 
> Please take a look at the doc from above link. I'd appreciate any your support if you think it makes sense.
> 
> Cheers,
> --satoru
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip
>  
>  
> 
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip
>  

_______________________________________________
5gangip mailing list
5gangip@ietf.org
https://www.ietf.org/mailman/listinfo/5gangip