IETF Logo Mail Archive

Re: [5gangip] New Version Notification for draft-xyx-5gip-ps-00.txt

Uma Chunduri <uma.chunduri@huawei.com> Thu, 11 May 2017 23:40 UTC

Return-Path: <uma.chunduri@huawei.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 03614129C14 for <5gangip@ietfa.amsl.com>; Thu, 11 May 2017 16:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 9-ykgOyFVrBo for <5gangip@ietfa.amsl.com>; Thu, 11 May 2017 16:40:36 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EACC129A96 for <5gangip@ietf.org>; Thu, 11 May 2017 16:36:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DMT23192; Thu, 11 May 2017 23:36:06 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 12 May 2017 00:36:03 +0100
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.175]) by SJCEML703-CHM.china.huawei.com ([169.254.5.81]) with mapi id 14.03.0235.001; Thu, 11 May 2017 16:36:01 -0700
From: Uma Chunduri <uma.chunduri@huawei.com>
To: jouni korhonen <jouni.nospam@gmail.com>, "d.lake@surrey.ac.uk" <d.lake@surrey.ac.uk>
CC: "5gangip@ietf.org" <5gangip@ietf.org>, "cb.list6@gmail.com" <cb.list6@gmail.com>, "swmike@swm.pp.se" <swmike@swm.pp.se>, "samitac.ietf@gmail.com" <samitac.ietf@gmail.com>, "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>
Thread-Topic: [5gangip] New Version Notification for draft-xyx-5gip-ps-00.txt
Thread-Index: AQHSypvCuQDoUxxu9E+gtGC3D+ovWaHvxyBw
Date: Thu, 11 May 2017 23:36:01 +0000
Message-ID: <25B4902B1192E84696414485F5726854018A2F4C@SJCEML701-CHM.china.huawei.com>
References: <149376035152.21552.16267155218438524059.idtracker@ietfa.amsl.com> <CAC8QAcfXDAQsv1MsCu7RAtBF6LC7Y_v8zutz1hOYkcbbRKT_cw@mail.gmail.com> <340a9b7fbfe5408bbc2f6d56e839009f@HE105831.emea1.cds.t-internal.com> <alpine.DEB.2.02.1705041251310.30304@uplift.swm.pp.se> <CAD6AjGR6+KK5uMstJGDBM2X4RHSmONoZOrAe9JBFoc4Us78J5A@mail.gmail.com> <88b1db15dced45bca9427b042cc82192@HE105831.emea1.cds.t-internal.com> <CAKmdBpdSEC9ZM4YJC2zxC53JwMdNmZMxoOuXNyFR_VrA-ddCxw@mail.gmail.com> <AM2PR06MB0882823A2088E10804043331B5EC0@AM2PR06MB0882.eurprd06.prod.outlook.com> <7B4F8607-E7A3-4EB8-BC29-015BB8821553@gmail.com>
In-Reply-To: <7B4F8607-E7A3-4EB8-BC29-015BB8821553@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.213.49.77]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.5914F566.01B0, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.175, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: bc173199344ef18b20f08177fe8d7f34
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/XgUvWV6PHY3_Km6SY5GtTJHc478>
Subject: Re: [5gangip] New Version Notification for draft-xyx-5gip-ps-00.txt
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: Thu, 11 May 2017 23:40:39 -0000


	>The protocol choice will usually take place in “stage-3 groups". In this case it would be RAN3 afair. Their current working assumption for NG data transport (with a disclaimer) is already GTP - check TS38.414 & 38.424. 
                >Like it was with rel-8 the interesting & hectic part of the mobility takes place in RAN. Out of all efforts in rel-8 PMIP never made it into RAN par of the network. 
                >Too much legacy there.

+1. Indeed too much..
Mobility is always built on anchor based solution and AFAIS, even today it's difficult to move away even 
virtual use plane/EPC and non-3GPP access and few more items put pressure to have a different outcome.  
May be too much at stake for the deployed base..(remember 4G upgrade is still happening).

                >If there’s a desire to revert the TR38.801 decision on using GTP, the timeframe is getting tight. 
                >The good point is that RAN (S1, X2, etc) never used GTP-C as a control plane.

GTP is used on S1 (S1-C) and X2 for inter eNodeB data transfer during mobility (eNodeB).

--
Uma C.

v2.23.0 | Report a Bug | By Email