[Hipsec] Fwd: New Version Notification for draft-ietf-hip-dex-12.txt

[Robert Moskowitz <[e-mail]>]

I believe this version answers all the IESG issues.

Please review, there are some important additions.

EKR had a number of security concerns.  Some I feel don't apply to HIP, 
like use an AEAD for HIP packet security.

But there are a number of added sections, particularly in Security 
Considerations that are worth the group's review that I have things 
stated properly.

Also there is a new parameter, I_NONCE to add Initiator randomness into 
the Master Key generation.  There is some cleanup in the KEYMAT section 
to reflect this.

So please take a read through.

Thank you


-------- Forwarded Message --------
Subject: 	New Version Notification for draft-ietf-hip-dex-12.txt
Date: 	Sun, 09 Feb 2020 23:11:55 -0800
From: 	[e-mail]
To: 	Robert Moskowitz <[e-mail]>, Rene Hummen 
<[e-mail]>, Miika Komu <[e-mail]>




A new version of I-D, draft-ietf-hip-dex-12.txt
has been successfully submitted by Miika Komu and posted to the
IETF repository.

Name: draft-ietf-hip-dex
Revision: 12
Title: HIP Diet EXchange (DEX)
Document date: 2020-02-09
Group: hip
Pages: 57
URL: https://www.ietf.org/internet-drafts/draft-ietf-hip-dex-12.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-hip-dex/
Htmlized: https://tools.ietf.org/html/draft-ietf-hip-dex-12
Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-hip-dex
Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-hip-dex-12

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 Perfect
Forward Secrecy (PFS), and MUST only be used on devices where PFS 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.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat