Re: [dhcwg] Choosing a value for option 60 (Vendor Class ID)

Patrick Guelat <patg@imp.ch> Fri, 07 June 2002 02:27 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 WAA26877 for <dhcwg-archive@odin.ietf.org>; Thu, 6 Jun 2002 22:27:15 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id WAA16356 for dhcwg-archive@odin.ietf.org; Thu, 6 Jun 2002 22:27:46 -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 WAA16303; Thu, 6 Jun 2002 22:26:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20330 for <dhcwg@ns.ietf.org>; Wed, 5 Jun 2002 13:25: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 NAA08108 for <dhcwg@ietf.org>; Wed, 5 Jun 2002 13:24:30 -0400 (EDT)
Received: from nbs.imp.ch (nbs.imp.ch [157.161.4.7]) by mail.imp.ch (8.11.6/8.11.6) with ESMTP id g55HOjI81334; Wed, 5 Jun 2002 19:24:46 +0200 (CEST)
Received: from nbs.imp.ch (localhost [127.0.0.1]) by nbs.imp.ch (8.12.3/8.12.3) with ESMTP id g55HOiFc11368631; Wed, 5 Jun 2002 19:24:44 +0200 (MES)
Received: from localhost (patg@localhost) by nbs.imp.ch (8.12.3/8.12.3/Submit) with ESMTP id g55HOiNR11692892; Wed, 5 Jun 2002 19:24:44 +0200 (MES)
X-Authentication-Warning: nbs.imp.ch: patg owned process doing -bs
Date: Wed, 5 Jun 2002 19:24:43 +0200
From: Patrick Guelat <patg@imp.ch>
To: Chris Pearson <chris.pearson@infocus.com>
cc: "'dhcwg@ietf.org'" <dhcwg@ietf.org>, De Tran <de.tran@infocus.com>
Subject: Re: [dhcwg] Choosing a value for option 60 (Vendor Class ID)
In-Reply-To: <EEBC1981C362D311AA230008C7E627BA07D8EB05@toccata>
Message-ID: <Pine.SGI.4.44.0206051909090.24767-100000@nbs.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

Hi

I'm working in the Cable modem field and the DOCSIS1.1 specification
requires the use of option 60. cablemodems report their capabilities
using this option.

RFC2132 doesn't tell us how it should look like, so I can just tell you
how this is used in the DOCSIS-world, even if this is probably not what
can be called best practice. I don't know if this option is actively used
in other applications by now.

The format used in DOCSIS is in NVT ASCII consistinng of two parts:

docsis1.1:[0-9A-F]+

Two fields seperated by a colon, 'docsis1.1' and an ascii-hexstring
describing the modem capabilities (TVL in TLV based).

Example:

        OPTION:  60 (VENDOR CLASS IDENTIFIER):
docsis1.1:05240101010201010301010401010501010601010701FF0801080901030A01010B01180C0101

I don't have any idea why this format was chosen, now if there was a place
to register the identifiers before the ':' it wouldn't be that bad.

Regards
	Patrick
--
Patrick Guelat, ImproWare AG Network Services, CH-4133 Pratteln
Mail: patg@imp.ch - Phone: +41 61 826 93 00 (ext: 13)

On Tue, 4 Jun 2002, Chris Pearson wrote:

> Greetings to the work group!  This is my first post, so please let me know
> if I'm off-topic.
>
> After grepping the Web and parsing the thread "Interpretation of Option 60
> (Vendor Class ID)" from this list, I'm pretty certain I know the answer to
> this question ("no"), but in the spirit of leaving no stone unturned, I'll
> ask it anyway: Is there a standard, IANA registry, best practice or
> convention regarding the values that clients may assign to vendor class ID?
>
> In the case I'm presently concerned with, the ID will be embedded in
> firmware and thus unchangeable in the field, so it's important to get it
> right.  The main goal is to reduce probability of collision with other
> vendor IDs, and more generally, to harmonize with prevailing wisdom.  (But
> re the character string vs. octet string question, I'm convinced that
> interoperation with major DHCP server implementations requires the former
> interpretation.)  Any and all comments appreciated.
>
> -- Chris Pearson
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>



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