[DMM] FW: New Version Notification for draft-yan-dmm-man-11.txt
Tianji Jiang <tianjijiang@chinamobile.com> Thu, 13 July 2023 00:46 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 9C924C151988 for <dmm@ietfa.amsl.com>; Wed, 12 Jul 2023 17:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 948UpwTucULN for <dmm@ietfa.amsl.com>; Wed, 12 Jul 2023 17:46:18 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 6E9F5C151999 for <dmm@ietf.org>; Wed, 12 Jul 2023 17:46:15 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.11]) by rmmx-syy-dmz-app10-12010 (RichMail) with SMTP id 2eea64af495161c-b4b67; Thu, 13 Jul 2023 08:46:10 +0800 (CST)
X-RM-TRANSID: 2eea64af495161c-b4b67
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from [192.168.86.21] (unknown[99.0.86.16]) by rmsmtp-syy-appsvr06-12006 (RichMail) with SMTP id 2ee664af494a5e7-5c0d6; Thu, 13 Jul 2023 08:46:10 +0800 (CST)
X-RM-TRANSID: 2ee664af494a5e7-5c0d6
User-Agent: Microsoft-MacOutlook/10.10.1b.201012
Date: Wed, 12 Jul 2023 17:45:58 -0700
From: Tianji Jiang <tianjijiang@chinamobile.com>
To: dmm@ietf.org
Message-ID: <3DCBF056-2315-4B36-96E6-F8BFBEA3353E@chinamobile.com>
Thread-Topic: New Version Notification for draft-yan-dmm-man-11.txt
References: <8843ca9.37f.1894c9b7c40.Coremail.yzw_iplab@163.com>
In-Reply-To: <8843ca9.37f.1894c9b7c40.Coremail.yzw_iplab@163.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3772028768_1135025590"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/4loUmvgO4xGLsK2ycne2S15N1Qo>
Subject: [DMM] FW: New Version Notification for draft-yan-dmm-man-11.txt
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: Thu, 13 Jul 2023 00:46:19 -0000
Hi, DMM experts: Good afternoon. We, the authors of the draft, have submitted a newer version of the draft (ver#11) ‘Mobility Capability Negotiation’ to the IETF-117, and are currently planning to present in-person in the DMM session. Thank you for all the valuable comments & suggestions from previous discussions (via IETF DMM sessions, email, f2f talks, etc.). This time, we have made significant editing of the document and then restructured the draft accordingly (as the 11th version now). The latest version revolves around the management planes of both the wireless and mobile-IP domains. We started by talking about the common mobility capabilities including the supported and provisioned resources along with associated protocols for certain mobility management scenarios. Then, we generalized two protocol categories for mobility capability negotiation & management, i.e., the host-initiated category that involves the direct & active engagement of mobile end devices vs. the network-based category over which mobile endpoints play almost no role in the process, for both domains. After that, we applied the categorization to analyze the mobility capability negotiation for both the mobile IPv6 and the 3GPP 5G system. We also further dived into the 5G roaming cases, the Home-Routed (HR) and the Local BreakOut (LBO) roaming, which indeed reflect the feasibility of our protocol dichotomy. So, DMM experts, we appreciate if you can spare some time in the next two weeks, read it over, and then share your comments. As of now, we intend to ask for a potential WG adoption in the coming IETF-117 DMM session. Thank you for your time! BR, -Tianji ---- Forwarded Message ---- Frominternet-drafts<internet-drafts@ietf.org> Date07/04/2023 14:08 ToJianfeng Guan<jfguan@bupt.edu.cn>, Jong-Hyouk Lee<jonghyouk@sejong.ac.kr>, Sejong University<jonghyouk@sejong.ac.kr>, Tao Huang<htao@bupt.edu.cn>, Tianji Jiang<tianjijiang@chinamobile.com>, Zhiwei Yan<yan@cnnic.cn> SubjectNew Version Notification for draft-yan-dmm-man-11.txt A new version of I-D, draft-yan-dmm-man-11.txt has been successfully submitted by Zhiwei Yan and posted to the IETF repository. Name: draft-yan-dmm-man Revision: 11 Title: Mobility Capability Negotiation Document date: 2023-07-04 Group: Individual Submission Pages: 17 URL: https://www.ietf.org/archive/id/draft-yan-dmm-man-11.txt Status: https://datatracker.ietf.org/doc/draft-yan-dmm-man/ Htmlized: https://datatracker.ietf.org/doc/html/draft-yan-dmm-man Diff: https://author-tools.ietf.org/iddiff?url2=draft-yan-dmm-man-11 Abstract: Mobile peers exchange signals with networks, for both IP and wireless domains, to negotiate capabilities for mobile registration, connection management, session establishment, service provisioning, etc. Generally, mobility capabilities include the supported and provisioned resources along with associated protocols for certain mobility management scenarios. While devices in the mobile IP domain would mostly focus on the IP-related negotiation, devices in the wireless domain, e.g., the 5G system (5GS), embrace both mobile IP- related resources as well as wireless-specific capabilities. Regarding both the mobile-IP and wireless domains, we have generalized two protocol categories for mobility capability negotiation & management, i.e., the host-initiated category that involves the direct & active engagement of mobile end devices vs. the network-based category over which mobile endpoints play almost no role in the process. The classification and then the application of the two categories help us analyze the mobility capability negotiation for both the mobile IPv6 and the 3GPP 5G system. The comparison of the capability negotiation under both the Home-Routed (HR) and the Local BreakOut (LBO) roaming cases in 5GS further reflects the feasibility of the protocol dichotomy. The IETF Secretariat
- [DMM] FW: New Version Notification for draft-yan-… Tianji Jiang