I reviewed the latest version and think it is ready for publication.

br Andrei

On 1/20/2021 4:09 PM, Eric Vyncke (evyncke) wrote:
> There have been several of *significant* changes  since the IETF last call in 
> November 2019 on the -11 revision, so, as the responsible AD, I am asking the 
> IETF community for 3rd review on the latest revision -24.
>
> The changes include at least: applicability statement, use of the FOLD 
> function, I_NONCE, input keying material for master/pair-wise key generation, 
> security section, some deleted DH groups and ciphers.
>
> For your convenience the diff between the two versions: 
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-hip-dex-24%26url1%3Ddraft-ietf-hip-dex-11&data=04%7C01%7Candrei.gurtov%40liu.se%7C370565e71f474343976108d8bd55aebf%7C913f18ec7f264c5fa816784fe9a58edd%7C0%7C0%7C637467522989981278%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lSa0YQ9%2BtdOFPnLhq5sHEAkFHlYDHQ6eRMv3lRGSFhg%3D&reserved=0
>  
>
> Thank you in advance for your valuable comments before the 3rd of February 
> 2021,
>
> -éric vyncke
>
> PS: thank you for the previous reviewers, your comments have helped the 
> authors to improve the document. Thank you as well to the authors for 
> listening to those comments.
>
> -----Original Message-----
> From: <[email protected]> on behalf of The IESG 
> <[email protected]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Wednesday, 20 January 2021 at 15:48
> To: IETF-Announce <[email protected]>
> Cc: Gonzalo Camarillo <[email protected]>, 
> "[email protected]" <[email protected]>, Eric Vyncke 
> <[email protected]>, "[email protected]" 
> <[email protected]>, "[email protected]" 
> <[email protected]>, "[email protected]" <[email protected]>
> Subject: Last Call: <draft-ietf-hip-dex-24.txt> (HIP Diet EXchange (DEX)) to 
> Proposed Standard
>
>
>     The IESG has received a request from the Host Identity Protocol WG (hip) 
> to
>     consider the following document: - 'HIP Diet EXchange (DEX)'
>       <draft-ietf-hip-dex-24.txt> as Proposed Standard
>
>     The IESG plans to make a decision in the next few weeks, and solicits 
> final
>     comments on this action. Please send substantive comments to the
>     [email protected] mailing lists by 2021-02-03. Exceptionally, comments 
> may
>     be sent to [email protected] instead. In either case, please retain the 
> beginning
>     of the Subject line to allow automated sorting.
>
>     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.
>
>
>
>
>
>     The file can be obtained via
>     
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-hip-dex%2F&amp;data=04%7C01%7Candrei.gurtov%40liu.se%7C370565e71f474343976108d8bd55aebf%7C913f18ec7f264c5fa816784fe9a58edd%7C0%7C0%7C637467522989981278%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=gdpptEioiBmuD05oC43afzYEIbxF9DmntVdDFlM3coI%3D&amp;reserved=0
>
>
>
>     No IPR declarations have been submitted directly on this I-D.
>
>
>     The document contains these normative downward references.
>     See RFC 3967 for additional information: 
>         rfc6261: Encrypted Signaling Transport Modes for the Host Identity 
> Protocol (Experimental - IETF stream)
>
>
>
>
>
> _______________________________________________
> Hipsec mailing list
> [email protected]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fhipsec&amp;data=04%7C01%7Candrei.gurtov%40liu.se%7C370565e71f474343976108d8bd55aebf%7C913f18ec7f264c5fa816784fe9a58edd%7C0%7C0%7C637467522989981278%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=jTLGcfXwfHhcrf0sSLvnqJW4avH5sNdYj0vhuVaJl%2Bo%3D&amp;reserved=0

_______________________________________________
Hipsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/hipsec

Reply via email to