Hi Alex, Eric and all, I reviewed the latest Draft and have some comments, please help to confirm, thanks.
For draft-ietf-netconf-yang-push-06: 1. In section 4.1, the configured subscription receivers not sepcify which mechnism to connect to client, it's better define clearly, specify it should be call home protocol. 2. In YANG model, "leaf period" 's unit is timeticks(1/100s), it difficult to understand for user, suggest to change the unit to millisecond. 3. for the "leaf dampening-period ", it's better to give one maxmum value, otherwise it may can not effective 4. If the time is not enough to send all the data in a cycle, how to deal with the remaining data? Just postpone the next cycle or do not send the remaining data? If you do not send the remaining data, it may cause the remaining data can not be monitored.\ 5. How to declare which path support "on-change"? Current draft defined all path not support "on-change" as default, if all "configure" leaf support "on-change" how I should do? Add extension for all "configure" leaf? It looks too complex, whether we can support one simple mode, such as define by type? then I can define all "configure" lead support "on-change". 6. I think "subscription-status" attributes not enough , when subscirption status is suspend ,we need "suspend reason", " suspend time". When subscription resume, we need "resume time" 7. or "Modify-subscription " and "Delete-subscription ", we should give the limitition: Subscriptions established via RPC can only be Modified/deleted via RPC using the same transport session used for subscription establishment. For draft-ietf-netconf-subscribed-notifications-02: 1. In A.1. ietf-netconf-netconf-event-noti, the draft name should not be "[I-D.ietf-netconf-restconf-notif]", it should be "draft-ietf-netconf-netconf-event-notifications-01", right? 2. In "section 1. Introduction" there have two repeated item "o Ability to subscribe to event notifications using two mechanisms: dynamic and configuration subscriptions." Thanks & Regards Walker (Guangying zheng) [X]
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
