On 03/14/2013 03:35 PM, Mark Andrews wrote:
The reason this is important to homenet and not the general enterpises is because people turn equipement off in homes when they go on holiday yet take their laptops and other equipment using names linked to the homenet with them. With enterprises these servers are always on even when everyone is on holidays and if they do turn the site fully off they are not expecting to update the zone while the site is shutdown. Mark
It's why I'm hoping that this gets captured in the -arch document. I'm still puzzling about whether it would be better for the master to be in the cloud or in the CER though. If the cloud is the master I can throw my CER in the trashcan and not lose anything which is a nice property. It's also the cloud's job to make a pretty web site to manage all of this. I trust them far more than router vendors to make useable UI's. On the other hand, I'd worry that trying to auto-populate a cloud master would be more difficult from the access control perspective: my CER can be more liberal since it can know whether a device trying to add a name has passed access control checks on my local network, say, where the cloud master has no clue about that (or, say, if it was on a guestnet or whathaveyou). There are probably a lot more considerations too. Maybe this does beg your multi-master question? Mike _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
