Juniper Networks

1137 Innovation Way Sunnyvale CA USA jhead@juniper.net

Juniper Networks

1137 Innovation Way Sunnyvale CA USA prz@juniper.net

Routing in Fat-Trees RIFT 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. 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.

Description Routing in Fat-Trees (RIFT) allows for key/value pairs to be advertised within Key-Value Topology Information Elements (KV TIEs). There are no restrictions placed on the type of data that is contained in KV TIEs nor what the data is used for. It could contain a simple string or even Thrift encoded data. However, the KV elements SHOULD NOT be used to carry topology information used by RIFT itself to perform distributed computations. This document defines a Key Type Registry to maintain Well-Known and vendor specific Key Types in order to simplify interoperability between implementations and eliminate the risk of collision for future implementations. An Experimental Key Type is additionally defined.

Key-Value Pair Structure illustrates the generic Key-Value Pair structure.

Generic Key-Value Structure

where:

• Key-Type:

  A 1-byte value that identifies the Key Type. It MUST be a reserved value from the Key Value Type Registry that is defined later in this document.

  Key Identifier:

  A 3-byte value that identifies the specific Key and describes the structure of the contained values.

  Values:

  A variable length value that contains data associated with the Key. It SHOULD contain 1 or more elements. Whether the collection of elements allows duplicates and/or is ordered is governed by the particular key identifier.

Well-Known Key Type This section reserves a value in the Key Type Registry to indicate Well-Known Key Types that all implementations SHOULD support. As shown in , the Key-Type will be used to identify that the Key Type is Well-Known. The Key Identifier will be used to identify the specific Key and describe the structure of the contained values.

Well-Known Key Type

OUI Key Type This section reserves a value in the Key Type Registry to indicate an OUI (vendor-specific) Key Type that any implementation MAY support. As shown in , the Key-Type will be used to identify the Key Type as OUI. The Key Identifier MUST use an organization's reserved OUI space to indicate the Key and value structure.

OUI Key Type

Experimental Key Type This section reserves a value in the Key Type Registry to indicate an Experimental Key Type. As shown in , the Key-Type will be used to identify the Key Type as Experimental. The Key Identifier will be used to identify the specific experimental Key and describe the structure of the contained values.

Experimental Key Type

IANA Considerations This section requests that IANA help govern Key Types via the usual IANA registry procedures as per . All values not suggested are available for assignment. The allocation of new values MUST be done via "Expert Review" procedures.

Key Type Registry This section defines the Key Type Registry that is used to identify a specific Key Type. It also suggests values for Experimental, Well-Known, and OUI Key Types. The range of valid values is 1 - 255. 0 is an illegal value and MUST NOT be allocated to or used by any implementation. It MUST be ignored on reception.

Requested Entries

Key Type	Value	Description
Experimental	TBD1	Indicates that the Key is Experimental.
Well-Known	TBD2	Indicates that the Key is Well-Known.
OUI	TBD3	Indicates that the Key is OUI.

Experimental Key Type This value indicates that a specific key is Experimental. The range of valid values is 1 - 16777215 (2^24-1). 0 is an illegal value and MUST NOT be allocated to or used by any implementation. It MUST be ignored on reception.

Requested Entries

Experimental Key	Identifier	Description
Illegal	0	Not allowed.

Well-Known Key Type This value indicates that a specific key is Well-Known. The range of valid values is 1 - 16777215 (2^24-1). 0 is an illegal value and MUST not be allocated to or used by any implementation. It MUST be ignored on reception.

Requested Entries

Well-Known Key	Identifier	Description
Illegal	0	Not allowed.
MAC/IP Binding	TBD1	To be defined.
FAM Security Roll-Over Key	TBD2	To be defined.

OUI Key Type This value indicates a specific OUI Key using an organization's reserved OUI space. The range of valid values is 1 - 16777215 (2^24-1). 0 is an illegal value and MUST NOT be allocated to or used by any implementation. It MUST be ignored on reception.

Requested Entries

OUI Key	Identifier	Description
Illegal	0	Not allowed.

Security Considerations This document introduces no new security concerns to RIFT or other specifications referenced in this document given that the TIEs that carry KV pairs are already extensively secured by the RIFT specification itself.

Acknowledgements To be provided.

Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.