[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposed Edits to Notification Draft
Sharon Chisholm wrote:
hi
I have a clarifying question on one of the editing instructions. I had
interpreted the following to be decoupled from the subscriptionId or not
subscriptionId discussion which is listed in the issues for discussion
section. I had interpreted this to simply be that Andy is saying the
correct way to return the subscription Id is with <ok> and not <data>.
On re-read, that sounds a bit off. What is the correct way to return a
subscription ID?
I think the WG already decided we do not need or want
the subscriptionId parameter at all.
The <ok> rpc-reply should be used because there is no data
that needs to be returned. You do not return any data with <ok>.
The WG did not decide to keep the subscriptionId "in case we want
it someday in the future", as you have interpreted it.
Andy
> 1 5. In section 2.1.1, in create subscription (source Andy)
> a. This should be <ok> instead of a <data> element containing
the subscription ID. The WG decided there is only one stream active
per session. That means there is no need for a subscription ID in the
document.
--
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/>