On Thu, Feb 19, 2015 at 08:43:26AM +0100, Mikael Abrahamsson wrote:
> >* While ram and flash have grown to be essentially "free" I really dont
> >see home router and cpe makers rushing to embrace slower languages or
> >bigger flash and memory requirements anytime soon.
This worry has been raised by others as well.
> That's because there has been no requirement to do so, most of the time.
> Basically a device has been sold with a certain amount of features, and
> this featureset hasn't changed over time, thus there is no need to
> future-proof. I see this changing.
What are the indicators you see ?
> Also, currently most routers consists of mostly L2 high speed forwarding,
> with some L3 thrown in between two ports (the WAN port, and the 5th
> internal port to the 5 port switch chip with 4 external ports). With
> homenet, all this changes. Now all ports need to be L3. This is a huge
> change both when it comes to bandwidth needed from the CPU to the ports,
> and also L3 performance needed. This will require home gateway
> manufacturers to make very different devices.
Sure. But does homenet give them the right user benefits to make it
worth their while ? Especially for gear that would not be OEM'ed by
SPs but in retail.
How many commercial vendors are really selling boxes with OpenWRT (no
homenet) ? To me, OpenWRT (without homenet) has already a lot of
benefits over those vendor specific SW on home routers, but seemingly
that hasn't helped much to proliferate OpenWRT into commercial offerings.
> We also have the (previous) mobile SOC:s trickling down into the home
> router space, and these are very price/performance efficient.
Just having looked for a good router for homenet, i am not really happy
yet with the choices available. Especially because i'd like to also run a bit
more than just basic routing. >= 32MByte memory, >= 16MByte flash for
example. Still seems to be a very limited set of choices.
> Do we really believe people are going to use wifi links to connect devices
> within their homenet?
Yes. Simply to extend reach. And if i understand it correctly,
If you have the typical setup:
Internet - router/AP .... wireless1... client/bridge/AP ---- wired
.... wireless2
AFAIK, this setup is typically sometthing that only works well if
router/AP and client/bridge/AP come from same vendor due to the complexitites
in AP/bridge looking like multiple clients on wireless1. So it
looks like a good opportunity to highlight how homenet would turn
client/bridge/AP into client/router/AP and eliminate those problems,
allowing vendors of such devices to much easier get added - without
expecting that router/AP is upgrade/changed.
Cheers
Toerless
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
