Re: [Netconf] I-D Action: draft-ietf-netconf-subscribed-notifications-14.txt

> From: Kent Watsen, July 5, 2018 12:23 PM
> 
> Looking at the diffs I see:
> 
>      Note that each individual receiver is identifiable by
>      its "name".  This "name" plus the "transport" are used by a
>      publisher implementation to a parameters needed to establish and
>      maintain a network connection using that transport.
> 
> I know that you worked this out with Martin, but I think that for configured
> subscriptions (and that's all we're talking about here, right?), a leafref to the
> actual transport instance (e.g., /restconf-server/call-home/restconf-client)
> would be more exact.

Yes, just configured subscriptions.  As some transports might not want/need call home, adding the leafref should be defined in each transport draft.  

So how about text which says: "Note that each individual receiver is identifiable by its "name".  Via this "name", publisher transport parameters can be referenced in order to establish and maintain a transport connection with a receiver.  This transport specific reference can come in several forms, including the augmentation of leafrefs to an actual transport instance.  Such augmentations would be defined in transport specific specifications building upon this document."

Eric

> Kent
> 
> 
> 
> ===== original message =====
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network Configuration WG of the IETF.
> 
>         Title           : Customized Subscriptions to a Publisher's Event Streams
>         Authors         : Eric Voit
>                           Alexander Clemm
>                           Alberto Gonzalez Prieto
>                           Einar Nilsen-Nygaard
>                           Ambika Prasad Tripathy
> 	Filename        : draft-ietf-netconf-subscribed-notifications-14.txt
> 	Pages           : 74
> 	Date            : 2018-07-02
> 
> Abstract:
>    This document defines a YANG data model and associated mechanisms
>    enabling subscriber-specific subscriptions to a publisher's event
>    streams.  Applying these elements allows a subscriber to request for
>    and receive a continuous, custom feed of publisher generated
>    information.
> 
> 
> The IETF datatracker status page for this draft is:
> <mangled-url-snipped/>
> 
> There are also htmlized versions available at:
> <mangled-url-snipped/>
> 
> A diff from the previous version is available at:
> <mangled-url-snipped/>
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> <mangled-url-snipped/>
> 
> 
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf