Channels are a means of maintaining multiple communication streams
within a single session. In NETCONF, there are three types of streams:
management, operations, and notifications. Channels allow these different
message types to be multiplexed within the same session without the
need to interleave the messages in a way that preserves their
integrity (e.g. valid XML instance documents). NETCONF utilizes
channels to separate asynchronous messages (notifications or RPC
progress reports) from normal operations, as well as separate
high priority operations (RPC abort) from normal operations.
Andy
The working group has three choices:
Option A. Keep channels in the base document and require each mapping to support them.
Option B. Make channels optional.
Option C. Remove channels from the base protocol and allow their use
in the protocol bindings.
Which option do you prefer?
If you would like to read the entire set of documents, you will find them by going to the NETCONF working group charter page:
http://www.ietf.org/html.charters/netconf-charter.html
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/>
--
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/>