Re: [Rift] comments on draft-przygienda-rift-dragonfly-00

zhang.zheng@zte.com.cn Thu, 02 November 2023 06:35 UTC

Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: rift@ietfa.amsl.com
Delivered-To: rift@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75EA4C1519BE for <rift@ietfa.amsl.com>; Wed, 1 Nov 2023 23:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 Kj-TbdusqeTb for <rift@ietfa.amsl.com>; Wed, 1 Nov 2023 23:35:04 -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 B2198C1519BB for <rift@ietf.org>; Wed, 1 Nov 2023 23:35:02 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (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 4SLYyX1ccRz8XrX7; Thu, 2 Nov 2023 14:35:00 +0800 (CST)
Received: from njb2app05.zte.com.cn ([10.55.22.121]) by mse-fl2.zte.com.cn with SMTP id 3A26Yjkd095828; Thu, 2 Nov 2023 14:34:45 +0800 (+08) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid203; Thu, 2 Nov 2023 14:34:47 +0800 (CST)
Date: Thu, 02 Nov 2023 14:34:47 +0800
X-Zmail-TransId: 2afe65434307ffffffffacf-c8f20
X-Mailer: Zmail v1.0
Message-ID: <202311021434471337568@zte.com.cn>
In-Reply-To: <CO6PR05MB7796EC58A06D9DDC5A08C4F7ACDCA@CO6PR05MB7796.namprd05.prod.outlook.com>
References: 202310271740269533158@zte.com.cn, CO6PR05MB7796EC58A06D9DDC5A08C4F7ACDCA@CO6PR05MB7796.namprd05.prod.outlook.com
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: prz@juniper.net
Cc: rift@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 3A26Yjkd095828
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 65434314.000/4SLYyX1ccRz8XrX7
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/ZBMraiCtdTQqvGS619LW1iXOHjY>
Subject: Re: [Rift] comments on draft-przygienda-rift-dragonfly-00
X-BeenThere: rift@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rift>, <mailto:rift-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift/>
List-Post: <mailto:rift@ietf.org>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rift>, <mailto:rift-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Nov 2023 06:35:08 -0000

Hi Tony, 
Yes. I also think RIFT protocol is good to be used in dragonfly+ topology. 
And the basic logic of protocol is not changed.  
I have some comments on the 00 version: 
1, If the ToF node still advertises the default route to leaf nodes? If it is, how many routes will be advertised to the leaf nodes, if these routes will be different due to the group?
2, If I understand right, in case the topology is used for AI training, the leaf node will select another route when the used route is congested. So in section 4.1, route needs to be changed when the destination is unreachable or congested. 
And futhermore, the dragonfly+ dense and sparse modes are different, will we consider the dense mode also? 
What do you think of it?
Best regards,
Sandy











Original


From: AntoniPrzygienda <prz@juniper.net>
To: 张征00007940;
Cc: rift@ietf.org <rift@ietf.org>;
Date: 2023年10月27日 21:04
Subject: Re: [Rift] comments on draft-przygienda-rift-dragonfly-00




daft explains how horizontals are used and that the DF+ backbone is basically collection of special inter-fabric horizontal links 
 
draft already adds some procedures for LIE processing and additional computation .
 
Good thing is it does NOT change really the flooding scopes/rules since those are the hardest part of the spec to implement correctly as is usual the case for IGPs 
 
if you have alternate proposal, well, there is a WG meet in 2 weeks 😉 
 

tony 


 



 

 
Juniper Business Use Only
 

From: zhang.zheng@zte.com.cn <zhang.zheng@zte.com.cn>
 Date: Friday, 27 October 2023 at 11:40
 To: Antoni Przygienda <prz@juniper.net>
 Cc: rift@ietf.org <rift@ietf.org>
 Subject: [Rift] comments on draft-przygienda-rift-dragonfly-00 



[External Email. Be cautious of content]
 
Hi Tony, 
Thank you for providing this draft! 
IMO it's an interesting topic that using RIFT in dragonfly or dragonfly+ topology. 
Could you please post the draft figures here for reading the draft easily?
And will you consider using east-west connection between the TOFs? 
Though it will change the flooding and computation procedure in RIFT protocol, we think it may be another feasible way. 
Thank you very much!
Best regards,
Sandy