At 05:05 PM 17/04/00 -0600, Vernon Schryver wrote:
>Is that a sign of good things happening to the document?
>I've been hoping to see some activity in the WREC list about either
>hijacking--uh--redirecting proxy hazards documement or the document
>NECP Is something happening behind the scenes? If so, please forget
>I asked.
NECP is not within the scope of WREC's current charter. NECP is being
revised, however, and we can expect a new version within the next few weeks
or so.
With respect to interception proxies, I would very much like to see these
discussed further on WREC. Our issues document could probably do with wider
review than just WREC.
But one very common mis-conception I have noticed is about the point at
which redirection occurs. In my experience, the redirection takes place
only at either source or destination, or more specifically, at a point
which is under the same administrative control as the end-user or (e.g.)
the web server itself.
A lot of the recent discussion on the IETF list seemed to assume that this
happened "somewhere in the middle". I'm not saying this is not possible,
just that it is not happening today (to my knowledge). In the future, I
think that it will get more, not less difficult to do this too - e.g. when
traffic is already tagged / labelled it will be more difficult to intercept
in the middle of its path.
In the meantime, there are many other ways to redirect clients to the
closest proxy. One common way is to simply use the DNS to give a response
dependant on the client's source IP address (for either the proxy or the
destination web server); many corporates do this today already - Akamai
have built a whole business out of it.
John
---------------------------------------------------------------
Network Appliance Direct / Voicemail: +31 23 567 9615
Kruisweg 799 Fax: +31 23 567 9699
NL-2132 NG Hoofddorp Main Office: +31 23 567 9600
---------------------------------------------------------------
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:28 MST