On 4/12/2016 3:05 AM, Scharf, Michael (Nokia - DE) wrote: > The link is in my first e-mail: > https://www.ietf.org/iesg/statement/writable-mib-module.html > > The relevant sentence is: "IETF working groups are therefore encouraged to > use the NETCONF/YANG standards for configuration, especially in new charters." > > Section 2.2 of draft-bittau-tcpinc-api-01 includes what one could call > "configuration", so the applicability of that IESG statement seems to me a > reasonable question.
The IESG statement is worded poorly at best. It appears to me to imply "when picking between MIB and Netconf/YANG models, pick the latter". I do not read this as "configuration APIs should be described in terms of Netconf/YANG." An abstract API should never need to get into such a level of detail to require a particular implementation. If you're aiming for something beyond that, IMO the IETF is the wrong place (e.g., a better place would be POSIX). Joe _______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
