[9504] in www-talk@info.cern.ch
Re: server redirects by client domain
daemon@ATHENA.MIT.EDU (Larry Masinter)
Sat Dec 23 00:50:14 1995
To: mgodsey@microsoft.com
Cc: www-talk@w3.org
In-Reply-To: Michael Godsey's message of Wed, 20 Dec 1995 03:31:23 -0800 <199512201935.LAA18869@imail1.microsoft.com>
From: Larry Masinter <masinter@parc.xerox.com>
Date: Fri, 22 Dec 1995 21:42:48 PST
Resent-From: www-talk@w3.org
There are at least three proposals floating to use 'DNS' to change how
references work:
a) use DNS for finding URN resolution services
(cf. various draft-ietf-uri-urn-* proposals).
Among other things, URN resolution services would help you find mirror
sites and replicas of the 'same' resource.
b) use DNS to indicate HTTP-NG vs HTTP support.
Simon Spero mentioned this in his talk describing HTTP-NG, that DNS
records might indicate the use of a completely different protocol for
http://foo.com/path
c) use DNS for simple host replication/round robin to indicate
multiple sites at different geographic (network topology) locations.
Whatever you think of these individually, doing them all with separate
DNS entries seems like a bad idea.
