IETF Logo Mail Archive

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

Erik Kline <ek@google.com> Thu, 30 July 2015 09:42 UTC

Return-Path: <ek@google.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 5B2B61A0363 for <saag@ietfa.amsl.com>; Thu, 30 Jul 2015 02:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level:
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gdA9sluH4Fmk for <saag@ietfa.amsl.com>; Thu, 30 Jul 2015 02:42:17 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (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 5E7191A01EA for <saag@ietf.org>; Thu, 30 Jul 2015 02:42:17 -0700 (PDT)
Received: by wibud3 with SMTP id ud3so60272803wib.0 for <saag@ietf.org>; Thu, 30 Jul 2015 02:42:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qO6dXaVoRTXTv0NhICjUVJeFvIcz57qZvXlMlHoGYNU=; b=oMIK69/67I8y25ao8HmFkMvEmlwkVUjxuKpIyPRxkWG7Cxr6UIz0uhyv40zmGoiws5 TFIwpjrcMH25qZ30y5AE+19vdi1M91r2MBX/VtQ5/OE/EYqAVOs4QctZUU7xI8STNxo1 QJrD0+sX6Xs3odN0zQEJnbvjG0FiDhZGZSk4b6+FuXrdLmEiABYLv6QZUN+U4Gr9I/9T T6t6oKcEOJVR7FY1Ckl2h8wepwr/Sp43bMbK1+PMFhrMyxRWPuKuVjAK5526APbAtgEH t9JEHjssaCR7avXnRw35A0Od/0LvL8o6sh92j84o7unWhYl1pan3IP70b6ocCfQBQE+1 VoKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=qO6dXaVoRTXTv0NhICjUVJeFvIcz57qZvXlMlHoGYNU=; b=VhPnEScRMsINiaHDkdQjUJJNQV20i+docV6+fg++fZQ/Mo2TsWwDqkddckXJH1oaO8 prpwskeYXfPk9+omMFV7Ac59ncy4UNe/hus7rU2KsUlRSI7x7Svz1ElBQP5p4COd7D9t bp0EtkssY/dTEjF+48M1HS10AjreH6OUWnCL1n7bE7j8engwaPltcZcBvimDva1sDfn+ zXXBkBT8b5t47RwU4EC2SMnhxBF5MxLLK5uImAYp7Iv+umAnZV84kvQYl4Pu0gzgqE0/ mY2gzoyEcDv2HMTFoq6Sbl6OQHxGPCJvi416HuiwMv/D8Z8Y0NZ/lfupUVpMs2P+k08o XqWw==
X-Gm-Message-State: ALoCoQnm5zjpoXh4HW5DH4xBYkl2RwNRFYDlIUSMF1mXPo4D9cDBwreKWNKeXsghNRALwIAKUjRA
X-Received: by 10.180.85.194 with SMTP id j2mr4475917wiz.11.1438249336005; Thu, 30 Jul 2015 02:42:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.138.203 with HTTP; Thu, 30 Jul 2015 02:41:56 -0700 (PDT)
In-Reply-To: <76f2dbd9.194fc.14ede0cda90.Coremail.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> <m2y4hyg2za.wl%randy@psg.com> <DM2PR0301MB0655D564B5F697E14F5CF371A88B0@DM2PR0301MB0655.namprd03.prod.outlook.com> <76f2dbd9.194fc.14ede0cda90.Coremail.lilishan48@126.com>
From: Erik Kline <ek@google.com>
Date: Thu, 30 Jul 2015 11:41:56 +0200
Message-ID: <CAAedzxoG+OyXJvYT2nCGDW2t+9zv0FH0SLkdAuEenWYMY3Nhgg@mail.gmail.com>
To: Lishan Li <lilishan48@126.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/09kD6ath0yoxfvB0TiVPMHpn6TA>
X-Mailman-Approved-At: Thu, 30 Jul 2015 08:10:51 -0700
Cc: Security Area Advisory Group <saag@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [saag] [dhcwg] 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: Thu, 30 Jul 2015 09:42:22 -0000

>>Even in the "trusted network" scenario, the gain is only apparent in the
>> absence of link-layer protection. For example, enterprise Wi-Fi networks
>> typically use 802.1x and EAP to negotiate a link-layer encryption key
>> specific to the client. This goes a long way towards protecting all the link
>> traffic, including DHCP. Clearly there is a residual risk of on-line
>> attackers, such as a local computer owned by a virus. That risk is generally
>> mitigated by filters in the switches, restricting the sending of DHCP and RA
>> packets. DHCP encryption would be useful if it was easier to deploy than
>> those filters, and more secure.
>>
> [Lishan]: The link-layer encryption 802.1x and EAP you mentioned is only
> designed for the Wi-Fi network. For the general scenario, such as wired
> environment, the DHCP encryption is needed.

802.1x works on wired ethernet.

v2.23.0 | Report a Bug | By Email