IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-karp-crypto-key-table-07. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon as possible.

IANA understands that, upon approval of this document, there are three actions which IANA must complete.

First, a new registry is to be created called the "KeyTable Protocols" registry. The registry is to be maintained through Specification Required as defined in RFC 5226.

Therre are initial values in the registry as follows:

------------------------------------------------------------------------
Protocol Name | Specification | Protocol Specific Values
------------------------------------------------------------------------
IEEE 802.1X CAK IEEE Std 802.1X-2010, A Key Management Domain (KMD).
"IEEE Standard for Local A string of up to 253 UTF-8
and Metropolitan Area characters that names the
Networks -- Port-Based transmitting authenticator's
Network Access Control". key management domain.

A Network Identifier (NID).
A string of up to 100 UTF-8
characters that identifies
a network service. The NID
can also be null, indicating
the key is associated with
a default service.
----------------------------------------------------------------------

Second, a new registry will be created called the "KeyTable KDFs" registry. The registry is to be maintained through First Come First Served as defined in RFC 5226.

There are no initial values in the new registry.

Third, a new registry will be created called the "KeyTable AlgIDs" registry. The registry is to be maintained through First Come First Served as defined in RFC 5226.

There are no initial values in the new registry.

IANA understands that these are the only actions required to be completed by IANA upon approval of this document.

Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.