On Tue, Jan 10, 2017 at 10:20:35AM +0100, Ladislav Lhotka wrote: > > > On 10 Jan 2017, at 09:39, Juergen Schoenwaelder > > <[email protected]> wrote: > > > > On Tue, Jan 10, 2017 at 09:20:36AM +0100, Ladislav Lhotka wrote: > >> > >> I think we need protocol and YANG specs that are not tied to any > >> particular model and that are thus capable of matching unforeseen > >> real-world implementations. This is no sci-fi, HTTP and XML schema > >> languages work this way. > >> > > > > I disagree that HTTP and XML schema languages do the same thing. Our > > goal is interoperable configuration of network devices; the notion of > > Even now, a client that's programmed to write straight to running isn't > interoperable with a server that has candidate and read-only running. A > RESTCONF server that supports only JSON isn't interoperable with a client > that supports only XML. > > We are not in a situation that every pair of a randomly chosen server and > client need to be interoperable. It's IMO perfectly fine if IoT and ISP > networks use different clients. Yet, both can still use the same RESTCONF, > same YANG, and even same YANG modules. >
Yes, there are optional protocol features and the protocols support negotiations of protocol features. Not a big deal. HTTP is full of this as well. The point is that writing to candidate has a well defined meaning because we defined how candidate behaves and interacts with the other datastores. If a client commits candidate, it knows what kind of changes it can expect to see in other datastores. If you want to do away with well-known datastores, you (a) either provide all the semantics we currently have hard-wired into well-known datastores as meta-data at runting (and you require that every client is able to interpret this meta-information correctly) or (b) you significantly loose functionality and we end up with generic editing protocols that unfortunately do not help much with configuration management (since we lost how information in differnet datastores interacts). In case I completely mis-understand you, consider to write an I-D. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
