Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane Protocol in 5GC"

Jordan Augé <jordan.auge@cisco.com> Thu, 19 July 2018 13:56 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 3D5FB130F72 for <dmm@ietfa.amsl.com>; Thu, 19 Jul 2018 06:56:41 -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 RlULib1Jsd43 for <dmm@ietfa.amsl.com>; Thu, 19 Jul 2018 06:56:36 -0700 (PDT)
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 BDCCE130EA9 for <dmm@ietf.org>; Thu, 19 Jul 2018 06:56:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7757; q=dns/txt; s=iport; t=1532008595; x=1533218195; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=nL0Yp/Lv/mlScVjeSBwsRcQVIHMn2IVR6StZdV6Aiw0=; b=Jjp0cd6kwk916PDhChetsn+Jhxj9BxLr8Qo2SXIty/Ooiz54ENWJLB8P 0QXdK9mi9IXMkH1D7ge3g/cOCnYY9+HIUs0Jq5mXxjUcTYGtaSB3i7h/u bNfLL2tq8Ij608YyL8hJ2FmnSmDufnAEiPjEDIMqkJaY1mrNsoeOQgIXX k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CtAQAbmFBb/xbLJq1cGQEBAQEBAQEBAQEBAQcBAQEBAYQwbRIohT6GRF+NWINtiQaISBSBZgsjhEkCgyY0GAECAQECAQECbRwMhTYBAQEBAgE6LgoHBQcECxEEAQEBCRUJBw8BNgkIGRuDBoF3CA+qbIpLixiDdC6BQYFYAoEtARIBhXUCh0mKLYdyBwKGDYpjQ4NPiBaIAII/hzcCBAYFAhSBQThhcTM9UII1ATMJghwMCxGDNIUUhVojMIk1gjkBAQ
X-IronPort-AV: E=Sophos;i="5.51,374,1526342400"; d="scan'208";a="5222123"
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; 19 Jul 2018 13:56:33 +0000
Received: from adreena.localnet ([10.61.230.146]) (authenticated bits=0) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPSA id w6JDuWfS014726 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Jul 2018 13:56:33 GMT
From: Jordan Augé <jordan.auge@cisco.com>
To: dmm@ietf.org
Cc: Arashmid Akhavain <arashmid.akhavain@huawei.com>, "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org>
Date: Thu, 19 Jul 2018 09:56:31 -0400
Message-ID: <3483862.hWH2oe9iMD@adreena>
Organization: Cisco Systems
In-Reply-To: <D57109449177B54F8B9C093953AC5BCD74BEC94C@YYZEML701-CHM.china.huawei.com>
References: <D7739626.1DBE6%sgundave@cisco.com> <D57109449177B54F8B9C093953AC5BCD74BEC94C@YYZEML701-CHM.china.huawei.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.61.230.146, [10.61.230.146]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/MrqN9D5cw0nCczUqMM_dbwT4VP8>
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.27
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, 19 Jul 2018 13:56:41 -0000

I am in support of it too.

Cheers,
-- Jordan

> I agree with the current LS
> 
> Arashmid
> 
> From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli
> (sgundave) Sent: Tuesday, July 17, 2018 3:49 PM
> To: dmm@ietf.org
> Subject: Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User
> Plane Protocol in 5GC"
> 
> All:
> 
> Thank you for the discussion today in the DMM meeting on the Liaison
> response to 3GPP CT4 group.  There was one comment at the microphone that
> we should not reference individual I-D's (non working documents) in the
> response. But, as we discussed and per the below summary, we have explained
> the criteria for inclusion / exclusion of I-D's.  If you still object to
> it, please let us know. We are extending the deadline for comments till
> Friday, 20th of July.
> 
> Dapeng & Sri
> 
> 
> 
> 
> Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on User Plane
> Protocol in 5GC"
> 
> "Sri Gundavelli (sgundave)" <sgundave@cisco.com<mailto:sgundave@cisco.com>>
> Mon, 09 July 2018 17:35 UTCShow
> header<https://mailarchive.ietf.org/arch/browse/dmm/>
> 
> Ok!  Thank you Kalyani and Arashmid.
> 
> 
> 
> 
> 
> Change-1: Add to the last sentence.
> 
> 
> 
> "Also please provide any evaluation criteria that could help us in
> progressing our work to support 5G."
> 
> 
> 
> Change-2: Add to the second sentence, of second paragraph
> 
> 
> 
> + " and building proof of concept demos."
> 
> 
> 
> 
> 
> Now, I need to pull this back for edits. Let me do that.  I hope this makes
> a difference in CT4 discussions.
> 
> 
> 
> All - Let us know if you have any issue with these additions, or to the
> original proposed text.
> 
> 
> 
> 
> 
> Sri
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On 7/9/18, 9:41 AM, "Bogineni, Kalyani"
> <Kalyani.Bogineni@VerizonWireless.com<mailto:Kalyani.Bogineni@VerizonWirele
> ss.com<mailto:Kalyani.Bogineni@VerizonWireless.com%3cmailto:Kalyani.Bogineni
> @VerizonWireless.com>>> wrote:
> 
> 
> 
> Sri:
> 
> 
> 
> Here is one edit in the last sentence to allow IETF to take feedback from
> 3GPP:
> 
> 
> 
> "Please let us know if you need any additional information. Also please
> provide any evaluation criteria that
> 
> could help us in progressing our work to support 5G."
> 
> 
> 
> Kalyani
> 
> 
> 
> -----Original Message-----
> 
> From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli
> (sgundave)
> 
> Sent: Monday, July 9, 2018 11:51 AM
> 
> To: Arashmid Akhavain
> <arashmid.akhavain@huawei.com<mailto:arashmid.akhavain@huawei.com<mailto:ar
> ashmid.akhavain@huawei.com%3cmailto:arashmid.akhavain@huawei.com>>>;
> dmm@ietf.org<mailto:dmm@ietf.org<mailto:dmm@ietf.org%3cmailto:dmm@ietf.org>
> >
> 
> Subject: [E] Re: [DMM] New Liaison Statement, "CP-173160: New Study Item on
> User Plane Protocol in 5GC"
> 
> 
> 
> Hi Arashmid/Kalyani,
> 
> 
> 
> Thank you both for your feedback.
> 
> 
> 
> Yes, we thought its better to keep the focus on problem statement and
> requirement analysis. We don't want to prematurely high-light any solution
> documents to SDO. Which did not go through proper review process, as it
> will only result in confusing them.
> 
> 
> 
> 
> 
> Having said that however, I think a general statement about proof of
> 
> concepts can help the cause.
> 
> 
> 
> The current text provides an high-level update and status on where the WG is
> going, and a also a pointer to all documents under review. I am personally
> not keen on making additional edits, unless you guys think the change is
> absolutely needed and will make a difference in CT4 discussion.
> 
> So, if you are keen on seeing any such changes, please propose the exact
> text. But, if you have no objections to the current response, we can let
> this go. In future liaisons we can have detailed technical exchanges.
> 
> 
> 
> 
> 
> Sri
> 
> 
> 
> 
> 
> 
> 
> On 7/9/18, 7:23 AM, "Arashmid Akhavain"
> <arashmid.akhavain@huawei.com<mailto:arashmid.akhavain@huawei.com<mailto:ar
> ashmid.akhavain@huawei.com%3cmailto:arashmid.akhavain@huawei.com>>>
> 
> wrote:
> 
> 
> 
> Hi Sri,
> 
> 
> 
> Thank you for your clarifying email. The POC draft talks about the SRv6
> 
> demos and I can see how it can be seen as a document advocating a
> 
> particular solution strategy.
> 
> So, I agree that we should stay away from specific POCs and drafts in
> 
> the LS. Having said that however, I think a general statement about
> 
> proof of concepts can help the cause.
> 
> 
> 
> At this point I think it is more important to discuss the GAPs in
> 
> existing system rather than focusing on different solutions. That's why
> 
> I really like what
> 
> draft-hmm-dmm-5g-uplane-analysis-00 is trying to do.
> 
> 
> 
> Cheers,
> 
> Arashmid
> 
> 
> 
> -----Original Message-----
> 
> From: Sri Gundavelli (sgundave) [mailto:sgundave@cisco.com]
> 
> Sent: 08 July 2018 19:29
> 
> To: Arashmid Akhavain
> <arashmid.akhavain@huawei.com<mailto:arashmid.akhavain@huawei.com<mailto:ar
> ashmid.akhavain@huawei.com%3cmailto:arashmid.akhavain@huawei.com>>>;
> dmm@ietf.org<mailto:dmm@ietf.org<mailto:dmm@ietf.org%3cmailto:dmm@ietf.org>
> >
> 
> Subject: Re: New Liaison Statement, "CP-173160: New Study Item on
> 
> User Plane Protocol in 5GC"
> 
> Hi Arashmid,
> 
> We were trying to avoid this debate on inclusion/exclusions of
> 
> individual I-  D's, but looks like we are just doing that. That is
> 
> fine. Lets review the  situation.
> 
> The approach on what documents to be explicitly listed is based on
> 
> the following principles.
> 
> #1 Provide references to DMM WG documents that have any relation to
> 
> the  study item in 5GC.
> 
> #2 Include references to individual I-D's that have done broader
> 
> requirement/solution analysis/comparative study on the topic of mobile
> 
> user  plane optimization; documents that are not advocating a specific
> 
> solution.
> 
> We also wanted to apply the constraint of documents that have had
> 
> substantial discussions in the working group. In other words,
> 
> documents that  were reviewed by the WG and received significantly
> 
> high number of  comments.
> 
> For #1: we have included draft-ietf-dmm-srv6-mobile-uplane-02.txt, as
> 
> its a  WG document on track for standardization.
> 
> For #2: we have included draft-bogineni as there were many
> 
> discussions/presentations/conference calls on that draft. We have also
> 
> included draft-hmm-dmm-5g-uplane-analysis-00, but however this draft
> 
> was  published recently and had near zero discussions in the WG. But
> 
> given the  quality of the document and noting that its about
> 
> requirement analysis and  as its not advocating a specific solution,
> 
> we chose to keep this document in  the list.
> 
> We have not included any other I-D's which have not had enough
> 
> discussions  and which are solution specific documents. Not that we
> 
> have not established  the draft applicability to the 3GPP study item.
> 
> These include:
> 
> draft-auge-dmm-hicn-mobility-00,
> 
> draft-auge-dmm-hicn-mobility-deployment-options-00,
> 
> draft-camarillo-dmm-srv6-mobile-pocs-00,
> 
> draft-gundavelli-dmm-mfa-00
> 
> draft-homma-dmm-5gs-id-loc-coexistence-01,
> 
> Now, if this sounds unreasonable or unfair, we have two options.
> 
> #1 Remove references to all individual drafts and only include WG
> 
> documents
> 
> #2: Include every single I-D (WG and non WG) documents.
> 
> All - Please comment.
> 
> Sri