Jürgen, On Fri, May 06, 2016 at 09:44:18AM +0200, Juergen Schoenwaelder wrote: > I disagree with many things in the document. For example, a data model > must not detail things like > > o encoding [XML | JSON] > > o protocol [RESTCONF | NETCONF] > > o protocol-transport [ssh, tls, tcp] > > o transport-ports [ports]
I believe the strawman document may be too general with regard to these items. These keywords may be appropriate for subscription/notification type model entries, especially when the subscription is intended to be directed to an end-point different than the transport connect the subscription is being requested from. The strawman should be updated to cover an example to clarify this point. > because of layering and modularity concerns and of deployment > flexibility. There are many more of these. Overall, it would help if > there were fewer documents and not so many overlapping documents. I agree that there are too many documents. The number of them has been somewhat driven by different parties pushing for analysis of requirements from different angles. As we converge on content, we should be centralizing the content. -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
