[dhcwg] Deployment consideration for SeDHCPv6

Sheng Jiang <jiangsheng@huawei.com> Thu, 05 June 2014 09:39 UTC

Return-Path: <jiangsheng@huawei.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 A080E1A015B for <dhcwg@ietfa.amsl.com>; Thu, 5 Jun 2014 02:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.552
X-Spam-Level:
X-Spam-Status: No, score=-4.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 wkPDmLwRUwp3 for <dhcwg@ietfa.amsl.com>; Thu, 5 Jun 2014 02:39:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABEFE1A011F for <dhcwg@ietf.org>; Thu, 5 Jun 2014 02:39:02 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHW16836; Thu, 05 Jun 2014 09:38:55 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Jun 2014 10:38:00 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Jun 2014 10:38:54 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.68]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Thu, 5 Jun 2014 17:38:42 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <ted.lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>, 神明達哉 <jinmei@wide.ad.jp>
Thread-Topic: Deployment consideration for SeDHCPv6
Thread-Index: AQHPgKHv1Ac5DKV250+NBNKyOimJag==
Date: Thu, 05 Jun 2014 09:38:41 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE891C2@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <5388F901.1000709@gmail.com> <78B235AF-D94C-40F1-9C76-4159B3A0A043@nominum.com> <CAJE_bqf4UZeFifHMhM=Vo2X66+ab7cnhb19K-XD_+_pr7-VS1A@mail.gmail.com> <FF49B4DE-E45F-4FF7-9C2D-5FA72FE66A4D@gmail.com> <C7C8884E-499D-4B55-B978-8D7A4D21EE3C@nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923AE88462@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE88462@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/uB0Z8sU40yxRyLtiPrmfcY-hJwk
Cc: dhcwg <dhcwg@ietf.org>
Subject: [dhcwg] Deployment consideration for SeDHCPv6
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: <http://www.ietf.org/mail-archive/web/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, 05 Jun 2014 09:39:05 -0000

Hi, Jinmei, Ralph, Ted and all,

The below text is the proposal from SeDHCPv6 authors in order to clarify the applicability. We plan to add these text, of course after reaching consensus in the mail list, into the next update version. Any comments are appreciated.

Deployment consideration

This document has defined two levels of authentication: full authentication based on certificate or pre-shared key verification and weaker authentication based on leap-of-faith. Both levels can be applied on servers and clients. The deployment scenarios can be categorized as below:

	Authenticating a server on a client
	   - Both fully authentication and leap-of-faith can be used. The latter is weaker. But, it is better than no protection by narrowing the attack scope.

	Authenticating a client on a server
	   - With fully authentication, the server can selectively serve a specific client (or deny specific clients). The server can prevent an attacker from breaking an existing DHCPv6 session of a client. The server can also prevent an attacker from pretending to be a past legitimate client.
	   - With leap-of-faith authentication, the server can only prevent an attacker from breaking an existing DHCPv6 session of a client and pretending to be a past legitimate client.
	   - A server may maintain both fully authentication and leap-of-faith authentication at the same time. In such scenarios, the clients authenticated through leap-of-faith normally have lower priority or/and limited network access. One example would be in an enterprise network, office devices or employers’ devices used full authentication are allowed to access all network resources, including the internal database; devices of occasional visitors also get authenticated, but through leap-of-faith, they can only access public web services of this enterprise and the Internet.

Best regards,

Sheng

>-----Original Message-----
>From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Sheng Jiang
>Sent: Tuesday, June 03, 2014 1:55 PM
>To: Ted Lemon; Ralph Droms
>Cc: dhcwg; 神明達哉
>Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May
>18
>
>The authors plan to produce an update version, which addresses the
>comments received during the WGLC, in two weeks. The "applicability
>statement" would be major target in this update. We will come up with a
>proposal text and invoke discussion in email list in a couple of days.
>
>Best regards,
>
>Sheng
>
>>-----Original Message-----
>>From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
>>Sent: Tuesday, June 03, 2014 4:53 AM
>>To: Ralph Droms
>>Cc: dhcwg; 神明達哉
>>Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May
>>18
>>
>>I have no personal objection to Jinmei's text, although I think it's incomplete.
>>Could you guys work with Sheng to see if you can come up with a mutually
>>agreeable update?
>>
>>_______________________________________________
>>dhcwg mailing list
>>dhcwg@ietf.org
>>https://www.ietf.org/mailman/listinfo/dhcwg
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg