Distributed Micro Services Communication(DMSC)
bofreq-wang-distributed-micro-services-communicationdmsc-03

Document Type Declined BOF request
Title Distributed Micro Services Communication(DMSC)
Last updated 2025-02-10
State Declined
Editor Aijun Wang
Responsible leadership
Send notices to (None)
bofreq-wang-distributed-micro-services-communicationdmsc-03

Name: Distributed Micro Services Communication(DMSC)

Description

The DMSC(Distributed Micro Services Communication) BOF aims to build one service oriented, distributed infrastructure that can accommodate the communications requirements among various micro-services, which are currently relying on the centralized controlled Service Mesh to accomplish the tasks. It will focus on tailoring the various HTTP methods, QUIC/TCP based micro services to the content semantic based framework, to facilitate the development of one distributed, service oriented network that can carry micro services, CDN and various live broadcast services.

Fill in the details below. Keep items in the order they appear here.

Required Details

  • Status: (not) WG Forming

  • Responsible AD: Zaheduzzaman Sarker

  • BOF proponents: Aijun Wang <wangaj3@chinatelecom.cn>, Enge Song <enge.seg@alibaba-inc.com>

  • Number of people expected to attend: 100
  • Length of session (1 or 2 hours): 2 hours
  • Conflicts (whole Areas and/or WGs)
  • Chair Conflicts: HTTPBIS/QUIC/CDNI/TCPM/TSVWG
  • Technology Overlap: HTTP/TCP/QUIC/CDN
  • Key Participant Conflict: Zaheduzzaman Sarker, Francesca Palombini, Mark Nottingham, Tommy Pauly, Lucas Pardue, Matt Joras

Information for IAB/IESG

Micro services are used widely within the current cloud based applications. To facilitate the communication of large amounts of these micro services, Cloud Service Providers build the Service Mesh infrastructure(for example: Istio, https://istio.io/)themselves to accomplish the task of authentication, authorization, load balancing, circuit breaker, service discovery and observability.

Such Service Mesh infrastructure has been widely used for a few years, but it encounters various challenges. The main challenge comes from its centralized control design philosophy and its tight integrated and co-located deployment with the micro services.

Then, in order to solve the challenges of the current Service Mesh infrastructure, the DMSC(Distributed Micro Services Communication) group will discuss how to build one distributed, shared infrastructure that can be utilized by various Cloud Service Providers, and also the Content Service Provider, to assist the communications of the wide deployed micro services.

Apart from this, recent research has shown that network devices undertaking some computing tasks can greatly improve the network and application performance in some scenarios, like for instance aggregating path-computing , key-value(K-V) cache, and in network securities etc. In the context of such heterogeneity of scenarios, it is desirable to have a generic and flexible framework, able to explicitly signaling the computing, service operation to be performed by network devices, which can be regarded as one kind of distributed services that are deployed within the network.

DMSC group will try to accomodate the distributed services around the network and within the network in one coherent architecture to accomplish the service discovery, service routing and service engineering functions to satify the emerged scenarios and requirements.

  • Any protocols or practices that already exist in this space:
    Istio(https://istio.io/) is one open source implementation of such infrastructure, but is in centralized control mode, has amounts of challenges in its current deployment and future development.

  • Which (if any) modifications to existing protocols or practices are required:
    Http/TCP/QUIC may be needed to adapt to the content semantic based layer

  • Which (if any) entirely new protocols or practices are required:
    One new transport protocol may be needed to design if the existing one can't be tailored to meet the micro services communication requirements.

  • Open source projects (if any) implementing this work:
    iStack: A General and Stateful Name-based Protocol Stack for Named Data Networking (https://www.usenix.org/conference/nsdi24/presentation/li-tianlong)

Agenda

=====================
Part 0: Chair's Slides (5 minutes)
======================
0) Chair's Slides

=========================================
Part I: Problem Statements and Applied Scenarios(45 minutes)
=========================================
1) Problem Statements of current Service Mesh infrastructure and Requirements of DMSC. Enge Song, Alibaba, 15 minutes.
https://datatracker.ietf.org/doc/draft-song-dmsc-promblem-and-requirements/

2) Signaling In-Network Computing operations (SINC) Yizhou Li, Huawei Technologies, 10 minutes
https://datatracker.ietf.org/doc/draft-lou-rtgwg-sinc/

3) Distributed AI model architecture for microservices communication and computing power scheduling, Hui Yang, BUPT, 10 minutes
https://datatracker.ietf.org/doc/html/draft-yang-dmsc-distributed-model

4) Dynamic Trust Security Architecture for Distributed Service Mesh Xuan Si, China Telecom, 10 minutes
https://datatracker.ietf.org/doc/html/draft-si-service-mesh-dta

=========================================
Part II: Proposed Architecture and Initial Solutions(55 minutes)
=========================================
5) Distributed Micro Service Communication architecture based on Content Semantic Xueting Li, China Telecom, 15 minutes
https://datatracker.ietf.org/doc/draft-li-dmsc-architecture/

6) Scalable Name-Based Packet Forwarding. Tianlong Li, BIT(Beijing Institute of Technology), 15 minutes
https://datatracker.ietf.org/doc/draft-song-dmsc-scalable-name-forwarding/

7) Architecture of Content based Service Router, Changwang Lin, H3C, 15 minutes
https://datatracker.ietf.org/doc/draft-lin-dmsc-content-based-service-router/

8) Technical Considerations for Distributed Micro Services Communication Daniel Huang, ZTE , 10mins
https://datatracker.ietf.org/doc/draft-yuan-dmsc-technical-considerations

==========================
Part III: Charter Discussions(15minutes)
==========================
9) Proposed Charter Discussions 15 minutes