egads....

["Mike O'Dell" <mo@ccr.org>]

we are already swimming in RPC protocols encoded in XML

any proposal based on doing RPC that way should NOT contribute
yet another encoding!!!   in fact, it isn't clear to me why such a
proposal should hinge on the specifics of the RPC mechanism much
at all.  the data to be moved as arguments to the RPC calls are the
central issue, so define *that* in an XML Schema(s) and get on with it.

after a cursory read, i believe this draft focusses on the RPC mechanics
since the actual details of configuration data are so completely
out-of-scope (if not down-right impossible).

given that, i would suggest the author adopt an existing RPC model
and then explain how to use it as suggested in the current draft.

	-mo




--
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/>