thanks, I'll check.
I hope this is not a yap (yet another protocol)
regards
-RP
-----Original Message-----
From: Ian Cooper [mailto:icooper(_at_)equinix(_dot_)com]
Sent: Friday, August 10, 2001 2:43 AM
To: Penno, Reinaldo [SC9:T327:EXCH]; 'Michael W. Condry';
'ietf-openproxy(_at_)imc(_dot_)org'
Subject: RE: Charter re-wording
See the "IDD" work item for the WEBI working group.
At 02:11 8/10/2001 -0700, Reinaldo Penno wrote:
-----Original Message-----
From: Ian Cooper
[<mailto:icooper(_at_)equinix(_dot_)com>mailto:icooper(_at_)equinix(_dot_)com]
Sent: Friday, August 10, 2001 1:10 AM
To: Michael W. Condry; ietf-openproxy(_at_)imc(_dot_)org
Subject: Re: Charter re-wording
Web-based service engines are sometimes identified as "edge"
servers,
which form an application-level overlay network on top of an
IP network.
They are explicitly addressed at IP level and terminate
a transport
connection in a normal way. Thus, they do not interfere with the
end-to-end principle in RFC 1958.
This is a weak attempt at addressing the concerns over
"end-to-end", though
I agree it's very good to be explicit in identifying that the
OPES systems
are explicitly addressed.
caveat: I haven't read the full thread, so sorry this isn't
exactly what
is being addressd
So, how you propose to do that? Offer OPES services
explicitly addressing
them at the IP Layer. Are you talking about going back to
putting HTTP
Proxy IP address on our browsers? So, if I have several OPES
devices in my
network providing me diffrent services I would have to
configure my client
to use
HTTP: IP A
Video: IP B
Language Translation: IP C
Virus Scanning: IP D.
etc, etc
And if some of them fails should I "reroute" manually changing the
configuration or have more than one IP address?
regards,
Reinaldo Penno