Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Sat, 07 July 2018 06:25 UTC
Return-Path: <sgundave@cisco.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 82C29130E1C for <dmm@ietfa.amsl.com>; Fri, 6 Jul 2018 23:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 DmeOXX8RVG0C for <dmm@ietfa.amsl.com>; Fri, 6 Jul 2018 23:25:33 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D362130DDA for <dmm@ietf.org>; Fri, 6 Jul 2018 23:25:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10506; q=dns/txt; s=iport; t=1530944733; x=1532154333; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=oEg2jSH0hH1QEfIotbUjmWpgIHa5Sd2JYI0Kt/TSH0c=; b=hX0/FriFVyqOUJQUH1FpO+3hwMqxkQoHb9mDu8rUvFShEOPOAXeutpzK VsiQT7w9AfRyMkI/ATV1DfHWiQxLQPo+BDyqWUK4WG00lsPB2yasDeY13 Qq8ftfyC8A4gwBhUuv57T2YdGECzgYShBOK22MBlvzHzeKaOQX1voVR/h c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BkAgCfXEBb/4cNJK1bGQEBAQEBAQEBAQEBAQcBAQEBAYNJYn8oCoNwiASMNIIHgziEfox8gXoLGAuEA0YCF4IWITQYAQIBAQIBAQJtHAyFNgEBAQMBAQEhEToGCgcEAgEIEQECAQEBAQICIwMCAgIfBgsUAQIGCAIEARIJEoMGgWcDDQgPqTeCHIRbgjYNgS6BOoELh2OBVj+BDgGCYS6BQYEVQgEBA4FdJoJbglUCh0aKJIc6KwkChgZzhR5vghyBQoQMiA2HfYI6T4ZiAhETAYEkHTiBUnAVGiGCNQEzCYInHIhIhT5vAY5TgRoBAQ
X-IronPort-AV: E=Sophos;i="5.51,319,1526342400"; d="scan'208";a="423578559"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jul 2018 06:25:29 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w676PTgL014170 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 7 Jul 2018 06:25:29 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 7 Jul 2018 01:25:28 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Sat, 7 Jul 2018 01:25:28 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Arashmid Akhavain <arashmid.akhavain@huawei.com>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"
Thread-Index: AQHUFbtMPBqSKqUAHkiArHHl6pSDFQ==
Date: Sat, 07 Jul 2018 06:25:28 +0000
Message-ID: <D765A84B.2BD1F3%sgundave@cisco.com>
References: <152347061706.2098.5631070563392014331.idtracker@ietfa.amsl.com> <D764EE74.2BD14D%sgundave@cisco.com> <D57109449177B54F8B9C093953AC5BCD74BC965B@YYZEML702-CHM.china.huawei.com>
In-Reply-To: <D57109449177B54F8B9C093953AC5BCD74BC965B@YYZEML702-CHM.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.188.62]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C8078F94207CE14C94393CF80FECC4B3@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/zxg86i-E8Sc-1PYlouIc720Jj8I>
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: Sat, 07 Jul 2018 06:25:36 -0000
Hi Arashmid, Thanks for the feedback. I have added a link to the DMM WG pages and it has links to all the DMM documents. I think that should be OK, we don’t have to explicitly list out every single I-D at this stage. As we move forward and based on WG discussions/progress, we can provide more detailed feedback on each document. I suggest we keep this simple for now. > So, what happens next? We wait for their reply? This is just a response to the LS; more an information exchange on the status/progress. Regards Sri On 7/6/18, 1:56 PM, "Arashmid Akhavain" <arashmid.akhavain@huawei.com> wrote: >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)