Hard to imagine not being confused, but I don't think OPES
needs total control of ICAP, but OPES does need a protocol
that has been through the normal IETF standards process.
An informational RFC doesn't meet its needs.
Hilarie
Ian Cooper <icooper(_at_)equinix(_dot_)com> 06/28/01 12:24PM >>>
I' confused. In trying to respond to another message I finding myself
asking why OPES seems to need total control of iCAP.
If it's published as an Informational RFC (with the current nits fixed)
what problem does that actually present?
Is it the job of a proposed working group to worry about the interaction of
standards bodies on a protocol that they themselves say they may choose not
to use? (And that if they do, may end up being something so different that
it's not the iCAP that's been examined by those other standards bodies.)