[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FW: I-D ACTION:draft-chisholm-netconf-event-00.txt
On Tue, Jul 12, 2005 at 09:57:00PM -0400, Sharon Chisholm wrote:
> Here's the actual draft. This is a proposed solution to the need to do
> asynchronous messaging in netconf. Andy suggested it would be good to
> understand what the requirements in this space are.
>
> Here are some big bullet items
>
> 1. MUST support different types of events
> 1.1 Large and Small messages
> 1.2 Different types of information
> 2. Client (manager) MUST be able to specify which events are of interest
> 3. Client (manager) MUST be able to stop receiving events
> 4. Client (manger) MUST be able to process events as they come in
Not sure what this really means.
> 5. Server (network element) should not be blocked after sending out an
> event
I guess I know what you mean but the bullet point itself does not
really convey whay I guess you wanted to say.
> 6. Events MUST work well for SSH
> 7. Events MUST work for Beep and SOAP
You probably mean SOAP/HTTP. The difference between "MUST work" and
"MUST work well" also remains somewhat unclear.
[And looking at the ID, I am not really clear how the SOAP/HTTP transport
mapping (I continue to dislike the term "application protocol" in the
NETCONF documents) is supposed to works - or my understanding of HTTP
1.1 chunked transfers is wrong. But now I am discussing the ID and not
the bullet points so this remark is off topic for this thread.]
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
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/>