Re: [Detnet] Available ISP topologies in academic work

peng.shaofu@zte.com.cn Wed, 27 March 2024 09:54 UTC

Return-Path: <peng.shaofu@zte.com.cn>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738A0C14F6B2 for <detnet@ietfa.amsl.com>; Wed, 27 Mar 2024 02:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level:
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 edh3KnP-UXMj for <detnet@ietfa.amsl.com>; Wed, 27 Mar 2024 02:54:17 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1868EC14F749 for <detnet@ietf.org>; Wed, 27 Mar 2024 02:54:13 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (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 4V4MSw3gdWz8XrRB for <detnet@ietf.org>; Wed, 27 Mar 2024 17:54:08 +0800 (CST)
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 mxct.zte.com.cn (FangMail) with ESMTPS id 4V4MSL3FFgz4xVbw; Wed, 27 Mar 2024 17:53:38 +0800 (CST)
Received: from njb2app06.zte.com.cn ([10.55.23.119]) by mse-fl1.zte.com.cn with SMTP id 42R9rUpp002995; Wed, 27 Mar 2024 17:53:30 +0800 (+08) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid201; Wed, 27 Mar 2024 17:53:33 +0800 (CST)
Date: Wed, 27 Mar 2024 17:53:33 +0800
X-Zmail-TransId: 2afe6603ec9dffffffff93d-40c18
X-Mailer: Zmail v1.0
Message-ID: <202403271753334319USZpcuMdtMx2rLKpXdkh@zte.com.cn>
In-Reply-To: <56baecbe18954627806ed624c4ef5701@huawei.com>
References: 56baecbe18954627806ed624c4ef5701@huawei.com
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: antoine.fressancourt=40huawei.com@dmarc.ietf.org
Cc: detnet@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 42R9rUpp002995
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6603ECC0.000/4V4MSw3gdWz8XrRB
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/oZYa1B1TuATvDheP9CWA5w_Mnz0>
Subject: Re: [Detnet] Available ISP topologies in academic work
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2024 09:54:21 -0000

Hi Antoine,

Thanks for your sharing a potential topology.

I have a little different understanding about the ideal reference topology, that is I think it may not be any topology in the real network.

Since for any particular topology in reality, someone can easily add new nodes (and their links) to the topology and let new flows that are waiting for admission check pass through these new nodes/links, by carefully planned TE paths, to avoid congestion with old flows that are already running in the network. 

As we always consider the worst-case when analyzing latency performance and service scale, the ideal topology is actually to observe each link separately.
That is, for each link, we assume that there are full competitive flows passing through it.
So the ideal reference topology may be like the following:

Many papers use topologies similar to the above for verification. I also see the similar topology provided by Toerless during the discussion in the maillist.
For example, https://www.ieee802.org/1/files/public/docs2010/ba-boiger-bridge-latency-calculations.pdf construct full competed frames on each hop to illustrate the burstiness cascade of TSN CBS.

Regards,
PSF



Original


From: AntoineFRESSANCOURT <antoine.fressancourt=40huawei.com@dmarc.ietf.org>
To: detnet@ietf.org <detnet@ietf.org>;
Date: 2024年03月21日 23:28
Subject: [Detnet] Available ISP topologies in academic work

_______________________________________________
detnet mailing list
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet

 

Hello,
 
Bouncing on the call for topologies to evaluate large scale DetNet proposals, I reminded some topologies I have been using during my PhD time, a few years ago. Unfortunately, some Internet tomography projects have stopped since then, and given the growing criticality of the Internet infrastructure, it seems that publicly available ISP-level topologies are difficult to get.
 
The reference project people go to when looking for ISP-level topologies is Rocketfuel (https://research.cs.washington.edu/networking/rocketfuel/). It is old but topologies extracted from this dataset are still used for routing mechanism evaluation.
 
Some specific ISP topologies have been refined and complemented with demands from flows in DEFO (https://sites.uclouvain.be/defo/). DEFO uses both real topologies from Rocketfuel and synthetic topologies generated with iGen (https://informatique.umons.ac.be/networks/igen/). The missing aspect in DEFO’s augmented topologies is the lack of latency bounds or Jitter bounds for flows, inter-arrival times etc. . Maybe we can augment those topologies to fit with what we need as a group to evaluate large scale detnet options ?
 
Best regards,
 Antoine Fressancourt