RIFT Keys Structure and Well-Known Registry in Key Value TIE
draft-przygienda-rift-kv-registry-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Tony Przygienda
|
|
Last updated |
|
2020-12-13
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group A. Przygienda
Internet-Draft Juniper
Intended status: Standards Track December 13, 2020
Expires: June 16, 2021
RIFT Keys Structure and Well-Known Registry in Key Value TIE
draft-przygienda-rift-kv-registry-00
Abstract
This document describes key structure of keys contained within RIFT
key-value TIEs.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 16, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Przygienda Expires June 16, 2021 [Page 1]
Internet-Draft draft-ietf-przygienda-kv-registry December 2020
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Description . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Key Type Registry . . . . . . . . . . . . . . . . . . . . . . 2
3. OUI Key Type . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Well-Known Key Type . . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5.1. Key Type Registry . . . . . . . . . . . . . . . . . . . . 3
5.1.1. Requested Entries . . . . . . . . . . . . . . . . . . 3
5.2. Well-Known Key Type Registry . . . . . . . . . . . . . . 4
5.2.1. Requested Entries . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Description
[I-D.ietf-rift-rift] specifies a topology information element (TIE)
that can carry unstructured key value pairs of data. This document
defines a registry for the keys to allow for vendor specific values
being carried without risking a collision with future standardized
values.
This document specifies also several well-known keys and their values
including a registry to allow for easier interoperability between
implementations.
2. Key Type Registry
The first octet of every key is a value from a "RIFT Key Types
Registry" which may specify the according key structure further.
3. OUI Key Type
This section reserves a key type value to indicate a vendor specific
key with further indication via Organizationally Unique Identifier
(OUI) which organization the key belongs to. The value of that first
octet is TBD1. The structure of the key is indicated in the figure
Figure 1.
Przygienda Expires June 16, 2021 [Page 2]
Internet-Draft draft-ietf-przygienda-kv-registry December 2020
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TBD1 | Organizationally Unique Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Specific Key Part ...
Figure 1: OUI Key
4. Well-Known Key Type
This section reserves a key type value in Key Type Registry to
indicate a well-known key that all implementations SHOULD support.
The type is followed by a 3 octets value from a "RIFT Well-Known Key"
Show full document text