RE: [dhcwg] Interface

The client *MUST* send the messages through the interface being configured. The client uses multicast messages and if directly received by the server, that's the way it knows what link the client is on. If a relay receives it and forwards it, that's how it can tag the message having come from that link so that the server knows what link the client is on. If the server doesn't know the correct link, it can't assign the proper addresses.

Note however that I feel if a server had told the client it may use unicast and the client has addresses of sufficient scope, there is no reason why the client must use that interface. This requires that client's source address is one of the addresses for that interface that is of "value" to the server in identifying the correct link. For example, a globally unique address would likely be of sufficient scope.

- Bernie

-----Original Message-----
From: Guja, ArturX [mailto:ArturX.Guja@intel.com]
Sent: Tuesday, September 18, 2001 3:33 PM
To: dhcwg@ietf.org
Subject: [dhcwg] Interface

Sorry for posting so many questions, but I'm working overtime on my
diploma here. I'm really grateful for any input.

So another one:
Is the client required to send DHCPv6 messages through the interface it is
going to configure, or can it send them through any interface?
I mean, why should there be such a restriction? After all, it sends
the DUID and the link-local address in the message. It might as well
use ANY interface for communication with the server, eg. when it is
multi-homed, and there is a DHCP server available on only one link,
but it serves the whole net :)))

I know it was mentioned somewhere, but I can't find it. :)))
Soory to bother you :)))

Artur

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