Data Plane Topology ID

Huzhibo <huzhibo@huawei.com> Fri, 01 July 2022 07:20 UTC

From: Huzhibo <huzhibo@huawei.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Data Plane Topology ID
Thread-Topic: Data Plane Topology ID
Thread-Index: AdiNGu0Xn8FxRR82QleUMKi0WRcVUg==
Date: Fri, 01 Jul 2022 07:20:12 +0000
Message-ID: <5ce1e59ff92b4f7993cbc03cd76f0534@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
Content-Type: multipart/alternative; boundary="_000_5ce1e59ff92b4f7993cbc03cd76f0534huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FdlTVZwC-ZVtdU7DvaA1_xGKkLM>
Precedence: list

Hi 6man:
We submitted a draft of the DataPlane extension Topo ID: https://tools.ietf.org/id/draft-li-6man-topology-id-00.txt.
This draft sloves the following problem: MT And Flexalgo Shared Addresses Space. RFC5120 defines if the topologies are quality of
Service (QoS) partitioned, then the Differentiated Services CodePoint (DSCP) bits in the IP packet header can be utilized to make the
decision.
However, we now apply MT and Flexalgo to other scenarios, such as slicing, where QoS cannot be used to differentiate topologies.
This document introduces a dedicated data plane ID to distinguish between different topologies. In this way, different topologies (MT or Flexalgo)
can reuse the same address space, simplifying multi-topology deployment and improving multi-topology performance.
We expect your review and comments.

Thanks
Zhibo Hu

Data Plane Topology ID Huzhibo