[Hipsec] Opsdir last call review of draft-ietf-hip-dex-06

Qin Wu <bill.wu@huawei.com> Fri, 23 February 2018 08:23 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E9301200C1; Fri, 23 Feb 2018 00:23:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Qin Wu <bill.wu@huawei.com>
To: ops-dir@ietf.org
Cc: hipsec@ietf.org, draft-ietf-hip-dex.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151937418915.22547.2306442974033264477@ietfa.amsl.com>
Date: Fri, 23 Feb 2018 00:23:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/IMUZVPCYZrUMAuoxB6vZdT_0DNM>
Subject: [Hipsec] Opsdir last call review of draft-ietf-hip-dex-06
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Feb 2018 08:23:09 -0000

Reviewer: Qin Wu
Review result: Ready

This document defines the Host Identity Protocol Diet EXchange (HIP
   DEX) protocol for constrained devices. The draft is well written. I believe
   it is ready for publication.
Major issue: None
Minor issue: Editorial
1.It is not clear how fine-grained policy control defined in IKEv2 is different
from policy control defined in HIP DEX protocol? In the draft, local policies
are mentioned many times, however it is not clear what local policy for HIP DEX
Protocol looks like? Is it possbile to carry policy control parameters(e.g.,
ACL parameter) in the HIP DEX protocol message? Would it be great to provide
example to clarify this. 2. Is Nonce I same as radom value #I? 3. Is puzzle
difficulty K same as #K used in the HIP R1 described in section 7? 4. Is puzzle
difficulty K same as low-order #K bits of the RHASH? If the answer is yes,
please make the term and symbol used in the draft consistent.