Although I appreciate the discussions on the
performance issues of XML vs SOAP/WSDL,
and also the discussions on XML vs SNMP,
the one thing that still bothers me most is:
I am not particularly enthused by seeing suggestions to
replace current protocol X (no matter which one it is)
with new protocol Y (not matter which one it is) if we
do not at the same time show how the new protocol will
be better at addressing real operator requirements.
I do not want to find us a few years from now with the
situation aka:
operators tell us that they are not using new protocol Y
because it does not address the real problems they face
and because vendors have not properly implemented it
and because it .... whatever
So, how does XML (or any new technology for that matter)
help us address the Operator Requirements.
I understand they are not yet very well specified,
but this is at least an initial list that I have
seen mentioned and that we need to addres:
- dump/save configuration
- load/restore configuration
- activate a new configuration at time X or at reboot
- rollback a configuration
- network level configuration, as in the following points
- mutli-device transactions (e.g. activate a specific
configuration at mutliple devices in sync
- rollback at multiple devices in sync
- who can do what on which devices, as in the
following points
- what are the identities of who can do what
- how can they be grouped
- how do we do access control fo such groups
- transport security
- how is the transport properly secured
Randy Bush (or other operators), pls add if my list is
not correct and/or incomplete
Thanks,
Bert
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>