On Thu, Mar 26, 2015 at 3:58 PM, Lorenzo Colitti <[email protected]> wrote:
> On Thu, Mar 26, 2015 at 1:20 PM, Terry Manderson < > [email protected]> wrote: > >> So the the decision will not be made only on the work needed. Specifying >> the timeline means the design team must also consider the resources at >> hand, or reasonably available, to reach an acceptable, full, standardized >> solution. >> > > Can we make that explicit in the charter? Given how much time has already > been spent here, I feel we must avoid a situation where the design team > chooses a protocol, but then nobody is willing to implement it. > > So, I would like to see the charter say that the design team must confirm, > before choosing the protocol, that there are volunteers to provide an > implementation that meets the necessary resource constraints to be included > in a home router. > > To my mind, if the perfect routing protocol were to descend from heaven, > but did not have volunteers lined up to implement it in an appropriate > time, the design team should reject it. Do we agree on that? > I agree with this to a point, but I think the design team should be directed to do more than just identify volunteers who are committed to providing an implementation that meets the resource constraints of a typical home router device. I also think it should be directed to require that A) some implementation of the chosen protocol must be made available in source to the community under RAND licensing terms, and B) the volunteers must be committed to presenting in Prague a demonstration of that code running on typical hardware. Shorter james: just as it would be a failure if we pick a routing protocol that we can't standardize, it would also be a failure if we pick one that can't be demonstrated in running code. I hope this isn't a controversial statement. -- james woodyatt <[email protected]> Nest Labs, Communications Engineering
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
