Re: [dhcwg] Rev of DHCPv6 spec

I would like to get clarification on when does a server send an unicast
option,
1. does the server send unicast option  whenever the client is on the same
link (20.11 is not clear about it) (or)
2. Is it an administrative policy that decides if the client can
unicast/multicast of messages. If it is so, is there any example of the
scenario where the server would not specify the option despite being on the
same link.
3. why is the client required to check if the client and server are on the
same link if  unicast option is already obtained from the server ( 16.1.1 )

And also,
 Is it not sufficient to have both client and server to be on the same link
to unicast client's message ?, if so what is the server response to
client's unicast if it didn't send unicast option to the client and still
gets messages unicast'ed to it.
-suresh

Ralph Droms <rdroms@cisco.com> on 10/11/2001 07:31:31 AM

Please respond to Ralph Droms <rdroms@cisco.com>

To:   dhcwg@ietf.org
cc:    (bcc: Suresh Kodati/India/IBM)
Subject:  [dhcwg] Rev of DHCPv6 spec

I've finished another rev of the DHCPv6 spec (-20d), which is available at
http://www.dhcp.org/dhcpv6.tty  I plan to submit this draft of the spec to
the IETF for publication on 10/12.  The list of issues addressed by this
draft is included below; these issues were discussed at the DHC WG meeting
in London (8/2001).  The -20d draft does not include any changes related to
IAs.  The changes related to IAs will appear in the next published rev of
the draft.

- Ralph

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg