Re: [dhcwg] VIV*O options.

On Wed, May 17, 2006 at 12:17:26PM -0700, Andre Kostur wrote:
> As long as you start after the Enterprise OID (and data length), that 
> shouldn't be an issue.

That's precisely the rub: this would use the same loop to process
VIV*O options (and also their contents, but that's not the point).

That is, VIV*O options (DHCP codes 124 and 125) are merely an
encapsulated space whose tag width is 4, and whose length width is
1, and which generally contain different encapsulated spaces.  Compare
DHCP which is 1/1, DHCPv6 which is 2/2.

I'm suggesting that the generic functions which implement that would
merely accept widths of 1, 2, 4 for code fields, and 1, 2 for length
fields - any combination.  1/2 is legal, 2/1 is legal.

> I'd interpret 42423 to align with 3925.  Sub-options 0 and 255 have no 
> special meaning.

I agree, except that it is IANA that defines enterprise-id 0 to be
reserved (so I expect it will never be used).  I guess I mean that
RFC3925 defers to IANA in my opinion.

-- 
David W. Hankins		"If you don't do it right the first time,
Software Engineer			you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins