Re: [netconf] I-D Action: draft-ietf-netconf-https-notif-04.txt

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

Hi Mahesh,

Thanks for updating the text.  One question, are you sure you need the
statement:

                 This example shows the flow assuming that	
 	   Subscribed Notifications is used and therefore a <subscription-

 	   started> notification is sent before sending the first
notification.	
 	   The example would be the same for when Subscribed Notification is
not	
 	   used by removing the first POST message for
<subscription-started>.

I am guessing that you mean "Subscription State Change Notifications" here
rather than "Subscribed Notifications".   As RFC-8639 Subscription State
Change Notifications are mandatory, is this statement necessary here?

Perhaps you could add a non-normative appendix which shows the implications
of dropping specific Subscription State Change Notifications If an
implementation desires this simplification?  E.g., issues with supporting
replay, issues with understanding what subscription is sending traffic, no
ability to see if the terms of the subscription changed, no awareness of
subscription suspend, no way to signal the end/termination of a
subscription, etc.  

All of these might be absolutely ok in an implementation, but it might be
worth addressing in aggregate in a place which is outside the bounds of the
normative text.

Eric


> -----Original Message-----
> From: netconf <[e-mail]> On Behalf Of Mahesh
> Jethanandani
> Sent: Monday, July 27, 2020 11:46 AM
> To: [e-mail]
> Subject: Re: [netconf] I-D Action: draft-ietf-netconf-https-notif-04.txt
> 
> This version of the document addresses comments received from Eric, and
> updates to the ietf-truststore module.
> 
> > On Jul 27, 2020, at 8:39 AM, [e-mail] wrote:
> >
> >
> > 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           : An HTTPS-based Transport for Configured
Subscriptions
> >        Authors         : Mahesh Jethanandani
> >                          Kent Watsen
> > 	Filename        : draft-ietf-netconf-https-notif-04.txt
> > 	Pages           : 27
> > 	Date            : 2020-07-27
> >
> > Abstract:
> >   This document defines a YANG data module for configuring HTTPS based
> >   configured subscription, as defined in RFC 8639.  The use of HTTPS
> >   maximizes transport-level interoperability, while allowing for
> >   encoding selection from text, e.g.  XML or JSON, to binary.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-netconf-https-notif/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-netconf-https-notif-04
> > https://datatracker.ietf.org/doc/html/draft-ietf-netconf-https-notif-0
> > 4
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-https-notif-04
> >
> >
> > 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:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> >
> > _______________________________________________
> > netconf mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/netconf
> 
> Mahesh Jethanandani (as co-author)
> [e-mail]
> 
> 
> 
> _______________________________________________
> netconf mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netconf