[Rift] Re: RFC 9992 on Routing in Fat Trees (RIFT) Key/Value Topology Information Elements Structure and Processing

zhang.zheng@zte.com.cn Thu, 25 June 2026 00:41 UTC

Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: rift@mail2.ietf.org
Delivered-To: rift@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B06C8106DDC3C for <rift@mail2.ietf.org>; Wed, 24 Jun 2026 17:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782348084; bh=9AbQNsLc8CrE50VcOJ1sXq9Wqykw/uNiFU5Gb+1ZoAw=; h=In-Reply-To:References:Date:From:To:Cc:Subject; b=NwGPjACpMd1lbuVCPwfkuVWiKY3ePh/I9vEDdnCEYLjIwQ1XiFMhmoYwC3w0RhfSV gJ28joDdaLGhyCUuIO44g8ZPKgxZXJq6IG6R3xUWQgXXvCuWBWETBIOayVf3LfeZfr F/63BzQM3yUyS+L1ZqoZowM2GHIln2aEIJdyMvoI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hoA98WL319GC for <rift@mail2.ietf.org>; Wed, 24 Jun 2026 17:41:23 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id BF66E106DDC2A for <rift@ietf.org>; Wed, 24 Jun 2026 17:41:22 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4gm0Nc5PWGz5BNRf; Thu, 25 Jun 2026 08:41:20 +0800 (CST)
Received: from njy2app03.zte.com.cn ([10.40.13.14]) by mse-fl2.zte.com.cn with SMTP id 65P0fEko070614; Thu, 25 Jun 2026 08:41:14 +0800 (+08) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njy2app04[null]) by mapi (Zmail) with MAPI id mid203; Thu, 25 Jun 2026 08:41:14 +0800 (CST)
X-Zmail-TransId: 2afc6a3c792ac6f-65520
X-Mailer: Zmail v1.0
Message-ID: <20260625084114932KodsuMCdLx8pMY6-Jzo6R@zte.com.cn>
In-Reply-To: <MW4PR84MB3003D19C9BC586C47F6929EEF4EE2@MW4PR84MB3003.NAMPRD84.PROD.OUTLOOK.COM>
References: 178113788808.9.17411280645020210589@rfc-editor.org,MW4PR84MB3003D19C9BC586C47F6929EEF4EE2@MW4PR84MB3003.NAMPRD84.PROD.OUTLOOK.COM
Date: Thu, 25 Jun 2026 08:41:14 +0800
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: zhaohui.zhang=40hpe.com@dmarc.ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 65P0fEko070614
X-TLS: YES
X-ENVELOPE-SENDER: zhang.zheng@zte.com.cn
X-SOURCE-IP: 10.5.228.133 unknown Thu, 25 Jun 2026 08:41:20 +0800
X-CLEAN: YES
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6A3C7930.000/4gm0Nc5PWGz5BNRf
Message-ID-Hash: 7RWVYFPB5RYEO3HKCVN5HJHNLNDB2DUL
X-Message-ID-Hash: 7RWVYFPB5RYEO3HKCVN5HJHNLNDB2DUL
X-MailFrom: zhang.zheng@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rift.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rift@ietf.org, jordan.head@hpe.com, tonysietf@gmail.com, christian@kuhtz.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Rift] Re: RFC 9992 on Routing in Fat Trees (RIFT) Key/Value Topology Information Elements Structure and Processing
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/2LygyAiUm9G2JyUf18riswOGwqI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Owner: <mailto:rift-owner@ietf.org>
List-Post: <mailto:rift@ietf.org>
List-Subscribe: <mailto:rift-join@ietf.org>
List-Unsubscribe: <mailto:rift-leave@ietf.org>

Congratulations.
Sandy












Original


From: Zhang,Zhaohui(Jeffrey) <zhaohui.zhang=40hpe.com@dmarc.ietf.org>
  
To: rift@ietf.org <rift@ietf.org>;Head, Jordan <jordan.head@hpe.com>;Tony Przygienda <tonysietf@gmail.com>;Christian Kuhtz <christian@kuhtz.com>;
  
Date: 2026年06月24日 04:04
  
Subject: [Rift] Re: RFC 9992 on Routing in Fat Trees (RIFT) Key/Value Topology Information Elements Structure and Processing
  


Congratulations to the authors and WG for achieving another milestone!
Thanks to the shepherd Christian and reviewers!
 
Jeffrey
 
-----Original Message-----
From: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>  
Sent: Wednesday, June 10, 2026 8:31 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: drafts-update-ref@iana.org; rift@ietf.org; rfc-editor@rfc-editor.org
Subject: [Rift] RFC 9992 on Routing in Fat Trees (RIFT) Key/Value Topology Information Elements Structure and Processing
 
A new Request for Comments is now available in online RFC libraries.
 
        RFC 9992
 
        Title:      Routing in Fat Trees (RIFT) Key/Value Topology Information Elements Structure and Processing
        Author:     J. Head, Ed.,
                    T. Przygienda
        Status:     Proposed Standard
        Stream:     IETF
        Date:       June 2026
        Mailbox:    jordan.head@hpe.com,
                    tonysietf@gmail.com
        Pages:      12
 
 
        I-D Tag:    draft-ietf-rift-kv-tie-structure-and-processing-09
 
        URL:        https://urldefense.com/v3/__https://www.rfc-editor.org/info/rfc9992__;!!NEt6yMaO-gk!ASYQI7CaOv4IIpGPWJLJGd1AQjd3jVzBuBpXhuZtA1IFnype4FTbkcjtWmYHlR4Jao7sT4Y9EsykqzNnDIZmolqi$  
 
        DOI:        10.17487/RFC9992
 
The Routing in Fat Trees (RIFT) protocol allows for key/value pairs to be advertised within Key-Value Topology Information Elements (KV TIEs). The data contained within these KV TIEs can be used for any imaginable purpose.
 
This document specifies behavior for the various Key Types (i.e., Well-Known, Organizationally Unique Identifier (OUI), and Experimental) and a method to structure corresponding values. It also defines a Well-Known Key Sub-Type used for testing tie-breaking behavior.
 
This document is a product of the Routing In Fat Trees Working Group of the IETF.
 
STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
 
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ietf-announce__;!!NEt6yMaO-gk!ASYQI7CaOv4IIpGPWJLJGd1AQjd3jVzBuBpXhuZtA1IFnype4FTbkcjtWmYHlR4Jao7sT4Y9EsykqzNnDD3iNCZM$
  https://urldefense.com/v3/__https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist__;!!NEt6yMaO-gk!ASYQI7CaOv4IIpGPWJLJGd1AQjd3jVzBuBpXhuZtA1IFnype4FTbkcjtWmYHlR4Jao7sT4Y9EsykqzNnDKF6IdF5$  
 
For searching the RFC series, see https://urldefense.com/v3/__https://www.rfc-editor.org/search/__;!!NEt6yMaO-gk!ASYQI7CaOv4IIpGPWJLJGd1AQjd3jVzBuBpXhuZtA1IFnype4FTbkcjtWmYHlR4Jao7sT4Y9EsykqzNnDPfk4UbN$
For downloading RFCs, see https://urldefense.com/v3/__https://www.rfc-editor.org/series/rfc-download/__;!!NEt6yMaO-gk!ASYQI7CaOv4IIpGPWJLJGd1AQjd3jVzBuBpXhuZtA1IFnype4FTbkcjtWmYHlR4Jao7sT4Y9EsykqzNnDF4MCccI$  
 
Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.
 
 
The RFC Editor Team
 
_______________________________________________
RIFT mailing list -- rift@ietf.org
To unsubscribe send an email to rift-leave@ietf.org
_______________________________________________
RIFT mailing list -- rift@ietf.org
To unsubscribe send an email to rift-leave@ietf.org