RE: [dhcwg] Interpretation of Option 60 (Vendor Class ID)
Patrick Guelat <patg@imp.ch> Wed, 08 May 2002 21:11 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 RAA24058 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 17:11:19 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA28360 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 17:11:27 -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 RAA28298; Wed, 8 May 2002 17:09:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA08313 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 03:01:00 -0400 (EDT)
Received: from mail.imp.ch (root@mail.imp.ch [157.161.1.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27747 for <dhcwg@ietf.org>; Wed, 8 May 2002 03:00:52 -0400 (EDT)
Received: from harem.imp.ch (harem.imp.ch [157.161.4.8]) by mail.imp.ch (8.11.6/8.11.6) with ESMTP id g4870rx35269; Wed, 8 May 2002 09:00:53 +0200 (CEST)
Received: from localhost (patg@localhost) by harem.imp.ch (8.11.2/8.11.2) with ESMTP id g4870qj573696; Wed, 8 May 2002 09:00:52 +0200 (MES)
X-Authentication-Warning: harem.imp.ch: patg owned process doing -bs
Date: Wed, 08 May 2002 09:00:52 +0200
From: Patrick Guelat <patg@imp.ch>
To: Steve Gonczi <steve@relicore.com>
cc: "Cosmo, Patrick" <Patrick@incognito.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Interpretation of Option 60 (Vendor Class ID)
In-Reply-To: <BFELJLKGHEJOPOPGJBKKMEIDCBAA.steve@relicore.com>
Message-ID: <Pine.SGI.4.33.0205080856390.466610-100000@harem.imp.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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
Steve, I agree with you that there is no implication on the character set to be used. But the term 'string' implies for me that it `could' be zero terminated, i.e. that it's ok to treat zero as a termination character in that case. If this is not the case, 'string' should be changed to 'array' imho. -Patrick -- Patrick Guelat, ImproWare AG Network Services, CH-4133 Pratteln Mail: patg@imp.ch - Phone: +41 61 826 93 00 (ext: 13) On Tue, 7 May 2002, Steve Gonczi wrote: > Interpretation of Option 60 (Vendor Class ID)IMHO it is meant to be an array > of unsigned bytes. > > The authors would have spelled out any formatting restrictions, such as a > specific > character set, or required zero termination if they had that in mind. > > You will see that they did so in other cases. ( e.g.: section 9.9). > > Because the authors did not restrict the allowed octet values in any way, we > can not safely > use a zero termination convention. ( embedded zeros are allowed by the > definition) > > /sG > -----Original Message----- > From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of > Cosmo, Patrick > Sent: Tuesday, May 07, 2002 9:41 AM > To: dhcwg@ietf.org > Subject: [dhcwg] Interpretation of Option 60 (Vendor Class ID) > > 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. > > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Interpretation of Option 60 (Vendor Class… Cosmo, Patrick
- Re: [dhcwg] Interpretation of Option 60 (Vendor C… Bud Millwood
- RE: [dhcwg] Interpretation of Option 60 (Vendor C… Steve Gonczi
- RE: [dhcwg] Interpretation of Option 60 (Vendor C… Richard Barr Hibbs
- Re: [dhcwg] Interpretation of Option 60 (Vendor C… Michael Carney
- RE: [dhcwg] Interpretation of Option 60 (Vendor C… Richard Barr Hibbs
- RE: [dhcwg] Interpretation of Option 60 (Vendor C… Patrick Guelat
- Re: [dhcwg] Interpretation of Option 60 (Vendor C… Ted Lemon