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

"Glen Zorn" <gwz@net-zen.net> Fri, 24 September 2010 01:11 UTC

Return-Path: <gwz@net-zen.net>
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 BE1A43A68F1 for <dhcwg@core3.amsl.com>; Thu, 23 Sep 2010 18:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.203
X-Spam-Level:
X-Spam-Status: No, score=-102.203 tagged_above=-999 required=5 tests=[AWL=0.396, BAYES_00=-2.599, 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 45lsAWftZMhd for <dhcwg@core3.amsl.com>; Thu, 23 Sep 2010 18:11:18 -0700 (PDT)
Received: from smtpauth17.prod.mesa1.secureserver.net (smtpauth17.prod.mesa1.secureserver.net [64.202.165.29]) by core3.amsl.com (Postfix) with SMTP id 5AC943A6851 for <dhcwg@ietf.org>; Thu, 23 Sep 2010 18:11:18 -0700 (PDT)
Received: (qmail 12914 invoked from network); 24 Sep 2010 01:03:23 -0000
Received: from unknown (124.157.132.203) by smtpauth17.prod.mesa1.secureserver.net (64.202.165.29) with ESMTP; 24 Sep 2010 01:03:22 -0000
From: Glen Zorn <gwz@net-zen.net>
To: 'Ted Lemon' <Ted.Lemon@nominum.com>
References: <201009230757.JAA27187@TR-Sys.de> <954E9F8A-B4F6-4A90-A091-33C4E7545DC5@nominum.com>
In-Reply-To: <954E9F8A-B4F6-4A90-A091-33C4E7545DC5@nominum.com>
Date: Fri, 24 Sep 2010 08:11:39 +0700
Organization: Network Zen
Message-ID: <000c01cb5b85$73e3ad70$5bab0850$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActbQoGSHiQf6XziSlGKhJL735jL+AAQieDQ
Content-Language: en-us
Cc: dhcwg@ietf.org, 'Alfred HÎnes' <ah@TR-Sys.de>
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: Fri, 24 Sep 2010 01:11:19 -0000

Ted Lemon [mailto://Ted.Lemon@nominum.com] writes:

...
> ...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.

Maybe.  However, that makes the DHCP usage of the vendor-specific construct
considerably more limited than other IETF protocols (e.g. RADIUS & Diameter
(in which even the IETF is considered a "vendor", assigned the vendor-id of
0)).