From: rtgwg <[email protected]> on behalf of [email protected] 
<[email protected]>
Sent: 23 October 2023 14:36

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.

<tp>

The RFC Editor currently lists seven possible expansions for 'sid' none of 
which is sufficiently well known to not need expanding when used.

You are adding number eight.

It might help readers, perhaps the IETF at large, if another abbreviation could 
be found.

Tom Petch



The draft link:

<https://datatracker.ietf.org/doc/draft-huang-rtgwg-sid-for-networking/>https://datatracker.ietf.org/doc/draft-huang-rtgwg-sid-for-networking/


Best regards,

Daniel Huang







黄光平 huangguangping


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


[cid:afc08a499f4d4614a09e37179ab78b10]  [cid:24242e5637af428891c4db731e7765ad]
南京市雨花区软件大道50号中兴通讯2号楼
R&D Building, ZTE Corporation Software Road No.50,
Yuhua District, Nanjing, P..R.China, 210012
M: +86 13770311052<tel:+86%2013770311052>
E: [email protected]
www.zte.com.cn<http://www.zte.com.cn/>
Original
From: [email protected] <[email protected]>
To: 黄程00315422;黄光平10039714;Dong Yang <[email protected]>;袁冬宇10335620;Fu 
Huakai;Ge Chen <[email protected]>;Jie Liang 
<[email protected]>;Yan Zhang 
<[email protected]>;郭勇10051305;gechen <[email protected]>;
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


_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to