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

Luca Muscariello <luca.muscariello@gmail.com> Thu, 19 July 2018 13:54 UTC

Return-Path: <luca.muscariello@gmail.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 E3388130E0D for <dmm@ietfa.amsl.com>; Thu, 19 Jul 2018 06:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ESInG1lWz_Pm for <dmm@ietfa.amsl.com>; Thu, 19 Jul 2018 06:54:48 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115B7130F52 for <dmm@ietf.org>; Thu, 19 Jul 2018 06:54:43 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id c135-v6so3084191ywa.0 for <dmm@ietf.org>; Thu, 19 Jul 2018 06:54:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VP4tgoHz7fEncYRg0eHwBtrea7Zk1TpO3oOqj1wmzKw=; b=n+2MRXBKQiOIvZTxfkzlh7jl17AAgRMZMY+1AxVTytAa4GfQ3lRfblbYCmNAwJLPi1 IcJfwSdpwQU6+3B/CpX+LShq7N6Lo6jbqlaATibi6m8m1sKKuElTrltvmHZ1jIlWXOOB 8clidtxzqx2Zc0nQutxNA+i6oIDFLwA2M1nBJXnMR40nVSjJzH8A3AaQC49TWqTdq7qL tkRW3ASAYZgbcBgaOxty72BQn/BkmvNt9J7AagZUvh0QHfUtybnpIe180yNxSxs/AgUI zrrD+ooYKcwAUm3iwb9+eDwdMnXuidL8gHNJwn5hbannZUojuWqtxSjRT90HyPX+JFTL f0Jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VP4tgoHz7fEncYRg0eHwBtrea7Zk1TpO3oOqj1wmzKw=; b=mnPqh00iPXT4AWSiIiQI8hBNlDdqH7WdaQ+8VHYamVvU9lqSSXx0oq7GOz1YU1tUYo Tlx9gzetjASRWKEiAoHod8qfzA/YrPoNnvD71bMEXDYSHQHN7TycuM6075HCFSnjqAHy YMFIR1E/iq0un/eat4Bm0so9J2WTf75IlCsnEGhkEA9TN0y9mwM28CrXKY57bLWi1TUT VVGiNYlVlGVdG0UMrtQ/P1MWNmGdsT2ALDmJeYibHJ/BHmgJHGF/SDVeW0KrPkU35Rpo 2P/qOkkvkJDLblDpGjHZoBdXZ/WChsxQvYsZN7avf1KDCS+XzIK88vYYr7hURM5+xsVM uC/Q==
X-Gm-Message-State: AOUpUlGhv8dUQxXADJQBrd9dQDuYR6pkhX5N2eDASSOz7V9JvZQJsTbM XJXduJpFCbqTIiQiX8oI7x7KY9ASbZi31Wgto3df0Wg0
X-Google-Smtp-Source: AAOMgpcG88h02BG0P2eXodx0pWNa+7hccPcY5bbzYpg4zoyA6sHVEHdO7bWwLyq77s8dc4TCBBD3N49WufV1rjNiXTE=
X-Received: by 2002:a81:a348:: with SMTP id a69-v6mr5147643ywh.142.1532008482156; Thu, 19 Jul 2018 06:54:42 -0700 (PDT)
MIME-Version: 1.0
References: <D7739626.1DBE6%sgundave@cisco.com> <D57109449177B54F8B9C093953AC5BCD74BEC94C@YYZEML701-CHM.china.huawei.com>
In-Reply-To: <D57109449177B54F8B9C093953AC5BCD74BEC94C@YYZEML701-CHM.china.huawei.com>
From: Luca Muscariello <luca.muscariello@gmail.com>
Date: Thu, 19 Jul 2018 09:54:30 -0400
Message-ID: <CAHx=1M5yoRioUJhi7LxxDim2Djz5=pirLEmjXxLJQbrU9w52-w@mail.gmail.com>
To: arashmid.akhavain@huawei.com
Cc: sgundave=40cisco.com@dmarc.ietf.org, dmm@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005f35b105715a85a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/l4xrxSuxM4vBuETZJtAJer0ddo4>
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:54:52 -0000

+1

On Thu, Jul 19, 2018 at 9:53 AM Arashmid Akhavain <
arashmid.akhavain@huawei.com> wrote:

> 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> 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@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 <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>>; dmm@ietf.org<mailto: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>>
>
> 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 <sgundave@cisco.com>]
>
> Sent: 08 July 2018 19:29
>
> To: Arashmid Akhavain <arashmid.akhavain@huawei.com<mailto:arashmid.akhavain@huawei.com>>; dmm@ietf.org<mailto: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
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>