| Internet-Draft | Additional Private Use Ranges for LAKE | September 2026 |
| Tiloca | Expires 21 March 2027 | [Page] |
This document adds Private Use ranges to IANA registries that pertain to the Lightweight Authenticated Key Exchange (LAKE) protocol.¶
This note is to be removed before publishing as an RFC.¶
Discussion of this document takes place on the Lightweight Authenticated Key Exchange Working Group mailing list (lake@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/lake/.¶
Source for this draft and an issue tracker can be found at https://gitlab.com/crimson84/draft-tiloca-lake-private-use-ranges.¶
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 21 March 2027.¶
Copyright (c) 2026 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 include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Lightweight Authenticated Key Exchange (LAKE) protocol [RFC9528] provides points of extensibility, for which related IANA registries exist.¶
When they were created, some of those registries did not include ranges with registration procedure "Private Use" (see Section 4.1 of [RFC8126]). Later on, it was brought to attention that having such ranges available would be convenient for private deployments.¶
This document rectifies this situation by adding Private Use ranges to three IANA registries missing those, as specified in Section 3.¶
This document uses the acronym "LAKE", expanded to "Lightweight Authenticated Key Exchange", to denote the protocol specified as "EDHOC" in [RFC9528]. Identifiers defined literally in [RFC9528] or in IANA registries (e.g., the names of the EDHOC registries themselves) are unchanged.¶
This document and the Private Use ranges defined in Section 3 do not impact the security of the LAKE protocol. When using values from such Private Use ranges, the security considerations compiled in Section 9 of [RFC9528] still apply.¶
This document has the following actions for IANA.¶
IANA is asked to add the following two ranges to the "EDHOC Method Types" registry [Method.Types] within the "Ephemeral Diffie-Hellman Over COSE (EDHOC)" registry group:¶
For both ranges, the registration procedure is "Private Use" per Section 4.1 of [RFC8126].¶
IANA is asked to add the following two ranges to the "EDHOC Error Codes" registry [Error.Codes] within the "Ephemeral Diffie-Hellman Over COSE (EDHOC)" registry group.¶
For both ranges, the registration procedure is "Private Use" per Section 4.1 of [RFC8126].¶
Tobias Müller pointed out the usefulness of a Private Use range for External Authorization Data (EAD) labels, which triggered the development of this document.¶
The author thanks Göran Selander and Mališa Vučinić for their early feedback during the preparation of this document.¶