[DMM] Adoption call for I.D.: draft-zzhang-dmm-mup-evolution-06 (Mobile User Plane Evolution)

Tianji Jiang <tianjijiang@chinamobile.com> Mon, 14 August 2023 22:16 UTC

Return-Path: <tianjijiang@chinamobile.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 6A207C159495 for <dmm@ietfa.amsl.com>; Mon, 14 Aug 2023 15:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level:
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 oeuZbuM1hrsT for <dmm@ietfa.amsl.com>; Mon, 14 Aug 2023 15:16:05 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 43FC1C153CBB for <dmm@ietf.org>; Mon, 14 Aug 2023 15:16:02 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.93]) by rmmx-syy-dmz-app10-12010 (RichMail) with SMTP id 2eea64daa7a160b-0cc9c; Tue, 15 Aug 2023 06:16:01 +0800 (CST)
X-RM-TRANSID: 2eea64daa7a160b-0cc9c
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from [192.168.86.25] (unknown[99.0.86.16]) by rmsmtp-syy-appsvrnew07-12032 (RichMail) with SMTP id 2f0064daa79c53b-5b676; Tue, 15 Aug 2023 06:16:00 +0800 (CST)
X-RM-TRANSID: 2f0064daa79c53b-5b676
User-Agent: Microsoft-MacOutlook/10.10.1b.201012
Date: Mon, 14 Aug 2023 15:15:51 -0700
From: Tianji Jiang <tianjijiang@chinamobile.com>
To: dmm@ietf.org
Message-ID: <3AD77251-2643-4A29-9757-34EF8F5833D9@chinamobile.com>
Thread-Topic: Adoption call for I.D.: draft-zzhang-dmm-mup-evolution-06 (Mobile User Plane Evolution)
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3774870960_695392325"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/LcTuVqbK7Q-si2X3CXDii0iVLi0>
Subject: [DMM] Adoption call for I.D.: draft-zzhang-dmm-mup-evolution-06 (Mobile User Plane Evolution)
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: Mon, 14 Aug 2023 22:16:10 -0000

Dear DMM Team:

 

During the IETF-117, we have presented and discussed our IETF draft: ‘Mobile User Plane Evolution’ (draft-zzhang-dmm-mup-evolution: https://datatracker.ietf.org/doc/draft-zzhang-dmm-mup-evolution/ ). In the presentation, we explained the fundamental ideas of the I.D., along with our objectives. As we have stated, this was the 6th iteration of the I.D. Including this time (of IETF-117), different versions of the drafts have been presented & discussed thru the IETF-114, -115, -116 & -117. 

 

At the moment, we believe we have covered sufficiently various aspects of the MUP-evolution, i.e., the potential integration of gNB & UPF with targeting at B5G & 6G. These are comprised of both IP-domain requirements & wireless technologies. Further, as of now, 
The 3GPP 4G LIPA work, i.e., the Local IP Access, bodes well for our (B5G, 6G) ‘ANUP-like’ proposal. 
The 3GPP Rel-19 planning (5G) is on-going and some potential work (of the I.D.) could be possibly brought it to 3GPP for further study (Rel-19); and 
The 3GPP Rel-20 (6G roadmap) targets toward the beginning of Y-2025, which is a perfect timing for exploration and adoption of the ANUP-like work.
 

Given all the work that have been done so far, we have, during the IETF-117 DMM session, initiated a possible adoption-call of the I.D., in the ‘informational’ track. We have emphasized our I.D. just serves as input to 3GPP and we don’t intend to do 3GPP work in the IETF community. For a procedural question from an on-site attendee of the DMM session, the 3GPP-to-IETF liaison manager has shared his opinion and said there is no problem to bring the ‘normal document’ to 3GPP for discussion/reference. 

 

At the end of the session, the DMM chair suggested we bring this draft to the email alias. So, we are here to officially initiate the adoption-call of our I.D. 

Team, please share your opinions, comments, questions, etc. Thank you.

 

BR,

 

-Tianji