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

Satoru Matsushima <satoru.matsushima@gmail.com> Fri, 17 November 2017 02:43 UTC

Return-Path: <satoru.matsushima@gmail.com>
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 3EA42126CD8 for <5gangip@ietfa.amsl.com>; Thu, 16 Nov 2017 18:43:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 dgoNnFTyAORe for <5gangip@ietfa.amsl.com>; Thu, 16 Nov 2017 18:43:07 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FCCB124D68 for <5gangip@ietf.org>; Thu, 16 Nov 2017 18:43:07 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id b6so834367pff.10 for <5gangip@ietf.org>; Thu, 16 Nov 2017 18:43:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NvnZvy8mpYNsq7ONygRlppKiiQlBFdauBhgETwAFv1A=; b=UIu67MP/KMGpwIhZey8qu/s1qDag2Hl7WC19XLHT6T+jH+GwBigH7Jtx7sNj0u2Qgn eKdfhUip/K0kny0jDXg1Y9WHfQZuuqe7qD+9CBWH9K38sydOztVwUa01mHvYaMZm48Q5 B9klZbrI4uv7u+vrKC+iXyskjblh/eQHV5Na0RCv29EJbpz5lt/CVfbd0ar39mW0lRj7 1ff3z3pR1KuI79jPL0pj8YSs+vICnovV7fYJzaGqhPRyWyVB8d5x4em8El5tO1yQUTVm gFTzLKTn/x24PGBTOU/8UgZkMVM/BKjcdEYN/emPrGS9/vecX4snOsOBs/3QOelv/QWz g87w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NvnZvy8mpYNsq7ONygRlppKiiQlBFdauBhgETwAFv1A=; b=ooqmWE8DuHfqcBkqgLM1nlX0cMsO1Fi5vtgif5r4tIWor6DIk62mqL/DClIXVS1xZa KB//266G1Zw6ahMQBHL8AmODcqrx0pfJlQUOqW7B718c03BXL4epN6x07ol6Ht6ISPrJ 6sUDCylnobBvgyy5dCD32yPyJycbNK6UYbAbbmuReZuunzla6x85eEo5x5lEOWHiPS6C Yr1wwv/2m50X9W5cv25qmYukRhsq+AwuJ4VOwTrt8ORCkUgoq+3eDe2U/hdoy3buElCd /iucf0usq8KMUWS9oapytY4bIYxrxP+Ar5ue+QDVp0kzjjGlLdloF7Js6L3F3Pu8qXjx aiUg==
X-Gm-Message-State: AJaThX4mWa0dPXk2R8oQeCNNNmAv4Bgsxrx8OerEJMkzCI9ZBTpPTcq+ YOruIH0H96GN7XykFAZOS4fk3azP
X-Google-Smtp-Source: AGs4zMZQYMhUBrxmaZ1BszHXkRyxCPqAwBWb36lkCFDqRqzyumKjxHx9NFFUlzPlBoLxM9Nbkdv/Kg==
X-Received: by 10.98.68.8 with SMTP id r8mr429058pfa.161.1510886586338; Thu, 16 Nov 2017 18:43:06 -0800 (PST)
Received: from ?IPv6:2001:67c:370:1998:3047:a2c6:84ee:e705? ([2001:67c:370:1998:3047:a2c6:84ee:e705]) by smtp.gmail.com with ESMTPSA id w1sm3669164pgq.34.2017.11.16.18.43.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Nov 2017 18:43:05 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <6dc78589-5b9f-8b3d-3f5d-697462503d69@gmail.com>
Date: Fri, 17 Nov 2017 10:35:21 +0800
Cc: 5gangip@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <10849076-6A90-454A-925D-C1841D1C73A3@gmail.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> <65b9aefbd54c480581fc584e2e55f5a9@HE105831.emea1.cds.t-internal.com> <DC3DF722-2C36-4D2D-A89D-B6C8F8611893@gmail.com> <bcdc433a-d479-fad1-eb7d-9daec32c47d6@gmail.com> <24BA8F69-B5B8-4969-85A5-32C115F44BAE@gmail.com> <70a5e9be-95e3-5979-31cb-484e36a85e04@gmail.com> <D1E99252-42E3-41D6-85DB-4DDFB54E70D3@gmail.com> <6dc78589-5b9f-8b3d-3f5d-697462503d69@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/72s8ggmZfb8PsMC8qp-e-vmCb40>
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: Fri, 17 Nov 2017 02:43:10 -0000

Alex,

> 
> I understand then.  Thank you for the explanation.
> 
> I think there are some problems with this.  Multiple encapsulations lead
> to loss of efficiency.  This leads to lesser bandwidth.  For voice
> calls, this can mean less quality of voice, or longer connection
> establishment times.
> 

As Cameron replied in another thread, the header tax issue has been lesser while bandwidth increased. What I mention here is that complication to correlate those stacked layers each other to meet the requirements.

Connection establishment time issue seems different from that. It more likes a control-plane signaling procedure issue.


> For example, now in Singapour I experience very long connection
> establishment times on my phone with SIM from home.  My operator is an MVNO (Mobile Virtual Network Operator) whose transport depends on another operator in my home country.  Here is yet another operator.
> 
> On another hand, skype has same connection establishment time as when I
> am at home.

So yes, that is a kind of control-plane signaling procedure issue.

Cheers,
--satoru



> 
> Alex
> 
> Le 16/11/2017 à 07:36, Satoru Matsushima a écrit :
>> Alex,
>> Let us imagine a case where under VPN label is imposed by a transport
>> service operator who provides backhaul connectivity for multiple
>> mobile operators. And upper VPN label is imposed by a mobile operator
>> who need to create three or more VPNs for each mobile user-plane,
>> control-plane O&M and if any other purposes respectively even just
>> within the mobile operator for example.
>> Cheers, --satoru
>>> 2017/11/15 22:46、Alexandre Petrescu <alexandru.petrescu@gmail.com>の
>>> メール:
>>> Satoru,
>>> I see two distinct "VPN label" layers.  I can agree with two IP
>>> layers in same stack, but two VPN layers too?
>>> Arent these too many layers?
>>> For the question of which one of the realities happened in some
>>> operator - I can ask locally about which of these layers (VPN
>>> label, LSP label, VLAN ID, SMAC, DMAC, VPN label, LSP label, SMAC,
>>> DMAC) are seen at the PGW.
>>> Alex
>>> Le 13/11/2017 à 17:54, Satoru Matsushima a écrit :
>>>> Alex, You’re right as others have admitted. But you can see more
>>>> stacked layers underneath of GTP/UDP/IPv4 Please take a look at
>>>> the attached picture which one of the realities happened in some
>>>> operator. Cheers, --satoru
>>>>> 2017/11/12 20:26、Alexandre Petrescu
>>>>> <alexandre.petrescu@gmail.com
>>>>> <mailto:alexandre.petrescu@gmail.com>>のメール:
>>>>> Le 19/10/2017 à 04:52, Satoru Matsushima a écrit :
>>>>>> Thank you Dirk, Yes that presentation made by George has much
>>>>>> encouraged ietf community. Other key facts which the
>>>>>> justification text mentioned are following: o IAB statement
>>>>>> on IPv6 https://www.iab.org/2016/11/07/iab-statement-on-ipv6/ o IPv6
>>>>>> deployment measurement http://www.worldipv6launch.org/measurements/ We can see big
>>>>>> number of adoption rate for cellular operators especially in
>>>>>> US. T-Mobile US and Verizon Wireless exceed 80%, 47.51% for
>>>>>> ATT Wireless, and 59% for Sprint Wireless.
>>>>> YEs, these networks carry much IPv6, but is it carried mostly
>>>>> in GTP/UDP/IPv4?
>>>>> Alex
>>>>>> Cheers, --satoru
>>>>>>> 2017/10/19 2:17、<Dirk.von-Hugo@telekom.de
>>>>>>> <mailto:Dirk.von-Hugo@telekom.de>> <Dirk.von-
>>>>>>> Hugo@telekom.de <mailto:Dirk.von-Hugo@telekom.de>>のメール:
>>>>>>> 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
>>>>>> _______________________________________________ 5gangip
>>>>>> mailing list 5gangip@ietf.org <mailto:5gangip@ietf.org> https://www.ietf.org/mailman/listinfo/5gangip
>>>>> _______________________________________________ 5gangip mailing
>>>>> list 5gangip@ietf.org <mailto:5gangip@ietf.org> https://www.ietf.org/mailman/listinfo/5gangip