HIP Diet EXchange (DEX)
|Document||Type||Expired Internet-Draft (hip WG)|
|Authors||Robert Moskowitz , Rene Hummen , Miika Komu|
|Last updated||2021-08-02 (Latest revision 2021-01-19)|
|Stream||Internet Engineering Task Force (IETF)|
|Intended RFC status||Proposed Standard|
Expired & archivedplain text html xml htmlized pdfized bibtex
SECDIR Telechat review (of -20) Has Nits
SECDIR Last Call review (of -11) Has Nits
SECDIR Last Call review (of -06) Has Issues
|Stream||WG state||Dead WG Document|
|Document shepherd||Gonzalo Camarillo|
|Shepherd write-up||Show Last changed 2019-10-31|
|IESG||IESG state||Expired (IESG: Dead)|
|Responsible AD||Éric Vyncke|
This document has a long history... Based on the July 2020 IESG evaluation (and the DISCUSS from Ben in March 2020 and Roman in December 2020), the authors have heavily modified and improved the text. The modifications were so important that I requested another IETF Last Call that is now completed with two supportive comments.
Hence, I am returning this item to the agenda of the last formal for the sitting IESG 2020.
-- note of July 2020 --
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 I (Eric V) requested in early 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.
|Send notices to||Gonzalo Camarillo <email@example.com>|
|IANA||IANA review state||IANA - Not OK|
This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2) and specifically developed for use on low end processors. The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and cryptographic hash functions. 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. Unlike HIPv2, HIP DEX does not support Forward Secrecy (FS), and MUST only be used on devices where FS is prohibitively expensive. 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.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)