Also, we need to distinguish between a deployment that will hand out exactly one /64 (broken) and one that will hand out multiple /64s on request, just not necessarily contiguous (strange, but not so broken).
On Sat, Mar 9, 2013 at 8:57 AM, Ted Lemon <[email protected]> wrote: > I am a bit skeptical that we don't have to deal with the case where an > end-user buys a broken gateway and then plugs a homenet gateway into it. > The way we deal with it might be to recommend that the homegate, when it > gets no delegation, set up a captive portal to notify the user of the > problem, but to simply punt on it seems like a bad option. > > BTW, an example of a router that might be a decent homenet router is the > Almond router: > http://www.kickstarter.com/projects/2037429657/almond-80211ac-touchscreen-wifi-router-smart-home?ref=email > > It has an LCD display, so informing the user that they have set up a > broken network is pretty easy. But we probably ought to have a document > that walks homenet gateway implementors through the various issues and > options, even if we don't propose a solution that makes it work. > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet >
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
