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

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 05 January 2021 00:22 UTC

Return-Path: <jmh@joelhalpern.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 40D553A0BDF for <dmm@ietfa.amsl.com>; Mon, 4 Jan 2021 16:22:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level:
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 1yfa0JQzOy0B for <dmm@ietfa.amsl.com>; Mon, 4 Jan 2021 16:22:55 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFDC03A0B86 for <dmm@ietf.org>; Mon, 4 Jan 2021 16:22:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4D8tW34wdQz1pG0L for <dmm@ietf.org>; Mon, 4 Jan 2021 16:22:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1609806175; bh=nycpQjjqK4jcY4UcMIg67lCtbusz9BV+HSvmCFaBcbw=; h=Subject:To:References:From:Date:In-Reply-To:From; b=ZzX9zC2XED+XBO/aEfSmPyzfD2uEKYg8zvAMYJBAQy1+wHFwABw1bi547lzg94i+4 ymufPn0opGdnpRvdtOJdpfroqSedScSz9x/VhgZ3XCC4aGSMuW/0DKJCP8lENHS2Kg jrShKIRrV0hcasnRkdk8nuNui3sK1Hu99+mJ/BRE=
X-Quarantine-ID: <nuqPIjnVrrJe>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4D8tW31BRBz1nvxx for <dmm@ietf.org>; Mon, 4 Jan 2021 16:22:55 -0800 (PST)
To: "dmm@ietf.org" <dmm@ietf.org>
References: <SN6PR13MB2334AD398B1B438613DE845085D10@SN6PR13MB2334.namprd13.prod.outlook.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <96ffc11c-a823-19ca-3039-7881f60dd9c6@joelhalpern.com>
Date: Mon, 04 Jan 2021 19:22:54 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <SN6PR13MB2334AD398B1B438613DE845085D10@SN6PR13MB2334.namprd13.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/7orHQgDEx3OmZY9LJIXHP41z9PU>
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: Tue, 05 Jan 2021 00:22:57 -0000

Hmmm.

It seems to me that this document ought to align with the ongoing work 
in the TEAS working group that is attempting to define terminology and 
framework (and then any necessary protocol mechanisms) for IETF network 
slices.  That work is explicitly intended to support 3GPP end-to-end 
network slices.

First, the discussion there exlicitly conluded that the term "Transport" 
was confusing and misleading.  Which is why the work is now called IETF 
network slicing.

Second, it seems that we want one IETF framework for this, not two 
competing frameworks.  Why is DMM doing this separately.  It seems to 
fall squarely into CCAMP and TEAS.  I presume we want a solution that 
works for 3GPP and works for other use cases?

Yours,
Joel M. Halpern

On 1/4/2021 7:11 PM, Linda Dunbar wrote:
> Support WG adoption.
> 
> Linda Dunbar
> 
> -------------------
> From: *Sri Gundavelli (sgundave)* <sgundave=40cisco.com@dmarc.ietf.org 
> <mailto:40cisco.com@dmarc.ietf.org>>
> Date: Wed, Dec 30, 2020 at 10:45 AM
> Subject: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 
> as a WG document
> To: dmm <dmm@ietf.org <mailto:dmm@ietf.org>>
> 
> 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 
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-clt-dmm-tn-aware-mobility-08&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C6af4a1ce1b62454eb25d08d8b0350e40%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637453089238313897%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SsBq92wzWCggc5r7r96NPHV2cAan2tjtvoYF2LEBtqY%3D&reserved=0>
> 
> 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
> 
> _______________________________________________
> dmm mailing list
> dmm@ietf.org <mailto:dmm@ietf.org>
> https://www.ietf.org/mailman/listinfo/dmm 
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdmm&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C6af4a1ce1b62454eb25d08d8b0350e40%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637453089238323895%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3CAVTNOGuuKjj0rAJcv54OPPObzMj6YSnPf2tsfKYG4%3D&reserved=0>
> 
> 
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>