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

Shunsuke Homma <homma.shunsuke@lab.ntt.co.jp> Thu, 15 November 2018 09:19 UTC

Return-Path: <homma.shunsuke@lab.ntt.co.jp>
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 779BE130DC3 for <dmm@ietfa.amsl.com>; Thu, 15 Nov 2018 01:19:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 UfWLwmaFEdC8 for <dmm@ietfa.amsl.com>; Thu, 15 Nov 2018 01:19:09 -0800 (PST)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by ietfa.amsl.com (Postfix) with ESMTP id 6EBCC130DBE for <dmm@ietf.org>; Thu, 15 Nov 2018 01:19:09 -0800 (PST)
Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id wAF9Ix04016538; Thu, 15 Nov 2018 18:18:59 +0900
Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 1727E6390ED; Thu, 15 Nov 2018 18:18:59 +0900 (JST)
Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 0C0606390C0; Thu, 15 Nov 2018 18:18:59 +0900 (JST)
Received: from [IPv6:::1] (unknown [129.60.13.61]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id F018440090B; Thu, 15 Nov 2018 18:18:58 +0900 (JST)
References: <CO1PR15MB109589470678B3C515CC60D7D0C30@CO1PR15MB1095.namprd15.prod.outlook.com>
From: Shunsuke Homma <homma.shunsuke@lab.ntt.co.jp>
Message-ID: <e34b74d0-2125-0d8a-9da7-8bbd34272c2e@lab.ntt.co.jp>
Date: Thu, 15 Nov 2018 18:18:52 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CO1PR15MB109589470678B3C515CC60D7D0C30@CO1PR15MB1095.namprd15.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
To: dmm@ietf.org, david.i.allan@ericsson.com
Cc: s.homma0718+ietf@gmail.com
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/6JK10dNIs5wnyTxaYoTKyhIpJsM>
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: Thu, 15 Nov 2018 09:19:11 -0000

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
----------------------------------