I believe there will be clients that implement only those messages required to complete an Information-Request message exchange.
RFC 3736 gives implementation guidelines for implementing the parts of RFC 3315 required for the Information-Request message exchange, for clients, servers and relay agents (although, if memory serves, RFC 3736 has no impact on relay agents).
Using "RFC 3736" to describe the Information-Request message exchange might be a useful shorthand. However, as implementations that support the Information-Request message exchange might not be based on RFC 3736, a different shorthand might be less confusing.
- Ralph
At 03:54 PM 8/12/2004 +0530, Syam Madanapalli wrote:
> > Sorry, it doesn't clearly answer my question. So can I rephrase your > > statement to "3736 is an implementation hint for DHCPv6 servers and > > relays, not clients."? > > > > Oh, sorry for the confusion. > > Yes I believe so.
That means there will not be any DHCPv6 Client that just implements RFC 3736 only? My understanding is that a host can implement light weight DHCPv6 Client (RFC 3736) for getting the other configuration (non -address) information.
> > Greg > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [EMAIL PROTECTED] > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
