>>>>> On Wed, 28 Apr 2004 12:16:15 -0400,
>>>>> Ralph Droms <[EMAIL PROTECTED]> said:
> I think the O flag (if we keep it!) should simply specify DHCPv6, with no
> implication about the way in which DHCPv6 is used.
> "Stateless DHCPv6" is simply a way to use some of the messages from the full
> specification in RFC 3315. RFC 3376 is a guideline to the implementation of
> DHCPv6 that uses just Information-request/Reply messages. A client can
> choose to use the Request/Reply or the Information-request/Reply message
> exchange to obtain other configuration information without address assignment.
Before going to further details, please let me clarify one thing about
RFC3736 (you should have meant RFC3736 by "RFC 3376" BTW).
In my understanding, RFC3736 defines a certain class of implementation
that is a subset of RFC3315, even though RFC3736 is basically a
"guideline". Specifically, RFC3736 defines the implementation class
in its Section 5.
So, there can be four types of servers and clients:
A. servers that conform to RFC3315. (These servers also conform to
RFC3736)
B. clients that conform to RFC3315 (These servers also conform to
RFC3736)
C. servers that only conform to RFC3736 (and do not implement the rest
of RFC3315)
D. clients that only conform to RFC3736 (and do not implement the rest
of RFC3315)
Is the above understanding correct?
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
