Thank you Joe for the reminder. This version incorporates YANGDOCTORS review comments as well as some other comments we've received offlist, the main updates are following:
* Define "frequency" and "interval" terms * Features, grouping and parameters renaming for, e.g., ease of understanding: o Rename "basic-recurrence-supported" and "icalendar-recurrence-supported" features to "basic-recurrence" and "icalendar-recurrence" o Rename "recurrence" grouping to "recurrence-basic" o Rename "utc-start-time" parameter to "start-time-utc" o Rename "date-time-start" parameter to "start-time" o Rename "recurrence-bound" choice to "recurrence-end" * Clarify that detection and resolution of schedule conflicts are beyond the scope of this document * Fix JSON examples of schedule representation in Appendix A so that they can be validated * Exemplify the difference between "max-allowed-end" and "validity" parameters inside "generic-schedule-params" grouping * Other editorial updates The diff is available at https://author-tools.ietf.org/iddiff?url2=draft-ietf-netmod-schedule-yang-03. The authors feel that there is nothing in particular that we would like to highlight and now we are not aware of any open issues. Thus this document is close to WGLC, pending any potential review and feedback from the WG(s). Best Regards, Qiufang From: Joe Clarke (jclarke) [mailto:[email protected]] Sent: Saturday, October 12, 2024 9:21 PM To: maqiufang (A) <[email protected]>; [email protected]; [email protected] Subject: Re: New Version Notification for draft-ietf-netmod-schedule-yang-03.txt Thanks, Quifang. Please include a summary of the changes and anything in particular you'd like feedback on. Joe From: maqiufang (A) <[email protected]<mailto:[email protected]>> Date: Friday, October 11, 2024 at 22:47 To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [OPSAWG]FW: New Version Notification for draft-ietf-netmod-schedule-yang-03.txt Forward this new version notification to keep TVR and OPSAWG up-to-dated. Any comments and suggestions are welcome. Best Regards, Qiufang //co-author -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Thursday, October 10, 2024 4:17 PM To: Daniel King <[email protected]<mailto:[email protected]>>; Mohamed Boucadair <[email protected]<mailto:[email protected]>>; Qin Wu <[email protected]<mailto:[email protected]>>; Qin Wu <[email protected]<mailto:[email protected]>>; maqiufang (A) <[email protected]<mailto:[email protected]>> Subject: New Version Notification for draft-ietf-netmod-schedule-yang-03.txt A new version of Internet-Draft draft-ietf-netmod-schedule-yang-03.txt has been successfully submitted by Mohamed Boucadair and posted to the IETF repository. Name: draft-ietf-netmod-schedule-yang Revision: 03 Title: A Common YANG Data Model for Scheduling Date: 2024-10-10 Group: netmod Pages: 64 URL: https://www.ietf.org/archive/id/draft-ietf-netmod-schedule-yang-03.txt Status: https://datatracker.ietf.org/doc/draft-ietf-netmod-schedule-yang/ HTML: https://www.ietf.org/archive/id/draft-ietf-netmod-schedule-yang-03.html HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-netmod-schedule-yang Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-netmod-schedule-yang-03 Abstract: This document defines a common schedule YANG module which is designed to be applicable for scheduling purposes such as event, policy, services, or resources based on date and time. For the sake of better modularity, the module includes a set of recurrence related groupings with varying granularity levels (i.e., from basic to advanced). The IETF Secretariat _______________________________________________ OPSAWG mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
