Re: New Version Notification for draft-huang-rtgwg-sid-for-networking-00.txt

huang.guangping@zte.com.cn Mon, 23 October 2023 13:36 UTC

Return-Path: <huang.guangping@zte.com.cn>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5D8C151549 for <rtgwg@ietfa.amsl.com>; Mon, 23 Oct 2023 06:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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, UNPARSEABLE_RELAY=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 a_ibngED3wbb for <rtgwg@ietfa.amsl.com>; Mon, 23 Oct 2023 06:36:54 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AB8EC16F417 for <rtgwg@ietf.org>; Mon, 23 Oct 2023 06:36:30 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4SDbnK4rvMz4xPFs; Mon, 23 Oct 2023 21:36:21 +0800 (CST)
Received: from szxlzmapp07.zte.com.cn ([10.5.230.251]) by mse-fl1.zte.com.cn with SMTP id 39NDaGCb066953; Mon, 23 Oct 2023 21:36:16 +0800 (+08) (envelope-from huang.guangping@zte.com.cn)
Received: from mapi (szxlzmapp05[null]) by mapi (Zmail) with MAPI id mid17; Mon, 23 Oct 2023 21:36:20 +0800 (CST)
Date: Mon, 23 Oct 2023 21:36:20 +0800
X-Zmail-TransId: 2b07653676d4ffffffffe05-01030
X-Mailer: Zmail v1.0
Message-ID: <202310232136207693400@zte.com.cn>
In-Reply-To: <169806715191.60097.15209503928354920462@ietfa.amsl.com>
References: 169806715191.60097.15209503928354920462@ietfa.amsl.com
Mime-Version: 1.0
From: huang.guangping@zte.com.cn
To: rtgwg@ietf.org
Cc: huang.cheng13@zte.com.cn, dyang@bjtu.edu.cn, yuan.dongyu@zte.com.cn, fu.huaka@zte.com.cn, chengg55@chinatelecom.cn, liangjie6@chinatelecom.cn, zhangy1156@chinaunicom.cn, guo.yong3@zte.com.cn
Subject: Re: New Version Notification for draft-huang-rtgwg-sid-for-networking-00.txt
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 39NDaGCb066953
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 653676D5.000/4SDbnK4rvMz4xPFs
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/ciSM_xODql2aqUpmHQXNhWX64D4>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Oct 2023 13:36:59 -0000

Hi everyone,
The co-authors and I have submitted a draft of service ID for addressing and networking to RTGWG and the chief motivation is to demonstrate and clarify why employing a standalone service ID matters significantly for multiple use cases with good benefits. The draft in the first place focuses on the standalone service ID in routing network though corresponding solution considerations have also been demonstrated as instantiation of how service ID could be utilized from perspective of end to end workflow. However, we would like to in the first stage address why, what and how in terms of  service ID rather than a specific framework solution.
Any comments, suggestions and contributions would be welcome and appreciated.
The draft link:
https://datatracker.ietf.org/doc/draft-huang-rtgwg-sid-for-networking/ 

Best regards,
Daniel Huang










黄光平 huangguangping

标准团队/有线规划部 Wireline architecture team./Wireline Product R&D Institute





南京市雨花区软件大道50号中兴通讯2号楼 
R&D Building, ZTE
Corporation Software Road No.50, 
Yuhua District, Nanjing, P..R.China, 210012 
M: +86 13770311052 
E: huang.guangping@zte.com.cn 
www.zte.com.cn


Original


From: internet-drafts@ietf.org <internet-drafts@ietf.org>
To: 黄程00315422;黄光平10039714;Dong Yang <dyang@bjtu.edu.cn>;袁冬宇10335620;Fu Huakai;Ge Chen <chengg55@chinatelecom.cn>;Jie Liang <liangjie6@chinatelecom.cn>;Yan Zhang <zhangy1156@chinaunicom.cn>;郭勇10051305;gechen <chengg55@chinatelecom.cn>;
Date: 2023年10月23日 21:19
Subject: New Version Notification for draft-huang-rtgwg-sid-for-networking-00.txt

A new version of Internet-Draft draft-huang-rtgwg-sid-for-networking-00.txt
has been successfully submitted by Daniel Huang and posted to the
IETF repository.
 
Name:     draft-huang-rtgwg-sid-for-networking
Revision: 00
Title:    Service ID for Addressing and Networking
Date:     2023-10-23
Group:    Individual Submission
Pages:    26
URL:      https://www.ietf.org/archive/id/draft-huang-rtgwg-sid-for-networking-00.txt
Status:   https://datatracker.ietf.org/doc/draft-huang-rtgwg-sid-for-networking/
HTML:     https://www.ietf.org/archive/id/draft-huang-rtgwg-sid-for-networking-00.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-huang-rtgwg-sid-for-networking
 
 
Abstract:
 
   More and more emerging applications have raised the demand for
   establishing networking connections?anywhere and anytime, alongside
   the availability of highly distributive?any-cloud services.  Such a
   demand motivates the need to efficiently interconnect heterogeneous
   entities, e.g., different domains of network and cloud owned by
   different providers, with the goal of reducing cost, e.g., overheads
   and end-to-end latency, while ensuring the overall performance
   satisfies the requirements of the applications.  Considering that
   different network domains and cloud providers may adopt different
   types of technologies, the key of interconnection and efficient
   coordination is to employ a unified interface that can be understood
   by heterogeneous parties which could derive the consistent
   requirements of the same service and treat the service traffic
   appropriately by their proprietary policies and technologies.
 
   Therefore, service ID is one promising candidate for the unified
   interface since it could be designed to be lightweight, secure, and
   enables fast and efficient packet treatment.  Leveraging service ID,
   addressing and networking among heterogeneous network domains and
   cloud providers can be accomplished by establishing the mapping
   between the unified service ID and the specific technologies used by
   a network domain or a cloud provider.
 
   This document provides typical use cases of unified service ID for
   addressing and routing (SIAN), validating that interconnecting
   different network domains or cloud providers can be achieved at lower
   cost without sacrificing the performance of application compared with
   existing methods of which problems as well as gaps have also been
   illustrated.  The requirements for SIAN are also derived for each of
   the scenarios.  Finally, a framework solution is demonstrated.
 
 
 
The IETF Secretariat