IETF Logo Mail Archive

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

Bernard Aboba <bernard_aboba@hotmail.com> Sun, 02 August 2015 01:27 UTC

Return-Path: <bernard_aboba@hotmail.com>
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 41C571A88E4 for <saag@ietfa.amsl.com>; Sat, 1 Aug 2015 18:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 khaoPHamkBF4 for <saag@ietfa.amsl.com>; Sat, 1 Aug 2015 18:27:25 -0700 (PDT)
Received: from BLU004-OMC2S28.hotmail.com (blu004-omc2s28.hotmail.com [65.55.111.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FFBD1A88E2 for <saag@ietf.org>; Sat, 1 Aug 2015 18:27:25 -0700 (PDT)
Received: from BLU181-W40 ([65.55.111.72]) by BLU004-OMC2S28.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 1 Aug 2015 18:27:24 -0700
X-TMN: [JqBmDgHymDH7fRmS1S6tbNpluaS7jgnH]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU181-W40A804FB089C688A209AC593880@phx.gbl>
Content-Type: multipart/alternative; boundary="_8c619a94-2876-48cd-a475-6c65f88a7ac3_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Alan DeKok <aland@deployingradius.com>
Date: Sat, 01 Aug 2015 18:27:24 -0700
Importance: Normal
In-Reply-To: <4E607681-7B1F-4128-9F24-D98FE23AA958@deployingradius.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>, <m2y4hyg2za.wl%randy@psg.com>, <DM2PR0301MB0655D564B5F697E14F5CF371A88B0@DM2PR0301MB0655.namprd03.prod.outlook.com>, <4E607681-7B1F-4128-9F24-D98FE23AA958@deployingradius.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 02 Aug 2015 01:27:24.0388 (UTC) FILETIME=[629C5A40:01D0CCC2]
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/S2CPkXFT8LjMgrPR_v4eg8ZDXIA>
Cc: Security Area Advisory Group <saag@ietf.org>
Subject: Re: [saag] 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: Sun, 02 Aug 2015 01:27:27 -0000

Alan said: 
"Or just sign the DHCP packets with a key derived from the 802.1X keys.  That requires no interaction with the switches.  Only the DHCP client and server need to be updated."


[BA] Authenticating a DHCP packet with a unicast key derived between the station and the AP would not prove authorization to act as a DHCP server, so IMHO it would not add any value beyond what is already provided by 802.11 security.  Similarly, authenticating a multicast DHCP packet with a key derived from the 802.11 group key would also not demonstrate authorization to act as a DHCP server so that also adds no value.

v2.23.0 | Report a Bug | By Email