Re: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document

Sridhar Bhaskaran <sridhar.bhaskaran@huawei.com> Fri, 16 November 2018 08:17 UTC

Return-Path: <sridhar.bhaskaran@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 EDF32124D68 for <dmm@ietfa.amsl.com>; Fri, 16 Nov 2018 00:17:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 67xMzCLC8Xul for <dmm@ietfa.amsl.com>; Fri, 16 Nov 2018 00:17:44 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 F3B13130E50 for <dmm@ietf.org>; Fri, 16 Nov 2018 00:17:43 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 1D0E3A1FB6648; Fri, 16 Nov 2018 08:17:40 +0000 (GMT)
Received: from BLREML702-CAH.china.huawei.com (10.20.4.171) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 16 Nov 2018 08:17:41 +0000
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.69]) by blreml702-cah.china.huawei.com ([::1]) with mapi id 14.03.0415.000; Fri, 16 Nov 2018 13:47:26 +0530
From: Sridhar Bhaskaran <sridhar.bhaskaran@huawei.com>
To: "d.lake=40surrey.ac.uk@dmarc.ietf.org" <d.lake=40surrey.ac.uk@dmarc.ietf.org>, "homma.shunsuke@lab.ntt.co.jp" <homma.shunsuke@lab.ntt.co.jp>, "dmm@ietf.org" <dmm@ietf.org>, "david.i.allan@ericsson.com" <david.i.allan@ericsson.com>
CC: "s.homma0718+ietf@gmail.com" <s.homma0718+ietf@gmail.com>
Thread-Topic: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document
Thread-Index: AdR8XE96oLekQbpPTFmeddzrqRcXkwAOdBAAAACzQ4AAOupP8A==
Date: Fri, 16 Nov 2018 08:17:25 +0000
Message-ID: <0E42DD26875E1748992B1E3F732A36AE0134F278@BLREML503-MBX.china.huawei.com>
References: <CO1PR15MB109589470678B3C515CC60D7D0C30@CO1PR15MB1095.namprd15.prod.outlook.com> <e34b74d0-2125-0d8a-9da7-8bbd34272c2e@lab.ntt.co.jp> <DB6PR0601MB2310594DF39A30A85B10B714B5DC0@DB6PR0601MB2310.eurprd06.prod.outlook.com>
In-Reply-To: <DB6PR0601MB2310594DF39A30A85B10B714B5DC0@DB6PR0601MB2310.eurprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.201.195.21]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/sBKfmbgQnQdSv0gz5Zmyg2mQB8s>
Subject: Re: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Nov 2018 08:17:47 -0000

Hi David Lake,

Could you please clarify what is your reference for the following statement?

>> The CT4 study for future user-plane makes it clear ***that for cross-domain connections GTP is problematic on N9**** and alternatives could be considered.

Regards
Sridhar Bhaskaran
 
-----Original Message-----
From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of d.lake=40surrey.ac.uk@dmarc.ietf.org
Sent: Thursday, November 15, 2018 3:09 PM
To: homma.shunsuke@lab.ntt.co.jp; dmm@ietf.org; david.i.allan@ericsson.com
Cc: s.homma0718+ietf@gmail.com
Subject: Re: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document

Dave

I agree with you.  In Rel 15 it is clear that the user plane protocol on both N3 and N9 is GTP.

The CT4 study for future user-plane makes it clear that for cross-domain connections GTP is problematic on N9 and alternatives could be considered.

The timeframe is Rel 16 and the working document is TR 29.892.   

So far there are TWO candidate protocols in the document:

1) GTP
2) SRv6

However, this is a working document and there is plenty of scope to add other candidates in advance of the adoption of the output of CT4 (not sure what date that is - my guess would be sometime round the end of 2019?)

So I think IN SCOPE for DMM is suggesting, detailing, explaining new User Plane candidate protocols.

OUT OF SCOPE of the DMM is deciding which of those protocols makes it into Rel 16.

Surely there are more than 2 candidate protocols we could consider for N3 and N9!?

David

-----Original Message-----
From: dmm <dmm-bounces@ietf.org> On Behalf Of Shunsuke Homma
Sent: 15 November 2018 09:19
To: dmm@ietf.org; david.i.allan@ericsson.com
Cc: s.homma0718+ietf@gmail.com
Subject: Re: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document

Hi Dave,

Thank you for reviewing our draft and sending your thought for the adoption.

When I reviewed the charter I couldn't find any text to make the draft to be out of scope. Could you please elaborate it with the text in the charter?

Best regards,

Shunsuke


On 2018/11/15 6:52, David Allan I wrote:
> HI
> 
> AFAIK 3GPP CT4 is looking for work it can adopt, and has indicated 
> that it wishes to perform the analysis itself. When they were directed 
> to this document in the recent IETF DMM liaison, it  resulted in a 
> liaison reply clearly indicated they would define their own criteria.
> 
> https://datatracker.ietf.org/liaison/1590/
> 
> However in the draft it states in the introduction: "However we 
> believe that to provide adequate information for 3GPP, we need to 
> clearly understand what the current user plane protocol is in Release 
> 15, and architectural requirements for the user plane." And in the 
> conclusion "Our conclusion here is that we suggest the UP protocol 
> study work in 3GPP takes into account the evaluation aspects described 
> in Section 5.", there is more, but I do not feel a need to be pedantic about it.
> 
> So the purpose of this draft seems to explicitly be to do work for 
> 3GPP that they have explicitly said they DO NOT WANT.
> 
> At the same time I do not see anything in the charter that suggests we 
> should be doing this work either.  It would appear to have little to 
> do with DMM's chartered direction.
> 
> As such I am opposed to adoption of the draft.
> 
> Cheers
> 
> Dave
> 
> 
> 
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
> 


--
----------------------------------
Shunsuke Homma
<homma.shunsuke@lab.ntt.co.jp>
TEL: +81 422 59 3486
FAX: +81 422 60 7460

NTT Network Service Systems Labs.
Musashino city, Tokyo, Japan
----------------------------------

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

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