[can't figure out what to quote - so for context we're talking about
2.5 - (network) transparent proxy in the taxonomy draft.. specifically
"The use of this type of proxy is transparent to both user and client"]
backing away a few feet from the paragraph, I wonder if we can just
drop the sentence. The basic meaning of it is already captured in
traffic redirection and a NTP is "a proxy that receives traffic as a
result of network traffic redirection".. so I think the basics are
really covered. but if that won't fly..
Problems with the current definition
1] recursive use of transparent
2] lack of agreement on what 'transparent' might mean (undetectable
vs configuration-free)
3] joe maintains that it's not necessarily undetectable or
configuration free to a user (who may need to specify routes
through it).. the value of doing this instead of just telling the
application to use a proxy totally escapes me though, unless you've
got a client that just doesn't know how to use a proxy.
4] I maintain it's not undetectable to a client (for various
applicaiton level protocol reasons previously detailed)
which leaves us with configuration-free for clients.
:: No configuration - there are cases where an NTP is deployed to
:: avoid rewriting code at the proxy or client, but not to avoid
:: configuration.
client, I concur.. but proxy? At a minimum an origin server style
request needs to be translated into a proxy style request..
In any event I had suggested "The use of this type of proxy requires
no configuration either by the user or the client." How about "The use
of this type of proxy requires no configuration by the client." Where
'client' is defined in 2.1 as "a program that establishes connections
for the purposes of sending requests." It doesn't say anything about
the rest of any sytem elements that may share a platform with the
client.
-P
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:27 MST