Re: [Netconf] YangPush now

["Tim Jenkins (timjenki)" <[e-mail]>]

Please see embedded, with prefix [Tim]. Note some editing of the original to separate the questions.

-- 
Cisco Systems Canada Co.
2000 Innovation Drive
Kanata, ON, Canada, K2K 3E8
Preferences <http://www.cisco.com/offer/subscribe/?sid=000478326>
Unsubscribe <http://www.cisco.com/offer/unsubscribe/?sid=000478327>
Privacy <http://www.cisco.com/web/siteassets/legal/privacy.html>



On 2018-07-17, 1:21 PM, "Juergen Schoenwaelder" <[e-mail]> wrote:

    I see several pieces but I do not see how the pieces give me a
    workable solution nor do I see how such a solution gives me
    interoperability.

[Tim] Even with your questions below, it's still not clear to me what would be missing. 
    
    If I configure a subscription, how does the flow of notifications work
    over NC and RC?

[Tim] NETCONF message flows are described in draft-ietf-netconf-subscribed-notifications, Appendix A.3.   RESTCONF is not in WGLC yet, but can be seen at draft-ietf-netconf-restconf-notif, Appendix B.2

    How do I configure where the connection goes?

[Tim] Since we don't implement netconf-server.yang, we do vendor specific stuff to link each receiver to our local call home/dial-out configuration.  There are lots of moving parts here, and we don't expect interoperability for quite a while.  This lack of interoperability is not a result of these subscription drafts though, so waiting for or making a model dependency to pending IETF work in this space will only make things more confusing and add further unnecessary delay to the process.

    What is
    the RC resource that provides me the notification stream?

[Tim] Current NETCONF implementation doesn't need this.  RESTCONF isn't used for configured subscriptions.

   How will
    all of this work if the endpoints in the future want to negotiate
    different encodings?

[Tim] Configured subscriptions aren't negotiable. However, negotiation is defined in the drafts for dynamic subscriptions. I think you can find more on that using a search of the text "configurable-encoding" within the YANG model of draft-ietf-netconf-subscribed-notifications.
    
    Since you said you implemented this: What exactly did you implement,
    what did not leave out, what did have to add to make it work?

[Tim] As configured subscriptions are not available in a public release at this point, I am not ready to give a full answer.
For dynamic subscriptions, you can see what is currently available at <https://github.com/YangModels/yang/tree/master/vendor/cisco/xe/1681>. Search on "push", for example <https://github.com/YangModels/yang/blob/master/vendor/cisco/xe/1681/ietf-yang-push.yang>. We have been deferring upgrading our IETF model version until this work is released from WGLC.  We don't want to make our users iterate model versions when the functional difference is quite low.
    
    /js
    
    On Tue, Jul 17, 2018 at 01:20:55PM +0000, Tim Jenkins (timjenki) wrote:
    > Juergen,
    > 
    > To flip this around, I don’t understand where the difficulties are.
    > 
    > But here’s what I see:
    > 
    >   1.  The format of the update notifications should be the same whether the subscription is dynamic or configured for a given transport and encoding. I believe we have that.
    >   2.  There are some differences in out of band notifications when I last read the drafts in details; these were explained by the different connection setup contexts. But this is otherwise unrelated to configured subscriptions.
    >   3.  Since the transport specific details are now separate from the base line drafts, it allows transport specific behaviour to decide how the connections (for configured subscriptions) are to be setup. We have usable variations of “call home” or “dial out” or whatever you want to call it for the cases we need. Admittedly, we do have to provide augmentations for some of the protocols, but then, that’s the intent of the design.
    > 
    > BTW, my comment below was sent last week. I have no idea how/why it arrived on the list after the IETF meeting yesterday.
    > 
    > Tim
    > 
    > --
    > Cisco Systems Canada Co.
    > 2000 Innovation Drive
    > Kanata, ON, Canada, K2K 3E8
    > Preferences <http://www.cisco.com/offer/subscribe/?sid=000478326>
    > Unsubscribe <http://www.cisco.com/offer/unsubscribe/?sid=000478327>
    > Privacy <http://www.cisco.com/web/siteassets/legal/privacy.html>
    > 
    > From: Juergen Schoenwaelder <[e-mail]>
    > Reply-To: Juergen Schoenwaelder <[e-mail]>
    > Date: Tuesday, July 17, 2018 at 1:50 AM
    > To: "Tim Jenkins (timjenki)" <[e-mail]>
    > Cc: "[e-mail]" <[e-mail]>
    > Subject: Re: [Netconf] YangPush now
    > 
    > I do not think that configured subscriptions have been fully worked
    > out. Nor do I see how I configure something that actually works.
    > Since you have implemented this, perhaps you can help me to understand
    > how all this actually works with the text in the current IDs.
    > 
    > /js
    > 
    > On Mon, Jul 16, 2018 at 11:10:52PM +0000, Tim Jenkins (timjenki) wrote:
    > Hi,
    > As an implementor of the drafts, I suggest enough already: we've been going down this path for quite some time.
    > Please publish both sets (dynamic and configured, and SN and YP) together.
    > Thanks,
    > Tim
    > > Hi,
    > >
    > > It might be useful (at least to me), if the draft authors could explicitly indicate what their preference is, and also which of the choices below they think would lead to the work completing most quickly.
    > >
    > > Thanks,
    > > Rob
    > >
    > >
    > > On 12/07/2018 19:48, Kent Watsen wrote:
    > > I would like to strongly +1 retaining the configured subscriptions
    > > (not necessarily in the Push draft itself for the sake of expediting
    > > WGLC or
    > > modularity)
    > > Ah, so here's another hum question: with or without yang push.
    > >
    > > hums now are:
    > >
    > >  1. dynamic subscriptions ~ configured subscriptions
    > >   a. dynamic first, then configured (published sequentially)
    > >  b. dynamic and configure together (published in parallel)
    > >
    > >   2. subscribed-notifications ~ yang-push
    > >     a. SN first, then YP  (published sequentially)
    > >     b. SN and YP together (published in parallel)
    > >
    > > Eric/Alex: please include a slide with this somewhere in your preso.
    > >
    > > Thanks,
    > > Kent // chair
    > _______________________________________________
    > Netconf mailing list
    > mailto:[e-mail]
    > https://www.ietf.org/mailman/listinfo/netconf
    > --
    > Cisco Systems Canada Co.
    > 2000 Innovation Drive
    > Kanata, ON, Canada, K2K 3E8
    > Preferences <http://www.cisco.com/offer/subscribe/?sid=000478326>
    > Unsubscribe <http://www.cisco.com/offer/unsubscribe/?sid=000478327>
    > Privacy <http://www.cisco.com/web/siteassets/legal/privacy.html>
    > _______________________________________________
    > Netconf mailing list
    > [e-mail]<mailto:[e-mail]>
    > https://www.ietf.org/mailman/listinfo/netconf
    > 
    > --
    > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
    > Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
    > Fax:   [phone]         <https://www.jacobs-university.de/>
    > 
    
    -- 
    Juergen Schoenwaelder           Jacobs University Bremen gGmbH
    Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
    Fax:   [phone]         <https://www.jacobs-university.de/>