Re: Where we stand/SNMPv3

> There is something else that people may want to understand is why
> the IETF is moving towards XML and leaving SNMP?Is this another protocol
> clone war?

There is no organized move within the IETF towards XML -
some individual working groups are using XML-encoding for
their protocols, but there's no conspiracy here.  Possibly
the most memorable quote from IETF 54 was Jeff Schilling's
comment in the saag meeting that "XML is this decade's
ASN.1."  

> Our problem is that the evaluated protocols meet the job,
> every protocol has its own way of doing the job. The main
> differences that we can list are relevant to performance
> (they have more or less the same amount of overhead) this
> what makes people really about especially that MIDCOM has
> real time applications.

We don't even know if there really are meaningful
differences between the protocols when it comes to
performance, so I'm not sure that there's progress to be
made here.  I haven't seen calls to eliminate protocols that
use TCP or SCTP for transport on the basis of performance/
scalability.

The discussion about protocol selection is over.  The
question now is whether or not to go ahead with an SNMP-
based midcom protocol.

Melinda