IETF Logo Mail Archive

Re: [dhcwg] WGLC: draft-ietf-dhc-client-id-02

Ted Lemon <Ted.Lemon@nominum.com> Mon, 16 April 2012 12:33 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 A684221F85E4 for <dhcwg@ietfa.amsl.com>; Mon, 16 Apr 2012 05:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.485
X-Spam-Level:
X-Spam-Status: No, score=-106.485 tagged_above=-999 required=5 tests=[AWL=0.114, 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 HKcSYEgqBk5g for <dhcwg@ietfa.amsl.com>; Mon, 16 Apr 2012 05:33:23 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id ACAB621F85F9 for <dhcwg@ietf.org>; Mon, 16 Apr 2012 05:33:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKT4wRiFDAfad0nX4nMb+eN8UlSlubIpRU@postini.com; Mon, 16 Apr 2012 05:33:13 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 50B181B83BD for <dhcwg@ietf.org>; Mon, 16 Apr 2012 05:33:12 -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 455E619006C; Mon, 16 Apr 2012 05:33:12 -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; Mon, 16 Apr 2012 05:33:12 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Bud Millwood <budmillwood@gmail.com>
Thread-Topic: [dhcwg] WGLC: draft-ietf-dhc-client-id-02
Thread-Index: AQHNGj3M8A+q0iwf8kCif1zWgGUm5padnZkAgAA9b4A=
Date: Mon, 16 Apr 2012 12:33:11 +0000
Message-ID: <21F1CED2-9B1E-4BBA-9CCB-66A1367465F4@nominum.com>
References: <64B00097-8ACB-4170-9303-8F863A47C2B5@nominum.com> <CAOpJ=k22-62DvQukZq=Qxx47Sf4EUOtEd+FdwHuj9KnMw4gR-w@mail.gmail.com>
In-Reply-To: <CAOpJ=k22-62DvQukZq=Qxx47Sf4EUOtEd+FdwHuj9KnMw4gR-w@mail.gmail.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="Windows-1252"
Content-ID: <841506E5E1AC764C8B940E7D221EDC4F@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-client-id-02
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: Mon, 16 Apr 2012 12:33:24 -0000

It is nearly inconceivable to me that some device out in the wild will check for the client identifier and drop the packet if it's there.   Anything's possible, I guess, but I really don't think this is likely.

Still, there is only one way to find out.   I think making it an administratively-configured option is a valid risk-management strategy.

v2.23.0 | Report a Bug | By Email