Re: [Netconf] WGLC on netconf-event-notifications-13

["Eric Voit (evoit)" <[e-mail]>]

> On Thu, Oct 11, 2018 at 04:41:39PM +0000, Eric Voit (evoit) wrote:
> > > From: Juergen Schoenwaelder, October 11, 2018 12:33 PM
> > >
> > > On Thu, Oct 11, 2018 at 04:13:15PM +0000, Eric Voit (evoit) wrote:
> > > > Hi Juergen,
> > > >
> > > > > From: Juergen Schoenwaelder, October 11, 2018 3:41 AM
> > > > >
> > > > > On Thu, Oct 11, 2018 at 09:25:39AM +0200, Martin Bjorklund wrote:
> > > > > >
> > > > > > > > But this illustrates a problem with SN; the "transport"
> > > > > > > > leaf is mandatory if the feature "configured" is
> > > > > > > > supported.  The problem is that just b/c a server supports the
> "configured"
> > > > > > > > feature, it doesn't mean that there is an identity defined
> > > > > > > > for all transports; e.g., there is no identity defined for
> > > > > > > > NETCONF.  So the leaf "transport" should probably not be
> mandatory.
> > > > > > >
> > > > > > > Made optional within the SN grouping "subscription-policy",
> > > > > > > and tweaked the definition as follows:
> > > > > > >
> > > > > > >     leaf transport {
> > > > > > >       if-feature "configured";
> > > > > > >       type transport;
> > > > > > >       description
> > > > > > >         "For a configured subscription, this leaf specifies the
> > > > > > >         transport used to deliver messages destined to all receivers
> > > > > > >         of that subscription.";
> > > > > > >     }
> > > > >
> > > > > The fix does not seem to address the question nor do I
> > > > > understand how a configured unspecified transport will work.
> > > >
> > > > An unspecified configured transport cannot work without leaf
> > > > transport
> > > populated.  That is why there is a refinement to the definition for
> > > the Data Node which appends to the description above: "This object
> > > is mandatory  for subscriptions in the configuration datastore."
> > > >
> > >
> > > The original statement was "there is no identity defined for NETCONF".
> > > So is there a defined transport identity for NETCONF or not?
> >
> > There is not.
> >
> > This identity was extracted from a previous version of SN to a new model in
> NETCONF-Notif earlier in the year.  When we subsequently removed
> configured subscription support from the NETCONF-Notif draft, we removed
> the identity.
> >
> 
> So should there be one? Or how do things work with NETCONF? (Seems we go
> in circles here instead of addressing the question...)

There should not be a NETCONF identity until there is configured subscription support for NETCONF.  

Previous reviewers have been very vigilant in ensuring each transport identity not appear until supported by a transport document.   This is why the NETCONF transport identity was extracted from SN earlier this year.

Eric

 
> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <https://www.jacobs-university.de/>