W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1997

RE: ID: Proxy autoconfig

From: Yaron Goland <yarong@microsoft.com>
Date: Sun, 6 Apr 1997 01:13:29 -0800
Message-Id: <11352BDEEB92CF119F3F00805F14F4850277F013@RED-44-MSG.dns.microsoft.com>
To: Stuart Kwan <skwan@microsoft.com>, "'nemo/Joel N. Weber II'" <devnull@gnu.ai.mit.edu>
Cc: http-wg@cuckoo.hpl.hp.com, josh@netscape.com
Having the info in two places isn't necessarily a bad thing. Each
solution has its place.

Oh the DHCP end of things I am looking at the URL as not just a place to
get proxy configuration but as a place to get any and all configuration
information I might need. It is the "entry" point from where I can start
making requests for all sorts of interesting things.

			Yaron

> -----Original Message-----
> From:	Stuart Kwan 
> Sent:	Friday, March 28, 1997 3:12 PM
> To:	'nemo/Joel N. Weber II'
> Cc:	http-wg@cuckoo.hpl.hp.com; josh@netscape.com
> Subject:	RE: ID:  Proxy autoconfig
> 
> 	   2)  Using DNS will not work for mobile clients.  For example,
> consider a
> 	   laptop named SKWAN01.INTRA.MICROSOFT.COM.  While plugged into
> the
> 	   Microsoft corporate net, it queries for and receives the TXT
> RR:
> 
> 		   w3-ns-pac.intra.microsoft.com. IN TXT
> 	   "service:yp-http://proxy1.intra.microsoft.com:8080/proxy.ins"
> 
> 	   I unplug my laptop and take it on a visit to Netscape.  When
> I plug into
> 	   the Netscape corporate network, I query for the TXT RR per
> above and the
> 	   query fails.  At this point, I have no way of finding the
> proxy servers
> 	   for that network, and automatic configuration fails.
> 
> 	I don't really follow this logic.
> 
> 	When you visit Netscape, I assume you'll get a different IP
> address.
> 	I also assume that means you'll have a different hostname--maybe
> 	visitor01.intra.netscape.com
> 
> Pardon that.  I was assuming dynamic DNS.  Future Microsoft clients
> (and
> DNS servers) will be dynamic-DNS enabled.  When they receive a new IP
> address, they will register that address under their name.
> 
> However, you make a good point.  When I plug my laptop in at Netscape,
> I
> need a new IP addr.  Either 1) they are running DHCP and this
> discussion
> is moot, the client can receive the URL via DHCP, or 2) I have dig
> into
> my laptop and enter a new IP address by hand - in which case a) the
> client could do a reverse lookup to determine it's name, or b) I could
> hand configure the new name, or c) I could hand enter the proxy
> information.  After all, some sysadmin is going to have to give me an
> IP
> (and DNS IPs, and gateways, etc etc), I might as well be given the
> proxy
> server info too.
> 
> I am also not opposed to storing this information in two places.  I am
> only concerned that we solve the automatic configuration problem.
> 
> Cheers,
> - Stuart Kwan
> Microsoft Corp.
Received on Sunday, 6 April 1997 01:16:21 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:34 EDT