Re: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 as a WG document

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 21 January 2021 01:22 UTC

Return-Path: <jie.dong@huawei.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 339713A1672 for <dmm@ietfa.amsl.com>; Wed, 20 Jan 2021 17:22:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 3QniqfVNLhaD for <dmm@ietfa.amsl.com>; Wed, 20 Jan 2021 17:22:02 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A100B3A1670 for <dmm@ietf.org>; Wed, 20 Jan 2021 17:22:02 -0800 (PST)
Received: from fraeml712-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DLl096xZCz67dpG for <dmm@ietf.org>; Thu, 21 Jan 2021 09:18:49 +0800 (CST)
Received: from dggeme751-chm.china.huawei.com (10.3.19.97) by fraeml712-chm.china.huawei.com (10.206.15.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Thu, 21 Jan 2021 02:21:59 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme751-chm.china.huawei.com (10.3.19.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Thu, 21 Jan 2021 09:21:57 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2106.002; Thu, 21 Jan 2021 09:21:57 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org>, dmm <dmm@ietf.org>
Thread-Topic: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 as a WG document
Thread-Index: AQHW6qb/P3C+dqhRYUmyQ/xxcxIrVKowXNcAgADwzLA=
Date: Thu, 21 Jan 2021 01:21:57 +0000
Message-ID: <57f47489646645918918dd93fbabf5f8@huawei.com>
References: <0DEC8F67-ACCF-4E56-99D6-BB93CEFB09E5@cisco.com> <8FB49AD0-7CA7-4509-8174-12CF426AAB49@cisco.com>
In-Reply-To: <8FB49AD0-7CA7-4509-8174-12CF426AAB49@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.143]
Content-Type: multipart/alternative; boundary="_000_57f47489646645918918dd93fbabf5f8huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/w8r-Vj_clMZf9mNYSr0ExjgNah8>
Subject: Re: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 as a 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, 21 Jan 2021 01:22:05 -0000

Dear Chairs,

Sorry for the late reply.

After reading this document and the discussion on the list, I also think some alignment with the TEAS working group on the definition, terminology and framework of network slice would be helpful.

As for the technical aspects, to my understanding this document proposes a mechanism to provide the transport path information to the mobile network endpoints, which IMO may also be used in networks without network slicing. If this understanding is correct, I’d suggest to clarify the relationship between the proposed mechanism and the network slicing use case.

Best regards,
Jie

From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli (sgundave)
Sent: Thursday, January 21, 2021 2:43 AM
To: dmm <dmm@ietf.org>
Subject: Re: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 as a WG document

Thank you all. This adoption call is now closed. We will review the feedback.

-          Chairs


From: dmm <dmm-bounces@ietf.org<mailto:dmm-bounces@ietf.org>> on behalf of "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org<mailto:sgundave=40cisco.com@dmarc.ietf.org>>
Date: Thursday, January 14, 2021 at 10:56 AM
To: dmm <dmm@ietf.org<mailto:dmm@ietf.org>>
Subject: Re: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 as a WG document

Gentle reminder.

This adoption call with expire on 18th Jan. Please provide your feedback.

Just to structure the discussion, we want to understand a.) if the WG agrees with the problem statement and is relevant for mobility working group, b.) is the proposed solution/approach is a reasonable approach, and if it is a good starting point

On the comments on where this work needs to happen etc , feedback is welcome but I would not worry too much about that now. Let’s agree upon the problem statement first and focus more on the technical aspects. If this is a valid problem, we can always decide to do that work here, or in some other group and that’s based on AD/Chair inputs and  on the review expertise that is needed for this work completion.

-Chairs





From: dmm <dmm-bounces@ietf.org<mailto:dmm-bounces@ietf.org>> on behalf of "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org<mailto:sgundave=40cisco.com@dmarc.ietf.org>>
Date: Wednesday, December 30, 2020 at 10:45 AM
To: dmm <dmm@ietf.org<mailto:dmm@ietf.org>>
Subject: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 as a WG document

Folks:

The authors of the document, Transport Network aware Mobility for 5G, have presented the proposal and the need for standardization in multiple IETF WG meetings. There have been good amount of discussions in the mailers and there is some level of interest for the work from the community. We are therefore considering the adoption of this document as a DMM WG document, to be moved on Informational Standards track.

Transport Network aware Mobility for 5G
https://tools.ietf.org/html/draft-clt-dmm-tn-aware-mobility-08


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.

The adoption call will end on 18th of January, 2021.

Regards
DMM WG Chairs