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

about channels



The netconf draft define 3 channels:
-Management channel
-Operation Channel
-Notification Channel

Now, reading the draft "over SSH" the "management channel" can not be
supported and only define a "single channel" mechanism.

Since basically the definition on what is an actual channels (i.e. from
a developer point of view) is an open issue that is defined based on the
protocol it is encapsulated (i.e. ssh, tls, beep, etc), why not go with
a more specific definition for these and on protocols like ssh, TLS,
telnet a channel is just another parallel stream. Something just like
what happen with ftp and ftp-data ports.

Personally I like the "over BEEP" definition since it provides this
mechanism over a single stream but for the others the same management,
operation and notification channels functionalities should be there.


-William
-- 
William Caban <william@hpcf.upr.edu>
High Performance Computing facility
University of Puerto Rico


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