HIP Diet EXchange (DEX)
draft-ietf-hip-dex-18
| Document | Type | Active Internet-Draft (hip WG) | |
|---|---|---|---|
| Last updated | 2020-03-20 | ||
| Replaces | draft-moskowitz-hip-dex | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | plain text xml pdf 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 | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
On agenda of 2020-04-09 IESG telechat
(returning item)
Has 2 DISCUSSes. Needs 7 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Éric Vyncke | ||
| 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: September 21, 2020 Hirschmann Automation and Control
M. Komu
Ericsson
March 20, 2020
HIP Diet EXchange (DEX)
draft-ietf-hip-dex-18
Abstract
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.
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 September 21, 2020.
Moskowitz, et al. Expires September 21, 2020 [Page 1]
Internet-Draft HIP Diet EXchange (DEX) March 2020
Copyright Notice
Copyright (c) 2020 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) . . . . . . . . . . . . . . . 5
1.2. Applicability . . . . . . . . . . . . . . . . . . . . . . 6
1.3. Memo Structure . . . . . . . . . . . . . . . . . . . . . 7
2. Terms, Notation and Definitions . . . . . . . . . . . . . . . 7
2.1. Requirements Terminology . . . . . . . . . . . . . . . . 7
2.2. Notation . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3. Definitions . . . . . . . . . . . . . . . . . . . . . . . 8
3. Host Identity (HI) and its Structure . . . . . . . . . . . . 9
3.1. Host Identity Tag (HIT) . . . . . . . . . . . . . . . . . 10
3.2. Generating a HIT from an HI . . . . . . . . . . . . . . . 10
3.2.1. Why Introduce FOLD . . . . . . . . . . . . . . . . . 11
4. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Creating a HIP Association . . . . . . . . . . . . . . . 11
4.1.1. HIP Puzzle Mechanism . . . . . . . . . . . . . . . . 13
4.1.2. HIP State Machine . . . . . . . . . . . . . . . . . . 14
4.1.3. HIP DEX Security Associations . . . . . . . . . . . . 18
4.1.4. User Data Considerations . . . . . . . . . . . . . . 19
5. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 19
5.1. Payload Format . . . . . . . . . . . . . . . . . . . . . 19
5.2. HIP Parameters . . . . . . . . . . . . . . . . . . . . . 19
5.2.1. DH_GROUP_LIST . . . . . . . . . . . . . . . . . . . . 20
5.2.2. HIP_CIPHER . . . . . . . . . . . . . . . . . . . . . 20
5.2.3. HOST_ID . . . . . . . . . . . . . . . . . . . . . . . 21
5.2.4. HIT_SUITE_LIST . . . . . . . . . . . . . . . . . . . 21
5.2.5. ENCRYPTED_KEY . . . . . . . . . . . . . . . . . . . . 22
Show full document text