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

Uma Chunduri <umac.ietf@gmail.com> Tue, 02 February 2021 00:08 UTC

Return-Path: <umac.ietf@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 BE6633A15DE for <dmm@ietfa.amsl.com>; Mon, 1 Feb 2021 16:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 GYBpvAt_NFfH for <dmm@ietfa.amsl.com>; Mon, 1 Feb 2021 16:08:02 -0800 (PST)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (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 033903A15D9 for <dmm@ietf.org>; Mon, 1 Feb 2021 16:08:01 -0800 (PST)
Received: by mail-yb1-xb2c.google.com with SMTP id w204so15878142ybg.2 for <dmm@ietf.org>; Mon, 01 Feb 2021 16:08:01 -0800 (PST)
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; bh=jrGaRLMsII+KoB1hpqPatrgAIZQd2g6hzhusnF3d7VE=; b=XRwZh3ygzrV2Ugc1Jw4q7AG0JUmvTNExxyf9+esTgHHYszWsGdOzXN11QSj5wWy4do 1xmoSmsv8y+W1gSwdct/vG03/lGQrz73UUICvNW4SEx6ukeVoBO78l7FwNiIdy475nAD 4Vqwv6fNnPxJB6iypmsr7nBsJ66jBgNrAorJyfKnTxczOlsIANcTtSSmto9cgIWEqkRq DgShwjBUUsNxCA4c3kI4WxGoVGl3YMTa5v0wgy4rDNEYlPMglnyM0sW3qDrpY/9Q4jBY orHeuiD2oFVmglp1feFL8bzySiIFD+i6VBpObo1pmwBV4sVG2rlWg5Sv7ODQnecsv2fV jOMg==
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; bh=jrGaRLMsII+KoB1hpqPatrgAIZQd2g6hzhusnF3d7VE=; b=H7RGVhPJDDqYXu9w+pQNrOGa9GQHU65BmEJqeycAcZMN5sHTohx71Q+xo7m6cDKgTn 5DPGf/txe2gutQSKImCUQIp7uguMz25sD91/cPq0ZpKV87Q8J7OHQpCsvxy2nIJ42kpG dsdlbijgMb9rcFF3xTxhxp/Sqy9CTh/Nt/gFzX9eJW0g8d7ZNnvmmkcte/UASLz10zWH rJlOXlJXluB6YmiuMAmjLyJ9LDCHQIZtkQnk2XaDyMa0qJLqPBgcYifetXyGx6ERof6Y 61xp08cZLnKxnRIsx3WdPwnts9aVrCtDmkZEHBwaaLsg59+AGRrLSAZVYVjiwQr2jtlr HxmQ==
X-Gm-Message-State: AOAM532pAP+EiaqVGaKyQc2s8TdszvA1iqwWfs+m+La4TOXC/pYk1Avn WrSSw+eDodxGm/4lP1ZEfhqS4pTTaV4akaXLg7HLILjF
X-Google-Smtp-Source: ABdhPJyeh8ogkhqdN7u68uI+OjxHLgOaIHpv/fMxeFQJo/Z8GJ/qKMvZPRUXj1OO9kLjH/qSoLKqrLiN75SBmxE/LDs=
X-Received: by 2002:a05:6902:1025:: with SMTP id x5mr27862203ybt.21.1612224481026; Mon, 01 Feb 2021 16:08:01 -0800 (PST)
MIME-Version: 1.0
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> <159c549a-7e17-f741-0307-dee73dbeeb9e@joelhalpern.com>
In-Reply-To: <159c549a-7e17-f741-0307-dee73dbeeb9e@joelhalpern.com>
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Mon, 01 Feb 2021 16:07:50 -0800
Message-ID: <CAF18ct5xEnS-FxiK45fhGL5=5TUQkmOPjB7nEoPcdpjYxa4Oyg@mail.gmail.com>
To: dmm <dmm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007d648405ba4f43dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/ch7p2mvlKUyRh6Qj3z-SnSGUc6o>
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: Tue, 02 Feb 2021 00:08:04 -0000

Dear All,

As suggested by WG chairs, we would like to spin one more version to
address the comments during the adoption call and in that process will
reach out to Joel and Hannu (separately)  for specific inputs where
terminology alignment has to happen w.r.t TEAS slicing definition draft.

Will keep you updated on the WG soon.
--
Uma C.

On Wed, Jan 6, 2021 at 2:40 PM Joel M. Halpern <jmh@joelhalpern.com> wrote:

> 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
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>