Thanks Ray. I agree that the routing protocol discussion has been interesting, but that we really need to take a more disciplined approach if we're ever going to get consensus on what the "correct" technology solutions are.
I think that starting with the architecture is a good idea. This will let us develop a holistic view of what it is we're trying to solve. I think it's important that we also get some idea as to the relative importance of the various architectural challenges (topology and §3.2 "Principles"?) over others. We need to be very careful to balance functionality with ease-of-use in the recommendations we make. IMO, the likelihood that functionality can be implemented bug-free and not cause confusion (and not cause trouble calls to the service provider) is part of the ease-of-use element. That is, if introduction of a function could confuse people or do bad things more often than it is found to be useful, then we don't need to be recommending that function as a MUST for everybody, and perhaps not as a SHOULD for everybody, either. Understanding the whole picture will also let us consider how selection of one technology to deal with one element impacts other selections. I'll take a look at the referenced draft and provide my comments. Barbara > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Ray Bellis > Sent: Friday, August 05, 2011 10:58 AM > To: [email protected] > Subject: [homenet] Homenet Architecture Draft > > We currently have draft-arkko-townsley-homenet-arch-00 as a candidate > for our first chartered WG item. > > To ensure we can maintain some inertia following our session in Quebec, > it would be appreciated if members could review this document. > > I'd especially like to see some feedback on §3.2 "Principles" since I > get the impression that some of those may be quite contentious. > > The discussion on LAN-side routing is interesting and I'm happy to see > that continue. However we must also work on the bigger picture before > getting rat-holed too much into implementation details. > > Ray Bellis > Homenet co-chair > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
