RIFT Key/Value Structure and Registry
draft-ietf-rift-kv-registry-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jordan Head , Tony Przygienda | ||
| Last updated | 2023-03-13 (Latest revision 2022-09-09) | ||
| Replaces | draft-head-rift-kv-registry | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Consensus: Waiting for Write-Up | |
| Document shepherd | Yuehua Wei | ||
| Shepherd write-up | Show Last changed 2022-09-12 | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | wei.yuehua@zte.com.cn |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The RIFT (Routing in Fat-Trees) 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 defines the various Key-Types (i.e. Well-Known, OUI, and Experimental) and a method to structure corresponding values.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)