Kacheong Poon wrote:
> For 4, NWAM can probably do the following. NWAM can perform
> WPAD and check if there is proxy info available from any
> server (we need to figure out what to do if there are multiple
> servers providing different info). If the info is available,
> then NWAM may do nothing. A WPAD aware app will find the
> proper info from the server(s). But if there is no proxy
> info available from the server(s) and there is a NWAM proxy
> setting associated with the current network environment, NWAM
> may "fake" a DHCP server (*) reply using that info to any query
^^^^^^^^^^^^^^^^^^^^
I think I've used the wrong words here. The proposal is
not trying to impersonate a DHCP server. It is really
"acting" on a request. For WPAD, the above proposes to reply
to the DHCPINFORM request on option 252 based on the
NWAM network proxy info. So the proposal is about
participating in the two service discovery methods mentioned
to enable different apps to work "magically." For example,
we can ship firefox with the default proxy configuration
set to auto-detect. And firefox will just work with NWAM
out of the box.
> done by WPAD aware apps. The WPAD aware app will take this
> info. If there is proxy info available from the server(s) and
> there is also a NWAM proxy setting, NWAM can still "fake" a
> DHCP server reply if the setting is supposed to override the
> proxy info from the server(s).
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
