%% You should probably cite draft-huang-rtgwg-us-standalone-sid instead of this I-D.
@techreport{huang-rtgwg-sid-for-networking-00,
    number =    {draft-huang-rtgwg-sid-for-networking-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-huang-rtgwg-sid-for-networking/00/},
    author =    {Daniel Huang and 陈戈 and Jie Liang and Yan Zhang and Dong Yang and Dongyu Yuan and Fu Huakai and Cheng Huang and Yong Guo},
    title =     {{Service ID for Addressing and Networking}},
    pagetotal = 26,
    year =      2023,
    month =     oct,
    day =       23,
    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.},
}