IETF Logo Mail Archive

Re: [dhcwg] Interpretation of Option 60 (Vendor Class ID)

Bud Millwood <budm@weird-solutions.com> Tue, 07 May 2002 15:33 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12723 for <dhcwg-archive@odin.ietf.org>; Tue, 7 May 2002 11:33:42 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA05226 for dhcwg-archive@odin.ietf.org; Tue, 7 May 2002 11:33:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04533; Tue, 7 May 2002 11:30:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04507 for <dhcwg@optimus.ietf.org>; Tue, 7 May 2002 11:30:02 -0400 (EDT)
Received: from fep04-svc.swip.net (fep04.swip.net [130.244.199.132]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12501 for <dhcwg@ietf.org>; Tue, 7 May 2002 11:29:55 -0400 (EDT)
Received: from there ([193.12.201.10]) by fep04-svc.swip.net with SMTP id <20020507152928.MCOH29474.fep04-svc.swip.net@there>; Tue, 7 May 2002 17:29:28 +0200
Content-Type: text/plain; charset="iso-8859-1"
From: Bud Millwood <budm@weird-solutions.com>
Reply-To: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: "Cosmo, Patrick" <Patrick@incognito.com>
Subject: Re: [dhcwg] Interpretation of Option 60 (Vendor Class ID)
Date: Tue, 07 May 2002 16:36:52 +0200
X-Mailer: KMail [version 1.3.2]
References: <4FB49E60CFBA724E88867317DAA3D198692A12@homer.incognito.com.>
In-Reply-To: <4FB49E60CFBA724E88867317DAA3D198692A12@homer.incognito.com.>
Cc: dhcwg@ietf.org
MIME-Version: 1.0
Message-Id: <20020507152928.MCOH29474.fep04-svc.swip.net@there>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA04508
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 8bit

On Tuesday 07 May 2002 15.40, you wrote:

> RFC 2132 states that option 60 "is a string of n octets". We are having a
> little debate about how to interpret this and would like to know how
> others, and the working group, interpret this option.

I went back and forth on this, and finally decided the best approach was to 
present it as a string, but allow escape sequences in the string so the user 
can at least work with non-printable characters if need be.

> does anyone know of any devices that send data for this option which cannot
> be interpreted as a string?

Experience with my customer base has shown that they (and/or their devices) 
expect it to be a string.

Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 8 758 3700
fax: +46 8 758 3687
mailto:budm@weird-solutions.com

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email