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

Qiufang - thank you for volunteering to be shepherd!  👍

K.

> On Jun 17, 2022, at 6:08 AM, Rob Wilton (rwilton) <rwilton@cisco.com> wrote:
> 
> Hi Kent, Mahesh,
>  
> Apologies for the delay, thank you for addressing the comments.  I can declare that the WGLC on this document is complete (as a reminder to the WG, both Kent and Mahesh reclused themselves because they are authors of this draft).
>  
> Qiufang Ma will kindly be acting as doc shepherd for this document.
>  
> I would like to thank the WG for their reviews and comments that have helped improve this document.
>  
> Regards,
> Rob
>  
>  
> From: netconf <netconf-bounces@ietf.org> On Behalf Of Mahesh Jethanandani
> Sent: 25 October 2021 04:30
> To: netconf@ietf.org
> Subject: Re: [netconf] I-D Action: draft-ietf-netconf-https-notif-09.txt
>  
> This version of the document addresses the remaining comments or questions that were raised during LC, and makes some editorial changes to better explain how the target resources by the receiver are to be used. More importantly, it retains the receiver capability fetching mechanism that was discussed and agreed upon in the last WG meeting.
>  
> The authors believe that this document is now ready for publication.
>  
> Thanks.
> 
> 
> On Oct 24, 2021, at 1:35 PM, internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> 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 YANG Notifications
>        Authors         : Mahesh Jethanandani
>                          Kent Watsen
>                 Filename        : draft-ietf-netconf-https-notif-09.txt
>                 Pages           : 27
>                 Date            : 2021-10-24
> 
> Abstract:
>   This document defines a protocol for sending notifications over
>   HTTPS.  YANG modules for configuring publishers are also defined.
>   Examples are provided illustrating how to configure various
>   publishers.
> 
>   This document requires that the publisher is a "server" (e.g., a
>   NETCONF or RESTCONF server), but does not assume that the receiver is
>   a server.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-https-notif/ <https://datatracker.ietf.org/doc/draft-ietf-netconf-https-notif/>
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-netconf-https-notif-09 <https://datatracker.ietf.org/doc/html/draft-ietf-netconf-https-notif-09>
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-https-notif-09 <https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-https-notif-09>
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/ <ftp://ftp.ietf.org/internet-drafts/>
> 
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org <mailto:netconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>
>  
> Mahesh Jethanandani
> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>