On 17.8.2015, at 14.19, [email protected] wrote: > Hi, > > +1. > > a) Any idea how often this data changes and really needs a re-write in “a > typical home" ;-) ?
Not very often, at least if you don’t bother to prune ‘old’ stuff much (it depends a bit, but most conservative setup would have some sort of per-interface offset value it would _only_ store when a) it changes (due to conflict),b) local set of interfaces grows, or c) local set of clients grows if you want to offer them persistent leases which I consider a bad idea). But again, this is assuming clever software. Stupid software could do write per client DHCP/DHCPv6-stateful request (or per prefix assignment action) :-) > b) Impact of > > MS>- cheap router vendors > MS> > MS>- bad software > > may depend on choice of flash file system, and how countermeasures against > “flash wear" are considered by the file system software authors. Sure. But I know for a fact some consumer devices (not routers though that I know of, nowadays at least) using FAT(/FAT32) on a flash disk, and that is just a sign of ’shoot me in the head, please..’ ;) Then you’re relying on lower layers (=flash controller) doing the smart thing. And so on. Ultimately, counting on anything is counterproductive, and making design as simple as possible is appealing. Cheers, -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
