On Sat, 7 Feb 2015 13:52:42 -0500, Carter Bullard wrote: > David, And it is still pretty simple. Want to do something different from > what is in the charter, change the charter. But as long as the charter > specifies a process, the WG should follow that process.
You quoted the charter as saying it would do requirements. Please note the "may" in those sentences, not "will": The NVO3 WG may produce requirements for a network virtualization control plane, ... ... The NVO3 WG may produce requirements for network virtualization data planes based on encapsulation of virtual network traffic over an IP- based underlay data plane. That wording was intentional, becuase a number of folk feel that while requirements can be useful, but they are a means to an end, not an end itself. I'm with others that would prefer to see requirements published as RFCs only if tightly coupled with an actual substantive document. Requirements for requirements sake are just not a good use of anyone's time, and all-to-often take focus/cycles away for the presumed actual purpose of a WG. Thomas _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
