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

Jordan Augé <jordan.auge@cisco.com> Fri, 16 November 2018 10:11 UTC

Return-Path: <jordan.auge@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 0A774130DC6 for <dmm@ietfa.amsl.com>; Fri, 16 Nov 2018 02:11:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.97
X-Spam-Level:
X-Spam-Status: No, score=-14.97 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable 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 ebSt7r65l5KX for <dmm@ietfa.amsl.com>; Fri, 16 Nov 2018 02:11:23 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6570130E7F for <dmm@ietf.org>; Fri, 16 Nov 2018 02:11:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3997; q=dns/txt; s=iport; t=1542363083; x=1543572683; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=QwU8abuBQEcNurQH7DxC/MSbe8iDeDVIYuc5qk7aK8s=; b=Keu8ngrXvTaVvcDrPt9C1OvoEYv2gTQ6wM22UO+Auh7zXxlalMRLuBph TI09GESKbUmQe2Gxf1G4TZ9vdUDfZjagwem3oYnGFrDYyN7qg9o3o0u2r agc2hMXFH/NopflCFNyrbKWf3rH/aF+2ivyC+89omyPOHBYi6jICauRlb o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0APAAABl+5b/xbLJq1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUgMBAQEBAQsBAYJocBInhFqIFY0qiQeEeBGJJhSBZgsBARgNhEcCg3U1CA0BAwEBAgEBAm0cDEIBEAGEaAEBAQMBAQEbHTQLBQcECxEEAQEBCQwJEA8BEQYoCBmDIoFpAw0ID6h9hC0BAwKDSA2CFAWOG4ERgxKCVkUBAQOBGYEEgnaCBCICiRuWIS4HAoZ6hwKDQwqBToUHihuNNYEHiS0CBAYFAhSBSAI0gVUzPVCCbIInFxKITIU/PgMwAYQ1iS8BAQ
X-IronPort-AV: E=Sophos;i="5.56,239,1539648000"; d="scan'208";a="8032357"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Nov 2018 10:11:20 +0000
Received: from adreena.localnet ([10.228.33.121]) (authenticated bits=0) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPSA id wAGABKx7005511 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Nov 2018 10:11:20 GMT
From: Jordan Augé <jordan.auge@cisco.com>
To: dmm@ietf.org
Cc: d.lake=40surrey.ac.uk@dmarc.ietf.org
Date: Fri, 16 Nov 2018 11:11:22 +0100
Message-ID: <2843588.raliIjvE52@adreena>
Organization: Cisco Systems
In-Reply-To: <DB6PR0601MB2310594DF39A30A85B10B714B5DC0@DB6PR0601MB2310.eurprd06.prod.outlook.com>
References: <CO1PR15MB109589470678B3C515CC60D7D0C30@CO1PR15MB1095.namprd15.prod.outlook.com> <e34b74d0-2125-0d8a-9da7-8bbd34272c2e@lab.ntt.co.jp> <DB6PR0601MB2310594DF39A30A85B10B714B5DC0@DB6PR0601MB2310.eurprd06.prod.outlook.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Authenticated-User: augjorda
X-Outbound-SMTP-Client: 10.228.33.121, [10.228.33.121]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/qzyzF46sDjgvGnZNvYquutM3t8c>
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 10:11:26 -0000

Hi David,

To follow up on your last question, I could refer to a draft initiated by 
Kalyani which so far has material about candidate protocols and includes SRv6, 
LISP, ILA and hICN, and was part of the DMM answer to the 3GPP CT4 study item.

https://tools.ietf.org/html/draft-bogineni-dmm-optimized-mobile-user-plane-01

Regards,
-- Jordan

> 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