Re: [dhcwg] WG last call on draft-ietf-dhc-subscriber-id-01.txt>

Bud Millwood <budm@weird-solutions.com> Fri, 29 August 2003 14:23 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 KAA28141 for <dhcwg-archive@odin.ietf.org>; Fri, 29 Aug 2003 10:23:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sj6K-0007Dc-CT for dhcwg-archive@odin.ietf.org; Fri, 29 Aug 2003 09:15:40 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7TDFd6p027727 for dhcwg-archive@odin.ietf.org; Fri, 29 Aug 2003 09:15:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19shyx-0003fF-0A for dhcwg-web-archive@optimus.ietf.org; Fri, 29 Aug 2003 08:03:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15592 for <dhcwg-web-archive@ietf.org>; Fri, 29 Aug 2003 08:03:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19shyw-0001Vc-00 for dhcwg-web-archive@ietf.org; Fri, 29 Aug 2003 08:03:58 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19shyv-0001VZ-00 for dhcwg-web-archive@ietf.org; Fri, 29 Aug 2003 08:03:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sgU5-0007Pj-Hu; Fri, 29 Aug 2003 06:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19seXu-0008Vp-Jg for dhcwg@optimus.ietf.org; Fri, 29 Aug 2003 04:23:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26947 for <dhcwg@ietf.org>; Fri, 29 Aug 2003 04:23:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19seXr-0004lb-00 for dhcwg@ietf.org; Fri, 29 Aug 2003 04:23:47 -0400
Received: from webmail.mail.se.dataphone.net ([212.37.1.50] helo=intermail.se.dataphone.net) by ietf-mx with esmtp (Exim 4.12) id 19seXq-0004lY-00 for dhcwg@ietf.org; Fri, 29 Aug 2003 04:23:46 -0400
Received: from [193.12.201.10] (account budm@weird-solutions.com HELO offset.weird.se) by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.0.5) with ESMTP id 1827265; Fri, 29 Aug 2003 10:23:43 +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: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] WG last call on draft-ietf-dhc-subscriber-id-01.txt>
Date: Fri, 29 Aug 2003 10:25:51 +0200
User-Agent: KMail/1.4.3
References: <4.3.2.7.2.20030828064105.00b99008@localhost>
In-Reply-To: <4.3.2.7.2.20030828064105.00b99008@localhost>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200308291025.51415.budm@weird-solutions.com>
Content-Transfer-Encoding: quoted-printable
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

On Thursday 28 August 2003 12.45, Ralph Droms wrote:

> This message announces a WG last call on "DHCP Subscriber ID Suboption for
> the DHCP Relay Agent Option" <draft-ietf-dhc-subscriber-id-01.txt>.  The
> last call will conclude on Friday, 9/12.

This documents says:

   The value is simply an array of bytes which
   can be interpreted by the DHCP server in whatever manner wanted.  The
   value can be a character string giving the name of the subscriber,
   four bytes interpreted as a big endian unsigned integer giving the
   number of the subscriber, a string of hex digits giving the
   subscriber ID, or whatever is needed.  The precise definition of the
   bytes is left to the implementation and field use.

We would really like to see this suboption fixed to exactly one data type. The 
problem with allowing the subscriber id be a sequence of bytes or an ascii 
string is that when it comes time for us to report the subscriber id, say in 
a log file, we really have no idea how to display it correctly. We may end up 
displaying it as a sequence of bytes, although it is (according to the 
manufacturer's documentation) a printable string, or vice-versa.

- Bud

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