[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new to cdn internetworking
When running everyone's through forward proxies (which does every business
via a firewall and some major ISPs), the proxy becomes a layer7 network
device that can do pretty much anything with content requests.
On Tue, 13 Nov 2001, Jasdip Singh wrote:
> Hi.
>
> http://www.ietf.org/internet-drafts/draft-singh-uri-localization-00.txt proposes
> one such approach for restricted contextual resolution of URIs by geography,
> language, and category. It proposes using NAPTR DNS RR (providing a simple
> context specification mechanism through regular expressions) for structured
> identifiers like URLs due to ability to derive a domain name from a URL and
> pervasive, proven nature of DNS for storing such transformation information.
>
> Other directory service solutions for limited contextual resolution are being
> proposed like the Service Lookup System proposal which proposes using Common
> Name Resolution Protocol (CNRP) instead and would be very useful for unstructed
> identifiers like keywords. I believe, in the end, a hybrid solution involving
> various directory services and what they are best suited to resolve would
> emerge, further considering global deployment and deployment latency issues with
> each of these solutions. I have not yet seen much interest in my proposal. :)
>
> Jasdip
>
> Richard Wade wrote:
>
> > One of the problems with providing effective content routing is that you are
> > trying to bridge the gap between application-layer information and IP
> > routing infrastructure. I think many people would agree that a DNS race
> > solution is nicely application independent, but certainly has potential
> > limitations.
>
>
Eric Dean
President, Crystal Ball Inc.
W 703-322-8000
F 703-322-8010
M 703-597-6921