[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NETCONF Notifications: Consensus Points


On 27-Nov-05, at 9:42 AM, Andy Bierman wrote:


Ted Goddard wrote:

Notifications for NETCONF over SOAP/HTTP could be implemented
using:

    1. Separate HTTP connections for NETCONF management and
       NETCONF notifications channels




You mean one session in each direction?
Both NC peers have to implement HTTP Server and Client SW
to have notifications in this case.


The agent on the managed device would still be the
HTTP server, but two normal HTTP connections would
be opened to it from the NMS.  Two connections
are necessary because pipelining a notification
request and a management request on the same connection
could cause the management request to be blocked
behind the notification.


    2. HTTP response to a notification request delayed until
       notifications are available




Not sure what you mean here.
I think you mean the NMS continuously polls for notifications,
but the agent holds each response until there is a notification
to send (in order to minimize the polling overhead).


Exactly; the agent does not respond to the request
for notifications until notifications are available.
Then if the NMS wants more, it asks again.  It's
not very elegant, but it does work within the confines
of HTTP.


Won't this cause the connection to time out in the client,
and perhaps HTTP caches in between the manager and agent?
(I guess this can be avoided by using a different port number than 80.) 

If there are caches or other factors causing timeouts,
then I would suggest that the NMS should keep polling
until the agent returns an error.  But HTTP on the
NMS could be configured to have a very long timeout,
so the problem shouldn't really arise.

Ted.




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






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





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