Minutes 2016 06 02
| Meeting Materials | Attending |
|---|---|
 password: 2fAmwFiT |
Ambika Prasad Tripathy, Einar Nilsen-Nygaard, Alexander Clemm, Alberto Gonzalez Prieto, Andy Bierman, Eric Voit, Hector Trevino, Tim Jenkins, Balazs Lengyel, Walker, Peipei Guo, Kent Watsen |
- Future Meetings will move to Wednesday, Eric to work with Andy to see if we can alternate Wed & Thursday
- No objection to current drafts with open issues listed below as minimum to submitting for WG adoption
- List of Open Issues by draft will be primary review item for next call.
- add a disclaimer on the top that each is not an IETF submitted draft yet. Instead it is a work-in-progress intended to get to submission readiness.
- add an open issues section as an Appendix. These open issues, can be tracked here, and removed by the RFC editor or by the authors over time as they are resolve.
- For future releases once things stabilize, consider adding a diffs section as an appendix. (Note: Perhaps this can be addressed via the open issues & resolutions appendix, used in conjunction with “diffs” capability already available with IETF drafts
- We need some intro text in the RFCs to define the linkages to other RFCs. Also these four should be submitted as a cluster of sequential RFCs, to allow for the relationships to be further cemented in readers minds
- Consider adding a design considerations section, this might be different
- Tim to address draft specific issues via email
- NETCONF mapping needs to be pulled out
- No one had reasons why Configured Subscriptions should use RESTCONF. HTTP transport seemed
- Discussion on Call Home. For Configured subscriptions, the Restconf definition is not appropriate for Call home as we are not using Restconf. But still the Publisher will still need to establish the connection, so in a general sense this is needed.
- Will a single subscription be delivered in sequence? We have been assuming that the answer is “yes”, however this might need further investigation as different line cards might stream updates for the same subscription without going through a central marshalling process. Expect more on this over time. (Will need to be in text.)
- Mismatch between 5277bis and how RESTCONF handles subscriptions. Need as position on how to reconcile the two.
- Alberto to post in the coming days.
- Negotiation vs. Auto Adjust.
- Eric reviewed the Cloud Policer use case from last week’s slide deck where auto adjust would not be viable. Andy notes that the negotiation may end up in some implementations in a way which provides less than stellar results.
- Negotiation should be relevant for I2RS Ephemeral requirements
- At this point it appears that Negotiation will be included for YANG Push