Re: [dhcwg] Fw:New Version Notification for draft-li-dhc-secure-dhcpv6-deployment-00.txt

神明達哉 <jinmei@wide.ad.jp> Thu, 15 October 2015 18:45 UTC

Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6C41AD26B for <dhcwg@ietfa.amsl.com>; Thu, 15 Oct 2015 11:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RTswabQJGirz for <dhcwg@ietfa.amsl.com>; Thu, 15 Oct 2015 11:45:05 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 027901AD16B for <dhcwg@ietf.org>; Thu, 15 Oct 2015 11:45:05 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so1413758igb.0 for <dhcwg@ietf.org>; Thu, 15 Oct 2015 11:45:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=e1Cc7uHj0dBIPgj4FKNy/lhYVyhUN0cIKWsGAVKIvHM=; b=ZPV+s3Lj8HqOvElN4nIxpKwdszN7FeFDFkSyLj4QpbG0VLuZVumvgCVb8FBbjp1PGY Rn9vhJNCBhaLtULjGcWNrFS/ggrjAUZ1p5q/sWLJulGRNdc2spck1sfUmtRBowPLlSEU WPZqpYdfV8v2HKejDhnwOX5xkJixOlWuVF2vbONopwgqnPMW5AAjeT608jHzBtPvrQAR n1DyuSN6bMRMvivj7I9eMSW/VWn89sVmDDdmhY34ErjOQkyxXlF9Oi803Zcia2JYvH11 43oY6T3SRppG4OBl05KCvXhnFFv0UPdvDAFqmN3LPS7NdWj7BdWArU/zDR66LUqbT/cT PrKg==
MIME-Version: 1.0
X-Received: by 10.50.70.1 with SMTP id i1mr502022igu.78.1444934704283; Thu, 15 Oct 2015 11:45:04 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.140.12 with HTTP; Thu, 15 Oct 2015 11:45:04 -0700 (PDT)
In-Reply-To: <CAJ3w4Nf-LqsW+UWNMa-FpkGWbUkZOJK=B1Xiq=3+koNfga0k0Q@mail.gmail.com>
References: <CAJ3w4Nf-LqsW+UWNMa-FpkGWbUkZOJK=B1Xiq=3+koNfga0k0Q@mail.gmail.com>
Date: Thu, 15 Oct 2015 11:45:04 -0700
X-Google-Sender-Auth: gi8a03OS4bmVwq0hNCy-CdJTTp0
Message-ID: <CAJE_bqdDSkTnOk278L9_Bn1F_wXdBZm2xTvC--v6FO9DcwH5wg@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
To: Lishan Li <lilishan48@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Yx-SuTAC0WKepbycrcDH-_qc8Tw>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Fw:New Version Notification for draft-li-dhc-secure-dhcpv6-deployment-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 18:45:06 -0000

At Wed, 14 Oct 2015 22:38:49 +0800,
Lishan Li <lilishan48@gmail.com> wrote:

> We have submitted a new draft draft-li-dhc-secure-dhcpv6-deployment-00.
> This draft analysis the DHCPv6 threat model, various key management schemes
> for secure DHCPv6 mechanisms deployment, and recommend the opportunistic
> security for DHCPv6.
> Could you please review the draft and any comments are welcome.

(making a couple of notes I happened to notice from a quick glance.
It's not a complete review).

In section 4 it states:

   TOFU MAY play a role in the scenario where the DHCPv6 client is
   mobile and connects to random networks such as public coffee shops.

It's surprising to me that the coffee shop scenario is referenced as a
case for TOFU several times (at least once in a sedhcpv6 discussion,
and now in this draft).  I'd say it's very naive to assume it can be safe
on first use in such a random network with random other users.

In section 5:

   In the scenario where the security policy is loss, the DHCPv6 server
   MAY NOT be preconfigured the authentication information, such as the

I suspect you meant 'MUST NOT' instead of 'MAY NOT'.

--
JINMEI, Tatuya