On Fri, Dec 18, 2015 at 03:22:48PM +0100, Ladislav Lhotka wrote: > > Is it not? I would say it severely restricts the workflow for the data model > development. The ultra-conservative update rules essentially permit only > incremental changes to published modules. This would be fine if the data > model landscape already was reasonably stable. We are not that far though, > and everything is in flux. So I believe we would be much better off with > "release early - release often" strategy, which is made impossible by the > existing update rules. >
There is a "release early - release often cycle" in the IETF process - it is called the Internet Drafts stage. Unfortunately, often people wait for things to stabilize (becoming an RFC) before implementing. I assume we would have fewer but more solid data models if they would all come along with running code behind them (and ideally > 1 independent implementations). The problem might be "us" and not the update rules. /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
