Lorenzo, On Fri, Apr 3, 2015 at 10:44 PM, Lorenzo Colitti <[email protected]> wrote:
> On Fri, Apr 3, 2015 at 12:04 AM, Alia Atlas <[email protected]> wrote: > >> In the light of the above figures -- can I trust an IETF working group to >>> understand that a huge amount of effort has been put into removing >>> mechanisms from this protocol, and to respect that work? >> >> >> Yes, I think that the requirement for minimal mechanisms and a simple >> easy to implement and troubleshoot protocol can be clearly expressed. How >> well the WG handles this depends in part on the WG chairs and how strongly >> the participants are reminded of that requirement and how stringently the >> need >> for truly active consensus is focused on. >> > > Alia - can we put something to that effect in the charter? > That is part of the scoping & chartering discussion. It is a possible outcome. I'm still gathering data (finally next week getting a bit more time to focus) and listening to opinions and concerns. Figuring out the charter scope is part of asking for what are the requirements and applicability driving the obvious and deployed interest in Babel? > There is a real risk that any WG working on standardizing babel will start > proposing lots of changes to the protocol (due to NIH syndrome, general > bikeshedding, etc.), alienating its author and leading to lost time and the > usual failures of design-by-committee. > Usually, people are suggesting a change or feature because they need it for a deployment or customer. Sometimes, there are just "interesting ideas" - but requiring implementations and solid discussion usually make it clear what the case is and how much applicability/scope creep there is. Regards, Alia To avoid this, can we see to it that the charter of any group chartered to > take babel to proposed standard status be chartered to do so without making > substantial changes to the protocol mechanics? > > That way, if the protocol works well as is, we'll get a standard soon. If > it doesn't, the WG can always throw up its hands and fail fast. >
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
