RE: Netconf over SOAP

["Mi-Jung Choi" <mjchoi@postech.ac.kr>]

>>This mechanism for notifications over HTTP has been discussed, but
>>was not included in the current draft due to the complexity of
>>initiating the reverse connection from the agent.  
>>What is your proposal?
> 
> => What complexity? Perhaps can you give us some details?
> If the agent has the HTTP client, the agent can easily connect to the
> HTTP server in the manager. 
> The agent can send an asynchronous notification message to the manager
> through the HTTP client.

Ok, that's fine.  Now turn it around where the manager connects to the 
agent.

=> As you know, the agent includes an HTTP server and the manager
includes
an HTTP client. The HTTP client in the manager connects to the HTTP
server
in the agent. Using this mechanism, the manager can request operations
such
as get-config, edit-config, etc.
For an asynchronous message from the agent, the agent also includes an
HTTP 
client and the manager includes an HTTP server. The agent can connect to
the manager using the HTTP client.
That is, the agent includes both an HTTP server and an HTTP client.
Eliot




--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>