Faye Ly wrote:
There are two different models supported: where the NMS connects to the network element and where the element connects to the NMS. This allows for devices to connect on bootup to get managed, very similar to the COPS-PR model, as well as the traditional NMS model. Once a connection is established, the element is managed by the manager.1. The client/server model may be as clear as the sky to most of the people but I think it deserves a clarification. Where is the client and where is the server? In the past we use the manager and agent entity to model the management paradigm and if your draft chooses to use the client/server model (or not), please make it clear.
2. The goal of this draft is to provide a XML protocol that manages a network device? Specifically 'manages' means what? Many things are mentioned in the proposal such as 'manipulate, install, edit and delete configuration' and 'The protocol allows the device to expose a full, formal, API' ... Again without a management paradigm, this is all very confusing.
See above.
3. Is RPC chosen because it is well understood and has the advantage of specifying the operation as well as the data being manipulated by the operation? Probably needs some text to explain that.
Chosen to reduce hair in the network element. Eliot -- 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/>