I believe the model we have agreed on in RFC 6020 is this: - YANG modules in I-Ds are 'development' modules and not 'published' modules.
- It helps a lot during module development if 'development' modules are actually implemented. Note that implementations of 'development' modules are not intended to be 'deployed'. - A 'published' module (something appearing in an RFC in the IETF) will be subject to YANG update rules. - 'Published' modules are expected to be 'implemented' and 'deployed'. - IETF WGs need to take care of the maintenance and interoperability of what has been 'published', hence the module update rules. - Obviously, it is good to detect major flaws during 'development' and hence the importance of early 'implementation' experience. Note that there are no formal module name or namespace assignements until a module has been published as an RFC. A WG might put in a best guess what the names might be but assignment and registration via IANA happens during the publication process. Perhaps it helps to clarify in RFC6020bis that the updates rules apply to published modules and not to modules under development. /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
