Re: [dhcwg] draft-bi-dhc-sec-option

Ted Lemon <Ted.Lemon@nominum.com> Wed, 28 March 2012 16:30 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 532A921E819E for <dhcwg@ietfa.amsl.com>; Wed, 28 Mar 2012 09:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.481
X-Spam-Level:
X-Spam-Status: No, score=-106.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WG2kifCiA3S for <dhcwg@ietfa.amsl.com>; Wed, 28 Mar 2012 09:30:51 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9FA21E8191 for <dhcwg@ietf.org>; Wed, 28 Mar 2012 09:30:51 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKT3M8ux4MXMsnYjDAxUd9lE0unKGAA/1l@postini.com; Wed, 28 Mar 2012 09:30:51 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BC8B41B80D5 for <dhcwg@ietf.org>; Wed, 28 Mar 2012 09:30:50 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B1074190064; Wed, 28 Mar 2012 09:30:50 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Wed, 28 Mar 2012 09:30:50 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Cui Yang <cuiyang@huawei.com>, Alper Yegin <alper.yegin@yegin.org>, dhc WG <dhcwg@ietf.org>
Thread-Topic: [dhcwg] draft-bi-dhc-sec-option
Thread-Index: AQHNDCs97FdY0hE8ekCzaZlLGDHV+ZZ+QWZIgAIPqID//5YZaQ==
Date: Wed, 28 Mar 2012 16:30:50 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472D1DD6@mbx-01.win.nominum.com>
References: <CAC16W0DXs4q5ApuiyN4pVJVuXQQunAFMGnu5JjJvszcWjnncJA@mail.gmail.com>, <2F208A97-BFF3-4820-BA98-3E47AC41D992@yegin.org>, <8D23D4052ABE7A4490E77B1A012B6307472C3E6F@mbx-02.win.nominum.com>, <8CC0CB0BCAE52F46882E17828A9AE2161F479B8F@SZXEML508-MBS.china.huawei.com>
In-Reply-To: <8CC0CB0BCAE52F46882E17828A9AE2161F479B8F@SZXEML508-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] draft-bi-dhc-sec-option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 28 Mar 2012 16:30:52 -0000

> The proposed DHCP option is aimed to help set up the security mechanism, i.e., carrying IP addresses of PKI server, etc.
> But the option itself does not need to be protected, or in other words, the security does not necessarily rely on the DHCP option.

So if a rogue DHCP server provides a PKI server address, the client will be able to tell that it is not a legitimate server without revealing sensitive information to it?