option 61

"Edie E. Gunter" <edie@watson.ibm.com> Tue, 02 July 1996 21:24 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20846; 2 Jul 96 17:24 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20842; 2 Jul 96 17:24 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa19119; 2 Jul 96 17:24 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA29858; Tue, 2 Jul 1996 17:16:07 -0400
Date: Tue, 2 Jul 1996 17:16:07 -0400
Message-Id: <9607022059.AA14904@edisto.watson.ibm.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Edie E. Gunter" <edie@watson.ibm.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: option 61
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

The dhc-options-1533update-04.txt document states: 

   The client identifier MAY consist of type-value pairs similar to the
   'htype'/'chaddr' fields defined in [3]. For instance, it MAY consist
   of a hardware type and hardware address. In this case the type field
   SHOULD be one of the ARP hardware types defined in STD2 [22].  A
   hardware type of 0 (zero) should be used when the value field
   contains an identifier other than a hardware address (e.g. a fully
   qualified domain name).

It then diagrams the option to look like this:

   Code   Len   Type  Client-Identifier
   +-----+-----+-----+-----+-----+---
   |  61 |  n  |  t1 |  i1 |  i2 | ...
   +-----+-----+-----+-----+-----+---

Is the "Type" field optional?  Is that what "MAY" in the first sentence
above means?  If it is optional, then how does one tell when it is
there and when it is not (i.e. when can I interpret that 3rd byte
as a type field)?  Couldn't there by interoperability problems if
one implementation assumes the type byte is there and another does not?

Edie