Re: [Netconf] LC on subscribed-notifications-10

[Qin Wu <[e-mail]>]

I have two comments on subscribed-notifications-10:
1.Why protocol parameter is defined in RPC while it is not defined in notification?
Is protocol parameter can be extended to support other transport protocol? Is there any dependency between protocol and DSCP?
2.Section 2.7.6 said
"   The tree structure of "subscription-completed" is almost identical to
   "subscription-resumed", with only the name of the notification
   changing.
"
Is there any key difference between "subscription-completed" and "subscription-resumed", it looks replay-completed is used to push
All event record before stop time expires, would it be great to clarify this in section 2.7.6?

-Qin
> -----Original Message-----
> From: Netconf [mailto:[e-mail]] On Behalf Of Kent 
> Watsen
> Sent: Wednesday, February 28, 2018 6:09 PM
> To: [e-mail]
> Subject: [Netconf] LC on subscribed-notifications-10
> 
> 
> WG,
> 
> The authors of netconf-event-notifications have indicated privately 
> that they believe this document is now ready for Last Call.
> 
> This starts a 2.5-week Last Call on
> draft-ietf-netconf-subscribed-notifications-10
> [1] The LC will end on March 17, or when active threads peter out.
> 
> Please send your comments on this thread. Reviews of the document, and 
> statement of support, are particularly helpful to the authors.  If you 
> have concerns about the document, please state those too.
> 
> Authors please indicate if you are aware of any IPR on the document.
> 
> 
> [1]
> https://tools.ietf.org/html/draft-ietf-netconf-subscribed-notification
> s-10
> 
> 
> Kent & Mahesh
> 
> 
> 
> 
> _______________________________________________
> Netconf mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netconf

_______________________________________________
Netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf
_______________________________________________
Netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf