Re: FW: Question regarding address specs for IPv4-only protocol MIBs

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

>>>>> Wijnen, Bert (Bert) writes:

[...]

Barr> As the protocol messages, method of address allocation, and
Barr> methods of identifying clients and leases are completely
Barr> different between DHCPv4 and DHCPv6, we believe that this
Barr> subtree could only be used for a DHCPv4 server.

Barr> Alternative One: specify the addresses using the InetAddressIPv4
Barr> convention -- this is, perhaps, the simplest approach.

Barr> Alternative Two: specify the addresses using the pair
Barr> InetAddressType and InetAddress, including the enumeration
Barr> clause "{ ipv4(1) }" for InetAddressType and the size clause
Barr> "(SIZE(4))" for InetAddress, along with the text "An
Barr> implementation is only required to support IPv4 addresses" in
Barr> each object description -- this is slightly misleading because
Barr> the subtree is not intended to ever be used for IPv6.

Barr> Alternative Three: specify the addresses as in Two, but without
Barr> the restricting enumeration and size clauses, adding explanatory
Barr> text to the conformance section -- this unfortunately causes the
Barr> OID subidentifier strings used in the index of four tables to
Barr> exceed the maximum size (by as much as 382.)

Alternative One only works if you will never ever have to support non
globally scoped addresses which potentially require a zone identifier
values to be distinguishable. If you can't be totally sure, using
alternative Three is the safer bet.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>