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

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

>>>>> Barr Hibbs writes:

Barr> I'm not sure I understand your point: I don't at all understand
Barr> the terms "non-globally scoped address" and "zone identifier" in
Barr> the IPv4 context.

That is why I point you to this. BTW, if you have read RFC 3291, you
should have at least stumbled across those terms and the following
reference:

   [21] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, A.
        and B. Zill, "IPv6 Scoped Address Architecture", Work in
        Progress.

The point is that you can have IPv4 addresses that are only used on a
given link and that there might be boxes that connect multiple such
links with IPv4 addresses that are "link local". On such a box, the
uniqueness property of the IPv4 address is lost and you need
additional information to resolve conflicts.

Barr> A DHCPv4 server DOES NOT listen for requests on the well-known
Barr> port for DHCPv6, will NEVER offer IPv6 addresses to its clients
Barr> (all of which MUST be IPv4), will NEVER support IPv6 addresses
Barr> in its options, NOR will it EVER support DHCPv6 protocol
Barr> messages.

Sure.

Barr> A DHCPv6 server is NOT an extension or upgrade path from DHCPv4:
Barr> the protocols use different message formats, different port
Barr> numbers, and a different protocol exchange.  We do not believe
Barr> that they can coexist on the same host.

Sure.


/js

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