HIP Diet EXchange (DEX)
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: The IESG <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Gonzalo Camarillo <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Protocol Action: 'HIP Diet EXchange (DEX)' to Proposed Standard (draft-ietf-hip-dex-11.txt) The IESG has approved the following document: - 'HIP Diet EXchange (DEX)' (draft-ietf-hip-dex-11.txt) as Proposed Standard This document is the product of the Host Identity Protocol Working Group. The IESG contact persons are Éric Vyncke and Suresh Krishnan. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-hip-dex/
This document was deferred by Terry Manderson in May 2018. The authors have taken into account all COMMENTs from the 2018 ballot, changing several parts of the document based on those COMMENTs. The document went successfully through a new IETF last call (that Eric requested in 2020) and the authors have addressed all points raised during this Last Call (including the SECDIR review by Don Eastlake). Security AD have currently some DISCUSSs based on the May 2020 telechat (that was cancelled pending the fix to those DISCUSS). Authors have addressed in revision -21 all DISCUSS (and some COMMENTs) points raised during the 2019 IESG review. So I am balloting the approval again in front of the 2020 IESG members. -éric -éric Technical Summary This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIPv2. The HIP DEX protocol is primarily designed for computation or memory- constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks. Working Group Summary There was WG consensus behind this document. Document Quality As discussed in RFC 6538, there are several implementations of the Experimental HIP specs. Nevertheless, it is not clear whether the HIP for Linux and OpenHIP implementations will be updated to comply with this specification. A proof-of-concept implementation of this spec for Sun SPOT hardware was developed in the past but is not currently being actively maintained. The authors also implemented this spec so that they could make educated design decisions about the protocol. However, the code was never distributed publicly. Personnel Gonzalo Camarillo is the document shepherd. Éric Vyncke is the responsible area director.