Re: [DMM] DMM WG Adoption Poll (2) for "Mobile User Plane Evolution" - draft-zzhang-dmm-mup-evolution-06

Bill Gage <billgage.ietf@gmail.com> Tue, 24 October 2023 15:25 UTC

Return-Path: <billgage.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 CFA61C151553 for <dmm@ietfa.amsl.com>; Tue, 24 Oct 2023 08:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UoYuzrS5PpBe for <dmm@ietfa.amsl.com>; Tue, 24 Oct 2023 08:24:58 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CCEDC151082 for <dmm@ietf.org>; Tue, 24 Oct 2023 08:24:58 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id 6a1803df08f44-66d36b2a247so28570866d6.1 for <dmm@ietf.org>; Tue, 24 Oct 2023 08:24:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698161097; x=1698765897; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=QPkSPS/EkQmQBC4nOe++tgcQQxP+yht758Fp2wQPKzA=; b=JkdKAJe4fsnHkcEkvJ0xms13ozTW2YOeZuz86ijbu2EBFMnvvJF7zhLjcuCiP1OfWJ N+tATBe3udRXLwpNt0O59//Cz01RSJ6p8wJAPxHFkB66xB8jBE8kZv5P+lNxwv4I9xFe vQY/16j/UjaM2jhnKvg8tY38LAxlu8Pqgrh9xV0FIrvf0GXeta4FFGZJdVeMZb3tzOAP 537/zdUR3IgBJf8zb4SD46rvu2GGmMorjF4Y1k+upKAF6VWT+stoSGKCKfktdFZ+j7fb dW8phQfOhOP88nSm7e4b6VA5jwIaB2POH+Q689yf77NRoOpfbz0mQU/ONBBl7SEERFiR yJRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698161097; x=1698765897; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=QPkSPS/EkQmQBC4nOe++tgcQQxP+yht758Fp2wQPKzA=; b=vFff5bu7U0eiIKt7146opGqHQUifZa8+F5hRNvuuusMbT84hI2GTQDKjV7nk3ts2aN lymAzcl6j8dRs49qs0KKMSt28G1C/GNdXuZVm5EKRz25bxcngKOFC+BSOfk58kfTpSuc RY7V81j4uvfHvK6BHb8Gix9Wywdq+LsR/HXKDNkMfrI3eenB376puk38wX5rStQgDhyM 7wsub3Tfd/9RgV/Gd/+otz4vcz21F9BNJZ81oYvuwEPBx+VkKkXu7DHNMiyrxbsEYxmi hz3IK28n4kcqxlQ++urNJhzyTI2ztKsvXgJYv7yiiS3UHzMqvKWBeQT4DlRj58+zyHV6 3WTA==
X-Gm-Message-State: AOJu0Yw0BrpSEyyKMTBE3DbCcgK9r5bLf9RAcc8g2YDXEAVHGPVyxgeZ nxlKbiaM1jQMOrVZaGjGr20IrVa6ffg=
X-Google-Smtp-Source: AGHT+IHpjDEKHU2kfjz3Lee6+NI6EUyGmJzpUiLxRCfhktWQXfgM43NQY14ugyLYV1+PXR8viRgWLQ==
X-Received: by 2002:ad4:5f4f:0:b0:66d:5020:ef67 with SMTP id p15-20020ad45f4f000000b0066d5020ef67mr14861115qvg.36.1698161096669; Tue, 24 Oct 2023 08:24:56 -0700 (PDT)
Received: from [192.168.2.57] ([50.101.70.178]) by smtp.gmail.com with ESMTPSA id dk9-20020a056214092900b0065b5306565esm3679522qvb.112.2023.10.24.08.24.56 for <dmm@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 Oct 2023 08:24:56 -0700 (PDT)
Message-ID: <eb5f83d4-3674-4360-8a9f-6e3a09b8d3b1@gmail.com>
Date: Tue, 24 Oct 2023 11:24:53 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: dmm@ietf.org
References: <CAFwJXX5brW8MumgvVtwL5d6AVSZYEa97C8nJAyzpoOe=4f=pNg@mail.gmail.com>
Content-Language: en-GB
From: Bill Gage <billgage.ietf@gmail.com>
In-Reply-To: <CAFwJXX5brW8MumgvVtwL5d6AVSZYEa97C8nJAyzpoOe=4f=pNg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/rMsNAvHd0E6LVqYY7nN2NqrkY3k>
Subject: Re: [DMM] DMM WG Adoption Poll (2) for "Mobile User Plane Evolution" - draft-zzhang-dmm-mup-evolution-06
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.39
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, 24 Oct 2023 15:25:03 -0000

As stated in the abstract, this document does not change the 3GPP 
architecture nor does it propose changes in signalling protocols defined 
by 3GPP. The authors explicitly state that this document describes an 
*implementation* based on existing 3GPP specifications.

The stated goal is to bring this work to 3GPP for further discussions, 
but 3GPP does not deal with implementation-specific matters. If there 
are no new interfaces and no new protocols, then there is nothing for 
3GPP to consider.

For 5G, that ship has already sailed - operators and vendors are already 
deploying solutions so it is unlikely that this document will have any 
effect on 5G networks.

For 6G, it is premature to assume that the 5G functional models and 
protocol stacks will be carried forward into 6G. Nothing in this 
document appears to address issues that other research is attempting to 
resolve.

Personally, I have no objection to this document being "adopted" as a WG 
draft (https://datatracker.ietf.org/doc/draft-wkumari-not-a-draft/), but 
I would have serious objections to further progression towards an RFC. 
If the goal of this document is simply to publicise an implementation, 
there are other venues where it may get more attention (e.g. arXiv, IEEE 
Access).

Cheers ...

/bill
On 2023-10-19 5:41 a.m., Satoru Matsushima wrote:
> Dear DMMers,
> 
> This email starts a two-weeks DMM WG adoption poll (2) for ""Mobile User 
> Plane Evolution" - draft-zzhang-dmm-mup-evolution-06.
> 
> https://datatracker.ietf.org/doc/draft-zzhang-dmm-mup-evolution/ 
> <https://datatracker.ietf.org/doc/draft-zzhang-dmm-mup-evolution/>
> 
> Please review the draft and post any comments on this mail thread prior 
> to Friday, November 3rd, 2023.
> 
> Regards,
> Sri, Satoru
>