Re: [dhcwg] extending the DHCPv4 option space, VSO usage -- was: Re: issues with draft-grochla-80211-dhcp-option-00

Ted Lemon <Ted.Lemon@nominum.com> Thu, 23 September 2010 17:11 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C5873A69E4 for <dhcwg@core3.amsl.com>; Thu, 23 Sep 2010 10:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.301
X-Spam-Level:
X-Spam-Status: No, score=-106.301 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6vclHZLMvz7 for <dhcwg@core3.amsl.com>; Thu, 23 Sep 2010 10:11:51 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by core3.amsl.com (Postfix) with ESMTP id B52C03A698F for <dhcwg@ietf.org>; Thu, 23 Sep 2010 10:11:47 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTJuKZ7+RajpL6lPp3UhAy46CHsqyG+VH@postini.com; Thu, 23 Sep 2010 10:12:20 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2D17C1B82D8; Thu, 23 Sep 2010 10:12:07 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 23 Sep 2010 10:12:06 -0700
MIME-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <201009230757.JAA27187@TR-Sys.de>
Date: Thu, 23 Sep 2010 10:11:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <954E9F8A-B4F6-4A90-A091-33C4E7545DC5@nominum.com>
References: <201009230757.JAA27187@TR-Sys.de>
To: Alfred HÎnes <ah@TR-Sys.de>
X-Mailer: Apple Mail (2.1081)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] extending the DHCPv4 option space, VSO usage -- was: Re: issues with draft-grochla-80211-dhcp-option-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Sep 2010 17:11:55 -0000

I'm not going to respond point-by-point to your helpful and insightful comments because it would get rather long, but suffice it to say that you've raised some very useful issues that I will take into account when I write up the option extension document.

Your point about the extended parameter request list, however, pretty much puts to rest the idea that this should be a vendor option.   If it's a vendor option, the client can't request it.   So it really can't be a vendor option.

You've proposed a solution to that problem--standardize the format of vendor options, and add a vendor option request option.   I think it's unnecessary, but don't really oppose it.   But that solution would require a bunch of standards work, and I suspect it would be controversial.   It's not fair to delay this draft on the basis of the potential that that solution might someday be standardized.   And I still think that this sort of option isn't what vendor options are for--my understanding of vendor options is that they're for vendors--e.g., Cisco, not IEEE.