> IMHO, we should accept that routing is going to be mixed with bridging > at the end node, and work around that reality. > > I absolutely agree you need routing. However, I disagree that your pool AP > needs to route, as Michael postulated. Keep routing in the core, or as > needed > in the case of multi-homed end devices.
I suspect most all devices are going to be multihomed at some point or another... > However, that pool AP may need access to several subnets. I want my > primary home network, my enterprise home network, and my guest network > all accessible as SSIDs at that pool AP. That means trunking back to the > home router, in my mind. I don't see any references to VLANs or any form > of trunking in the Homenet drafts or the mailing list archives. Am I missing > something? We probably need virtualization in the home, as well, for just these situations. I don't see how you substitute one for the other, though --unless you're going to push all routing onto the host (and it's always easier to push the problem someplace else rather than to solve it). :-) Russ > > Chris. > > > :-) > > Russ > > _______________________________________________ > homenet mailing list > [email protected] <mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/homenet > > > > > -- > Chris Elliott > [email protected] <mailto:[email protected]> > CCIE # 2013 R&S _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
