Re: comments on notification-07 draft

[Martin Bjorklund <mbj@tail-f.com>]

"Sharon Chisholm" <schishol@nortel.com> wrote:
>  Comments inline
> 
> -----Original Message-----
> From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On
> Behalf Of Martin Bjorklund
> Sent: Wednesday, May 16, 2007 5:28 AM
> To: netconf@ops.ietf.org
> Subject: comments on notification-07 draft
> 
> Hi,
> 
> Here are some comments on the latest draft.  Some comments are the same
> as before
> (http://ops.ietf.org/lists/netconf/netconf.2007/msg00035.html).
> 
> 
>   o  2.1.1 
> 
>      The missing-element's error-info is broken:
> 
>          Error-info: <startTime Description: An expected element is
>          missing.
> 
>      I think that you should define an error-app-tag for the second
>      error, i.e. replay asked for when it's not available.  
> <sharon>
> 
> I believe there were previously comments to not have special error
> messages. This was discussed in Prague too. It involves reving the base
> protocol I think.
> </sharon>

Ok.  So will you remove this text instead?   And just refer to the
'missing-element' and 'operation-failed' standard error codes?

>    o  3.4
> 
>      I've pointed out before that the 'stream' element makes no sense
>      within a named profile.  If you think it does, the text for
>      create-subscription must be modified to allow for this case.
> <sharon>
> I guess the problem is that stream has a minOccurs > 0 in the
> subscription. I think it does make sense to be able to save this in the
> named profile since it filters content.
> </sharon>

If you don't specify a stream in create-subscription, it defaults to
NETCONF.  So a stream in a named-profile doesn't make much sense.


>    o  3.6
>   
>      Why does this section talk about "multiple filters"?  In the
>      schema for 'create-subscription', the description for the
>      'filter' parameter says: 
> 
>          This is mutually exclusive with the named profile parameter.
> 
>      So when/how can multiple filters be specified?
> <sharon>
> It doesn't. It talks about multiple filter elements. This is the term
> used in the base protocol document. If it talks about multiple filters
> anywhere this is residue, but I believe this has been corrected
> everywhere now.
> </sharon>

Ok.


/martin

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