HIP Diet EXchange (DEX)
draft-ietf-hip-dex-23
| Document | Type | Active Internet-Draft (hip WG) | |
|---|---|---|---|
| Authors | Robert Moskowitz , Rene Hummen , Miika Komu | ||
| Last updated | 2021-01-15 | ||
| Replaces | draft-moskowitz-hip-dex | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | plain text html xml pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Gonzalo Camarillo | ||
| Shepherd write-up | Show (last changed 2019-10-31) | ||
| IESG | IESG state | AD Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Éric Vyncke | ||
| IESG note |
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. -éric |
||
| Send notices to | Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
HIP WG R. Moskowitz, Ed.
Internet-Draft HTT Consulting
Intended status: Standards Track R. Hummen
Expires: 19 July 2021 Hirschmann Automation and Control
M. Komu
Ericsson
15 January 2021
HIP Diet EXchange (DEX)
draft-ietf-hip-dex-23
Abstract
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.
Status of This Memo
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 19 July 2021.
Moskowitz, et al. Expires 19 July 2021 [Page 1]
Internet-Draft HIP Diet EXchange (DEX) January 2021
Copyright Notice
Copyright (c) 2021 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 Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. The HIP Diet EXchange (DEX) . . . . . . . . . . . . . . . 6
1.2. Applicability . . . . . . . . . . . . . . . . . . . . . . 7
1.2.1. Partial Computational Cost of FS via SIGMA . . . . . 8
1.3. Memo Structure . . . . . . . . . . . . . . . . . . . . . 9
2. Terms, Notation and Definitions . . . . . . . . . . . . . . . 9
2.1. Requirements Terminology . . . . . . . . . . . . . . . . 9
2.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3. Definitions . . . . . . . . . . . . . . . . . . . . . . . 10
3. Host Identity (HI) and its Structure . . . . . . . . . . . . 11
3.1. Host Identity Tag (HIT) . . . . . . . . . . . . . . . . . 12
3.2. Generating a HIT from an HI . . . . . . . . . . . . . . . 12
3.2.1. Why Introduce FOLD . . . . . . . . . . . . . . . . . 13
4. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 13
4.1. Creating a HIP Association . . . . . . . . . . . . . . . 14
4.1.1. HIP Puzzle Mechanism . . . . . . . . . . . . . . . . 16
4.1.2. HIP State Machine . . . . . . . . . . . . . . . . . . 16
4.1.3. HIP DEX Security Associations . . . . . . . . . . . . 20
4.1.4. User Data Considerations . . . . . . . . . . . . . . 21
5. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Payload Format . . . . . . . . . . . . . . . . . . . . . 21
5.2. HIP Parameters . . . . . . . . . . . . . . . . . . . . . 21
5.2.1. DH_GROUP_LIST . . . . . . . . . . . . . . . . . . . . 22
5.2.2. HIP_CIPHER . . . . . . . . . . . . . . . . . . . . . 22
5.2.3. HOST_ID . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.4. HIT_SUITE_LIST . . . . . . . . . . . . . . . . . . . 24
Show full document text