Hi Kent, Support adoption!
A few comments/nits for the authors to consider... - In the abstract, I was not sure how to parse "..scheduling information such as event, policy, services, or resources..", are these examples well known and established as scheduling information? - The introduction made sense as a motivation for the document initially, but it should be rephrased esp that the referenced modules are expected to be updated to use this common module going forward. You may create an appendix with this historical context if needed. - Section 3.1, the description is a bit sparse; also there are no examples that use this grouping. Please expand. - The description inside the YANG module is old and incorrect, it says 2 groupings and focused only on iCalendar. - s/RFC XXXX: A YANG Data Model for Scheduling/RFC XXXX: A Common YANG Data Model for Scheduling/ - for discard-action, is there a possibility for creating new actions in future or these two are the only ones? I am asking to make sure that the choice of modeling this as enum is correct or not. - In these lists "leaf-list date-times" and "leaf-list dates", is there any ordering constraint that should be added explicitly in text? - Section 3.4 needs more descriptive text for period and timeticks. The yang module has a long must statement for verification that should be explained here in text. - Section 3.5 needs more descriptive text for by* leaves -> "An array of the "bysecond" (or "byminut", "byhour") specifies a list of seconds within a minute (or minutes within an hour, hours of the day)." The examples in the appendix gave some hints but the description should be clearer. - s/byminut/byminute/ - Appendix A.1, the text says end date is Dec 31, 2027 but the JSON says 1st Dec - "2027-12-01T18:00:00Z" - Appendix A.2, the text says Dec 1, 2025 but the example says 1st Nov - "2025-11-01T15:00:00" Thanks! Dhruv On Tue, Mar 26, 2024 at 9:20 PM Kent Watsen <[email protected]> wrote: > NETMOD WG, > > This email begins a 2-week adoption poll for: > > A Common YANG Data Model for Scheduling > https://datatracker.ietf.org/doc/draft-ma-opsawg-schedule-yang > > PS: This draft moved from OPSAWG to NETMOD > > There is no known IPR on this draft: > > > https://mailarchive.ietf.org/arch/msg/netmod/mg1KP3m6bCSXh-3N-YKLvEb_udk/ > > Please voice your support or technical objections to adoption on the list > by the end of the day Apr 10 (any time zone). > > Thank you, > Kent (as co-chair) > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
