Sorry for being abrupt.
Unfortunately, the use of "OPES" has become VERY overloaded - and I am trying
to shun that mis-use.
Clearly, any requirement for a proxy service by the IETF is a requirement
for a proxy
service regardless of name of the architecture.
The goal of OPES is to define an architecture where the proxy services have
unified clean interfaces for protocols and APIs to build these services.
NOW, this idea has come along at a time where there has been a big
uncontrolled mess in Internet devices and services and providing an
authorized environment for these services is LONG overdue. So OPES is
taking on the issues surrounding sorting out this long overdue mess. OPES
alone may not be able to charter all of these. Maybe we need an OPES-AAA
sub-group (or something like that) to focus on the AAA aspects as these
goals become clear from all the requirements.
Correct me if have mis-represented things here....
PM 11/19/2001, Leslie Daigle wrote:
Howdy,
Um, yeah.
There is an inherent issue of what should be an Internet
standard, where the IETF spends cycles on making stuff work. My
cut on that is that it should be for things that can be built
out more generally. There's plenty of stuff you can do in your
own software, and maybe many companies will do the same thing.
But it's not clear that all of those things should be _Internet_
standards.
If you have a non-consented model where traffic is shunted &
logged, then the endpoints don't know where their traffic is
going. It makes it harder to predict network issues. It also
becomes harder to build more pieces in front or behind.
These are only my own thoughts to address why it _might_ be
reasonable, and not a double standard.
"Condry, Michael W." wrote:
> Humm. A proxy that just does a service is ok to do but a proxy that
> supports a standardized IETF approved set of protocols has to live by
> different rules?
Leslie.
--
-------------------------------------------------------------------
"An essential element of a successful journey
is recognizing when you have arrived."
-- ThinkingCat
Leslie Daigle
leslie(_at_)thinkingcat(_dot_)com
-------------------------------------------------------------------
Michael W. Condry
Director, Network Edge Technology