--On søndag, september 11, 2005 17:57:29 -0400 Henning Schulzrinne
<hgs(_at_)cs(_dot_)columbia(_dot_)edu> wrote:
- Generalization of point solutions. Even major new
functionality often starts out as the need of a specialized
group of users. If you always do only what is needed
right now and don't think ahead -- you will get bloat
and an architecture that does not work well.
The converse also happens: The assumption that specialized protocols are
needed for every new application. The world outside the IETF bubble is
starting to largely ignore this for new applications, yielding SOAP and
OASIS.
In some (many?) cases, I'd actually argue that they ARE desiging new
protocols, but build them on quite complex substrates.
The management protocols that the Storage Networking people are building on
top of Web Services using CIM data models still have to face the same
issues as a CLI interface on top of Telnet, or a MIB interface on SNMP -
are the right objects defined? are the operations correctly identified? are
access controls at the right level of granularity? are the entities
participating in the process correctly identified?
Once these things are "right" (or at least agreed upon), getting the bits
on the wire to work is relatively easy (in comparision).
that said - sometimes the problems DO fit the tools.
Harald
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf