Re: [dhcwg] missing pieces for the Secure DHCPv6 draft
神明達哉 <jinmei@wide.ad.jp> Sun, 01 November 2015 04:20 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 4B1931B29D3 for <dhcwg@ietfa.amsl.com>; Sat, 31 Oct 2015 21:20:24 -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 2tdyRyR5X8KY for <dhcwg@ietfa.amsl.com>; Sat, 31 Oct 2015 21:20:23 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (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 DE3FC1B29CF for <dhcwg@ietf.org>; Sat, 31 Oct 2015 21:20:22 -0700 (PDT)
Received: by igdg1 with SMTP id g1so36880406igd.1 for <dhcwg@ietf.org>; Sat, 31 Oct 2015 21:20:22 -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=s/ni7KP+Oc0BVF2ZEG8AU/NGJrU6zv89ZQhZYE3hPtg=; b=N9e0Ttgu6VojxPkwcOwFKQygWIvDtdEw1y+++IUiq+27JShDXDfZVbpNHZt6J67/OV LGulQRZlhQVtHLukFfBhdg77wSYUoROLGpgxokpGLxt84u1CeUvtOTF2Ohfs6xbZnwWA lAMhXW9o99UqIGwEEJzASD/iY/CFaoJ7WTlzjMtVEuJFCBUWot5MgdRYfV1CqlzlFGJ6 UjdNVOJvOeKnYRmcLunTl0OQJy3IBBDHdlYDC3Qim6SgN9c6UAdj0taelISGFD9MYOBy Liiq2LhvWiQS6F9S2fEhlD0VM76NuXfQ5fu8UsIaDzpcnK1ONKe/BLOzgcGmbGeDwrzt iZUA==
MIME-Version: 1.0
X-Received: by 10.50.70.1 with SMTP id i1mr5830679igu.78.1446351622299; Sat, 31 Oct 2015 21:20:22 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.140.71 with HTTP; Sat, 31 Oct 2015 21:20:22 -0700 (PDT)
In-Reply-To: <201510310102.t9V12gEL036127@givry.fdupont.fr>
References: <CAJE_bqfU__kQMXWq8cdc8ppQg3qzTkKbywnQdHDTrqhZhp_Geg@mail.gmail.com> <201510310102.t9V12gEL036127@givry.fdupont.fr>
Date: Sun, 01 Nov 2015 13:20:22 +0900
X-Google-Sender-Auth: da5VQMgDy8PPGhSseXtThixIayc
Message-ID: <CAJE_bqfuUd6b2rAA_2BsWvVA9BbRO2FFogJjrkkx0FL2VVz9_A@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/v8eYQfC_f2ksIPiFGHk3p-FIBn0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, charliekaufman@outlook.com
Subject: Re: [dhcwg] missing pieces for the Secure DHCPv6 draft
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: Sun, 01 Nov 2015 04:20:24 -0000
At Sat, 31 Oct 2015 02:02:42 +0100, Francis Dupont <Francis.Dupont@fdupont.fr> wrote: > > For the purpose of the sedhcpv6 draft, if usability issues of TOFU > > still continues to be blocking, I think we can simply remove it from > > the draft as an alternative. > > => perhaps the solution is to move all deployment/applicability stuff > from the secure DHCPv6 "mechanisms" I-D so it can be published as soon > as the threat model is complete? That's a possibility and in a sense cleaner approach. If the wg now agrees with that I'm fine with that, too, but I'd note we once rejected the idea. -- JINMEI, Tatuya