Re: [saag] Fw:Fw:New Version Notification for draft-cui-dhc-dhcpv6-encryption-02.txt

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 29 July 2015 14:19 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2DC61A1EEE for <saag@ietfa.amsl.com>; Wed, 29 Jul 2015 07:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 85YmFDZAUr9T for <saag@ietfa.amsl.com>; Wed, 29 Jul 2015 07:19:40 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7ADC1A1B82 for <saag@ietf.org>; Wed, 29 Jul 2015 07:19:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B9042BE3F; Wed, 29 Jul 2015 15:19:38 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9elfrF9jpq1R; Wed, 29 Jul 2015 15:19:37 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.19.103]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 09C81BE7D; Wed, 29 Jul 2015 15:19:35 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1438179577; bh=0a1eajp3A04K2X/6KD/roXMWmCIyapK1Fd2mg4qw0AA=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=fONEwJT3xGYSm6ilbzvxbn8VRK6tZ6IqQWmymhPk0eEkzixNPJWFwgsWNGq0Cfc/+ ItcFKzeIctVwHUoJGVC1YqDO3RFEKPI3W2medxrYVr1sXrceS8k8IMyLWY5FUjL7Z3 fktlyIyG3Iz6OPFyns9YVY/vzP/mrA1nmDsZDWeY=
Message-ID: <55B8E0F2.3000403@cs.tcd.ie>
Date: Wed, 29 Jul 2015 15:19:30 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Lishan Li <lilishan48@126.com>
References: <313da830.6be8.14ed8564467.Coremail.lilishan48@126.com> <m2mvyfh1re.wl%randy@psg.com> <55B8A692.8080409@cs.tcd.ie> <m2a8ufgpjn.wl%randy@psg.com> <55B8D49A.1010402@cs.tcd.ie> <165fe8ce.ef05.14eda273b12.Coremail.lilishan48@126.com>
In-Reply-To: <165fe8ce.ef05.14eda273b12.Coremail.lilishan48@126.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/A-V8lG0rhwr-YXas_hhDNv6ntzo>
Cc: Security Area Advisory Group <saag@ietf.org>
Subject: Re: [saag] Fw:Fw:New Version Notification for draft-cui-dhc-dhcpv6-encryption-02.txt
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2015 14:19:41 -0000


On 29/07/15 15:11, Lishan Li wrote:
> Dear Stephen,
> 
> 
> As you said, we can use TOFU for the current mechanism. And in the
> future, we can specifies a set of key distribution mechanism for the
> DHCP. Could you please check whether my understanding is correct? 
> Thanks very much for your guidance.

So that *might* be the right answer, but it might not be. And
maybe it'll turn out to be right for DHCP server/service
authentication but not for other services. My main point is that
the analysis of the various key management schemes and DHCP
security services and DHCP deployments needs to be done before
we can be confident in saying which is the right thing to specify
now that might be deployed in reality.

We do I think have proof that symmetric keying for everything
fails, thanks to RFC3118, but for all the rest, as far as I know
we'd just be guessing right now.

Anyone volunteering to try help figure this out?

Cheers,
S.


> 
> 
> Best Regards, Lishan
> 
> 
> At 2015-07-29 21:26:50, "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
> wrote:
>> 
>> 
>> On 29/07/15 12:40, Randy Bush wrote:
>>> but this is a tangent.  the point is that protocols which rely
>>> on keying really need to nail the key distribution model(s).
>> 
>> I agree. But I think one of the issues here is that we don't 
>> (afaik) have a worked out analysis of how various key distribution
>> models play with DHCP.
>> 
>>> 
>>> while tofu may be one, is it really one that security folk think
>>> the ietf should advocate for set-up authenticity?  it's not how i
>>> want to make the wsj; and coffee shop mitm will be in the wsj
>>> soon enough.
>> 
>> Fair enough. OTOH, I don't think there will be one key distribution
>> model that will work well for all DHCP deployments. So we may end
>> up having to specify a set of mechanisms, when each is suitable to
>> use and the security considerations resulting. That's a chunk of
>> work, and a chunk of work where these authors are looking for
>> help. I do hope someone's going to volunteer to help them with 
>> that.
>> 
>> S.
>> 
>> 
>>> 
>>> randy
>>> 
>>> 
>> 
>> _______________________________________________ saag mailing list 
>> saag@ietf.org https://www.ietf.org/mailman/listinfo/saag