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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Mon, 17 December 2018 17:52 UTC

Return-Path: <sgundave@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 D9D4D130F1B for <dmm@ietfa.amsl.com>; Mon, 17 Dec 2018 09:52:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.96
X-Spam-Level:
X-Spam-Status: No, score=-15.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 sOfKkDAak_ZG for <dmm@ietfa.amsl.com>; Mon, 17 Dec 2018 09:52:02 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7C11130EE9 for <dmm@ietf.org>; Mon, 17 Dec 2018 09:52:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7012; q=dns/txt; s=iport; t=1545069121; x=1546278721; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=fn98JK9WPAJowMdeef9TeLPwLrxp/TlsNJAZsa1+Rp8=; b=H9CCTEUnNjYmQETdzyNKU45jH6ju05R61zbSp+BYC3vfz8F376JljV80 m+ErejCriVe2MBSKeAnDlri2bpjEm/14AF5UY94T4fXIw9kLbnjVKIefV eUjU3wgwTRAxiJPVxFQ8ukOV3EHx6r0ikj7McyWkBuMTUcmNKYJIQcGhY w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJAAA74Rdc/5tdJa1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBWilmgQInCoNyiBmLd4INfIJJhVCOQ4F6CwEBGAuESQIXgn0iNAkNAQMBAQIBAQJtHAyFPAEBAQEDAQEbBhE6GwIBBgIRAwECAwImAgICHwYLFQgIAgQBEhSDD4FoAxUPjFKbU4EvhDECgQ2COA2CFwWBC4szF4FAP4ERgl01gldHAQEDgV4XgnGCNSICiSUslxkvCQKHC4cdgQqCJhiBXYUcgzGHKIk8hHaBEol5AhEUgScfOIFWcBU7gmyCJxcSbQEBh12FP0ExjVeBHwEB
X-IronPort-AV: E=Sophos;i="5.56,366,1539648000"; d="scan'208";a="214383920"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Dec 2018 17:52:00 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id wBHHpxW4030816 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 17 Dec 2018 17:51:59 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 17 Dec 2018 11:51:59 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1395.000; Mon, 17 Dec 2018 11:51:59 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document
Thread-Index: AQHUljE1gigxQX+ev06MrLeEear1RA==
Date: Mon, 17 Dec 2018 17:51:59 +0000
Message-ID: <D83D218E.2E14BF%sgundave@cisco.com>
References: <D8242158.2DFB2F%sgundave@cisco.com> <D82D483F.2E04E4%sgundave@cisco.com> <D8388995.2E0FF2%sgundave@cisco.com> <381BB175-A810-42B8-9EE8-8D62E7E86E83@gmail.com>
In-Reply-To: <381BB175-A810-42B8-9EE8-8D62E7E86E83@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.188.53]
Content-Type: text/plain; charset="utf-8"
Content-ID: <65450EFC332CC144BF62BDD00C104A79@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/vkmVPEnW5bu5O5yStOTdCyykbQE>
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: Mon, 17 Dec 2018 17:52:15 -0000

Hi Satoru-San,

Thank you for your comments. All the LS statements received from 3GPP with
regards to the work item on, User Plane Optimization study, will be taken
into consideration in this decision process.


Sri



On 12/17/18, 1:19 AM, "Satoru Matsushima" <satoru.matsushima@gmail.com>
wrote:

>Thank you Sri, and all,
>
>During that, let me make clear some questions and comments. First one:
>
>> So the purpose of this draft seems to explicitly be to do work for 3GPP
>>that they have explicitly said they DO NOT WANT.
>
>It’s wrong. In the LS of CP-173160 requested any information regarding
>user plane. So please re-read the following:
>
>> 2. Actions:
>> To IETF DMM:
>> ACTION:         CT4 respectfully asks IETF DMM to provide any
>>information that may be relevant to the above CT4 work by July 2018.
>> 
>
>And the LS of C4-185491 didn’t say they don’t want. It just said that the
>evaluation criteria for the user plane protocol study (FS_UPPS) in 5GC
>shall be defined by 3GPP CT4. It should be very natural and responsible.
>
>Second one is that:
>
>> Particularly the discussion around slicing is very speculative. And
>>conclusion thereof that “The expected evaluation points from this aspect
>>should be whether the candidate protocols can support to indicate a
>>network slice in the UP packets.” Firstly, IETF doesn’t have any work on
>>slicing, on the contrary. Secondly, the need for such indication in the
>>3GPP has been discussed in the ongoing 3GPP CT4 meeting this week with
>>fully opposing views for such network slice indication. (Network slicing
>>is supported in 3GPP Rel-15 already, and nothing new was defined in the
>>user plane in Rel-15. There was no need for that!)
>
>It looks not accurate view of the latest discussion in 3GPP CT4. CT4
>agreed not to introduce any NEW identifiers to indicate network slice for
>5GC and its transport. Existing identifiers can be expected for that
>purpose in user plane.
>
>
>Hope it helps our understanding correct.
>
>Best regards,
>--satoru
>
>
>
>
>> 2018/12/14 15:14、Sri Gundavelli (sgundave) <sgundave@cisco.com>のメール:
>> 
>> Folks – Sorry for the delay on this. Given the number of support votes
>>for the company I am affiliated with, I thought it would be best for my
>>co-chair Dapeng reviews this feedback, and in consultation with the AD,
>>makes the decision on this. We will close it soon.
>> 
>> Sri
>> 
>> 
>> 
>> From: Sri Gundavelli <sgundave@cisco.com>
>> Date: Wednesday, December 5, 2018 at 9:18 AM
>> To: "dmm@ietf.org" <dmm@ietf.org>
>> Subject: Re: [DMM] Call for adoption of
>>draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document
>> 
>> Thanks for all the feedback. The adoption call is now closed. We will
>>review the feedback and decide on the next steps.
>> 
>> Sri
>> 
>> 
>> 
>> From: dmm <dmm-bounces@ietf.org> on behalf of Sri Gundavelli
>><sgundave@cisco.com>
>> Date: Wednesday, November 28, 2018 at 10:42 AM
>> To: "dmm@ietf.org" <dmm@ietf.org>
>> Subject: Re: [DMM] Call for adoption of
>>draft-hmm-dmm-5g-uplane-analysis-02 as DMM WG document
>> 
>> Gentle reminder.  The below adoption call will close next week, the 4th
>>of December, 2018. Please provide your feedback.
>> 
>> 
>> Sri
>> 
>> 
>> 
>> From: dmm <dmm-bounces@ietf.org> on behalf of Sri Gundavelli
>><sgundave@cisco.com>
>> Date: Tuesday, November 13, 2018 at 4:34 PM
>> To: "dmm@ietf.org" <dmm@ietf.org>
>> Subject: [DMM] Call for adoption of draft-hmm-dmm-5g-uplane-analysis-02
>>as DMM WG document
>> 
>> Folks:
>> 
>> During IETF 102 and 103, the authors of the document,
>>draft-hmm-dmm-5g-uplane-analysis.txt have provided the overview of this
>>document. The chairs felt there is good amount of work that went into
>>the document and the analysis has value. The document quality is very
>>high. There was also generally good feedback and interest for the work
>>from the community. We are therefore considering adopting this document
>>as a DMM WG document, to be moved on Informational Standards track.
>> 
>> There were also few concerns/comments on the 1.) Relevance of this
>>document to 3GPP in the immediate time frame 2.) Archival Value of the
>>document 3.) Target Audience  - IETF or 3GPP.
>> On #3, there was also a view that the document should be restructured
>>to make it IETF focussed.  With this background, we would like to ask
>>the WG to provide some feedback on their interest for this work. Please
>>provide substantial comments as why this should be adopted, or why it
>>should not be adopted. If there is interest, and if there are no other
>>concerns from AD/IESG/Others, then we may take up this work at some
>>point. 
>> 
>> Draft Pointer: 
>>https://tools.ietf.org/html/draft-hmm-dmm-5g-uplane-analysis-02
>> 
>> 
>> The adoption call will end on 4th of December, 2019.
>> 
>> 
>> Regards
>> Dapping & Sri
>> _______________________________________________
>> dmm mailing list
>> dmm@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmm
>