IETF Logo Mail Archive

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

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 06 January 2021 22:40 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 3FBD13A133F for <dmm@ietfa.amsl.com>; Wed, 6 Jan 2021 14:40:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level:
X-Spam-Status: No, score=-2.362 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, 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 xz76UbidYckM for <dmm@ietfa.amsl.com>; Wed, 6 Jan 2021 14:40:40 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 22BCA3A12E4 for <dmm@ietf.org>; Wed, 6 Jan 2021 14:40:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4DB4880MSBz6GVCr; Wed, 6 Jan 2021 14:40:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1609972840; bh=xG6EJVBJTykHVWSZXkFqbBz4rmLCFWM4lrlXx/91VjE=; h=Subject:To:References:From:Date:In-Reply-To:From; b=XKul6Ja0DdYBvMXLBzmw4VvcLn95q6SOtAdrMbimkn7qQKAgVwPC0YYA7cg7WNHwI +jc+pIXyhXwqN+VKr3BCfcUsTUsATlXFRnfrsScT0JPju023PGh/0yKKqC45JXQDAz Zx9C7dcDDJ/hHdK0khiidayIZ6Wd38ZJpKTZ9PvU=
X-Quarantine-ID: <V5TcXHy_Zz1m>
X-Virus-Scanned: Debian amavisd-new at a2.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 maila2.tigertech.net (Postfix) with ESMTPSA id 4DB4873VCxz6GFNq; Wed, 6 Jan 2021 14:40:39 -0800 (PST)
To: Kaippallimalil John <john.kaippallimalil@futurewei.com>, "dmm@ietf.org" <dmm@ietf.org>
References: <SN6PR13MB2334AD398B1B438613DE845085D10@SN6PR13MB2334.namprd13.prod.outlook.com> <96ffc11c-a823-19ca-3039-7881f60dd9c6@joelhalpern.com> <BYAPR13MB4197FB85159A5B393B02CBE8D9D10@BYAPR13MB4197.namprd13.prod.outlook.com> <198e4e59-a9e8-6f46-e4f0-6558ae1f909e@joelhalpern.com> <HE1PR07MB3386BF1545AB37BE66E909C99BD10@HE1PR07MB3386.eurprd07.prod.outlook.com> <CAF18ct7zJJ3MWqth_U+-UvxLzoe0R_vNQQbNKWdF+SRuOH1cZA@mail.gmail.com> <fa56d084-6dbc-03d8-2da3-5bc53e4e9bc6@joelhalpern.com> <SA0PR13MB40808C373097163891415E24E8D00@SA0PR13MB4080.namprd13.prod.outlook.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <159c549a-7e17-f741-0307-dee73dbeeb9e@joelhalpern.com>
Date: Wed, 06 Jan 2021 17:40:38 -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: <SA0PR13MB40808C373097163891415E24E8D00@SA0PR13MB4080.namprd13.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/5SzzkhA6xd5Z9784G5hDNQpZ-ww>
Subject: Re: [DMM] Call for adoption of draft-clt-dmm-tn-aware-mobility-08 as a WG document - Objections
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: Wed, 06 Jan 2021 22:40:41 -0000

In line,
Joel

On 1/6/2021 5:29 PM, Kaippallimalil John wrote:
> Joel,
> This draft is not attempting to lay out a new architecture. The figure and architecture section are there to provide context for the reader.
> 
> The draft is also not asserting that these are the only ways to solve the issue.
> The last portion of the draft only refers to applicability since several IETF technology (and even non IETF data plane like L2) may be used E2E in the transport underlay corresponding to a 3GPP overlay (F1/W1, N3, N9).
> The draft is agnostic to any specific underlay. It is concerned with how the slice type/QoS properties between 3GPP provider and subscriber (UE) is realized as the data plane GTP packets (overlay) traverse one or more transport underlay segments on path.

At the veyr least, the draft needs significant rewording so taht it 
clealry explains what you are saying here.  As currently worded, it does 
not lead the reader to that understanding.  And as such, calls into 
doubt what the supporters of adoption believe they are adopting.

> 
> The dmm working group seems to be a natural choice as folks there have background and expertise in both IETF and 3GPP technologies.

A WG looking like "the natural place" for something does not mean that 
said working group actually has the given work in its charter. For 
example, there were quite a number of drafts which were presented in the 
SFC WG as the natural place for initial discussion, but which did not 
fit within the SFC charter and therefore were not adopted by SFC as work 
items.

> 
> Best Regards,
> John

v2.23.0 | Report a Bug | By Email