Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
Arashmid Akhavain <arashmid.akhavain@huawei.com> Fri, 06 July 2018 20:57 UTC
Return-Path: <arashmid.akhavain@huawei.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 369BC130EA8 for <dmm@ietfa.amsl.com>; Fri, 6 Jul 2018 13:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7A0VePdoaFLg for <dmm@ietfa.amsl.com>; Fri, 6 Jul 2018 13:57:00 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 24632130DC8 for <dmm@ietf.org>; Fri, 6 Jul 2018 13:57:00 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id DE8D61657FA39 for <dmm@ietf.org>; Fri, 6 Jul 2018 21:56:55 +0100 (IST)
Received: from YYZEML703-CHM.china.huawei.com (10.218.33.73) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 6 Jul 2018 21:56:57 +0100
Received: from YYZEML702-CHM.china.huawei.com ([169.254.6.148]) by YYZEML703-CHM.china.huawei.com ([169.254.5.242]) with mapi id 14.03.0382.000; Fri, 6 Jul 2018 16:56:53 -0400
From: Arashmid Akhavain <arashmid.akhavain@huawei.com>
To: "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
Thread-Index: AQHUFVGdq6XAt58/PUWVijs4IXASkKSCpMug
Date: Fri, 06 Jul 2018 20:56:52 +0000
Message-ID: <D57109449177B54F8B9C093953AC5BCD74BC965B@YYZEML702-CHM.china.huawei.com>
References: <152347061706.2098.5631070563392014331.idtracker@ietfa.amsl.com> <D764EE74.2BD14D%sgundave@cisco.com>
In-Reply-To: <D764EE74.2BD14D%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.193.61.47]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/ALJ5qtYGGXkJZu3XvDchRJ16LnU>
Subject: Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.26
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 06 Jul 2018 20:57:04 -0000
Hi Sri, We might also want to add draft-camarillo-dmm-srv6-mobile-pocs-00 under "Related Documents". Also, we might want to say something like: "Although we will NOT pick a particular approach, we will be ready to provide further assistance to 3GPP regarding the technical details of different candidates." So, what happens next? We wait for their reply? Cheers, Arashmid > -----Original Message----- > From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli > (sgundave) > Sent: 06 July 2018 13:49 > To: dmm@ietf.org > Subject: Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on > User Plane Protocol in 5GC" > > We plan to send the following response to 3GPP CT4. If you have any quick > comments/corrections/suggestions, please let us know in a day. > > > > ³ > Thank you for your Liaison request (Reference: CP-173160) and for sharing > the information on the status of the CT4 study item on user-plane protocol > for 5GC. The IETF DMM working group wants to acknowledge your request > and want to share the following update. > > IETF DMM working is currently reviewing various proposals on approaches > for realizing optimizations in user-plane for mobile packet core. These > proposals include protocol specifications based on new/existing protocols > and proposals covering requirements/analysis/comparison of various > approaches. At this point of time, some of these documents are working > group documents and some are individual submissions and yet to be > adopted as working group documents. Based on the working group interest, > feedback charter-scope, the working group may choose to adopt some of > these work items as working group documents and at that time will seek > feedback from 3GPP. > > We also would like to state that the DMM working group will not be in a > position to pick a single approach/solution as THE approach for user-plane > optimization. Most likely the working group may standardize more than one > approach, but will characterize each of these approaches based on its > technical capabilities and limitations. This approach would be consistent with > the approach that IETF took with IPv6 transitioning work, where IETF > standardized multiple approaches including DSLite, NAT64, Gi-DSLite and > other approaches. > > Finally, IETF would like to point 3GPP to the following documents under > consideration. > > http://www.ietf.org/id/draft-bogineni-dmm-optimized-mobile-user-plane- > 01.tx > t (Individual submission) > > https://www.ietf.org/internet-drafts/draft-hmm-dmm-5g-uplane-analysis- > 00.tx > t (Individual submission) > > > Related Documents: > > > https://www.ietf.org/id/draft-ietf-dmm-srv6-mobile-uplane-02.txt (Working > group document) > > > Link to DMM Pages: > > https://datatracker.ietf.org/wg/dmm/documents/ > > > > Please let us know if you need any additional information. > " > > ----- > > > > > > > > > On 4/11/18, 11:16 AM, "Liaison Statement Management Tool" > <lsmt@ietf.org> > wrote: > > >Title: CP-173160: New Study Item on User Plane Protocol in 5GC > >Submission Date: 2018-04-11 URL of the IETF Web page: > >https://datatracker.ietf.org/liaison/1572/ > >Please reply by 2018-07-20 > >From: Satoru Matsushima <satoru.matsushima@g.softbank.co.jp> > >To: Sri Gundavelli <sgundave@cisco.com>,Dapeng Liu > ><maxpassion@gmail.com> > >Cc: Dapeng Liu <maxpassion@gmail.com>,Terry Manderson > ><terry.manderson@icann.org>,Distributed Mobility Management > Discussion > >List <dmm@ietf.org>,Sri Gundavelli <sgundave@cisco.com>,Suresh > Krishnan > ><suresh@kaloom.com> Response Contacts: > >georg.mayer.huawei@gmx.com,3GPPLiaison@etsi.org > >Technical Contacts: > >Purpose: For action > > > >Body: 1. Overall Description: > >3GPP working group of CT4 (Core and Terminal) would like to inform the > >IETF that CT4 has initiated a study item on user plane protocol in 5GC > >for Release-16 of 5G phase 2 (see CP-173160). > > > >Based on the outcome from the IETF / 3GPP Coordination meeting at > >IETF#100, 3GPP CT4 got aware that IETF DMM WG is currently working on a > >possible candidate protocol for the 3GPP 5G user plane protocol. > > > >3GPP CT4 wants to emphasize that currently there is no related > >evaluation ongoing in 3GPP. Nevertheless, a study item was approved for > >such a study to start in the second half of 2018. The study will > >evaluate between existing solutions within 3GPP and other protocols, > >based on the Release > >16 stage 2 (system architecture) requirements. > > > >3GPP CT4 would like to point IETF DMM to the following specifications > >on GTP-U. The Release 16 stage 2 requirements are not yet known but it > >is worth looking at latest GTP-U spec which will be evaluated through > >the study as the existing protocol. > > > >€ [1] 3GPP TS 29.281 (V15.1.0): GPRS Tunnelling Protocol User Plane > >(GTPv1-U) > > > > > >Following technical report provides information of how 3GPP considered > >GTP-U apply to user plane of 5G_ph1: > > > >€ [2] 3GPP TR 29.891 (V15.0.0): 5G System Phase 1; CT4 Aspects > > > > > >Furthermore, 3GPP would like to give the following general guidance to > >IETF DMM, regarding user plane transport within 3GPP networks. These > >are technical specifications that include also the necessary > >information to understand which architectural, QoS, security-related > >and high-level requirements GTP-U currently complies to within 5G_ph1. > > > >€ [3] 3GPP TS 23.501 (V15.0.0): System Architecture for the 5G System > >€ [4] 3GPP TS 23.502 (V15.0.0): Procedures for the 5G System > >€ [5] 3GPP TS 23.503 (V15.0.0): Policy and Charging Framework for the > 5G > >System > >€ [6] 3GPP TS 33.501 (V0.6.0): Security Architecture (work in progress) > > > >2. Actions: > >To IETF DMM: > >ACTION: CT4 respectfully asks IETF DMM to provide any information > that > >may be relevant to the above CT4 work by July 2018. > > > > > >3. Date of Next CT and CT4 Meetings: > >CT4#83 26th Feb 2nd Mar 2018 Montreal, CAN > >CT#79 19th 20th Mar 2018 Chennai, India > >CT4#84 16th 20th April 2018 Kunming, China > >CT4#85 21st 25th May 2018 Osaka, Japan > >CT#80 11th 12th June 2018 La Jolla, USA > >CT4#85-bis 9th 13th July 2018 TBD, France > >CT4#86 20st 24th Aug 2018 TBD, USA > >Attachments: > > > > CP-180116 > > > >https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2018-04-11-3gpp-t > >sgc > >t-ct4-dmm-cp-173160-new-study-item-on-user-plane-protocol-in-5gc-attach > >men > >t-1.doc > > > > _______________________________________________ > dmm mailing list > dmm@ietf.org > https://www.ietf.org/mailman/listinfo/dmm
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- [DMM] New Liaison Statement, "CP-173160: New Stud… Liaison Statement Management Tool
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Charlie Perkins
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Uma Chunduri
- Re: [DMM] [E] Re: New Liaison Statement, "CP-1731… Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Satoru Matsushima
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Bogineni, Kalyani
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Arashmid Akhavain
- Re: [DMM] New Liaison Statement, "CP-173160: New … Luca Muscariello
- Re: [DMM] New Liaison Statement, "CP-173160: New … Jordan Augé
- Re: [DMM] New Liaison Statement, "CP-173160: New … Giovanna Carofiglio (gcarofig)
- Re: [DMM] New Liaison Statement, "CP-173160: New … Sri Gundavelli (sgundave)