> I haven't even mentioned source address selection, as that doesn't come > into play for a singlehomed homenet - but as soon as the homenet gets > multihomed, applications would benefit a LOT from doing intelligent > source address selection. Like in presenting users a selection menu > "use ISP? -> SpaceNet, HE.NET, don't care" and picking the appropriate > source address. > > Yes, there's quite a bit of specifications missing to be able to do that > (like, how do I find a label to stick onto an address I find on my > interface), but for a *homenet*, this is the way it needs to be - nobody > will fiddle with the router to do "http goes to SpaceNet, bittorrent goes > to HE.NET", but if the application can do it, it greatly empowers users.
Indeed. And some devices like mobile phones already allow the user to say "only sync my photo album when on Wifi". One thing that does worry me is every application developer having to re-invent the code for all of this (find labels, actually implement the networking code correctly etc). I think a standard API should be available for all of this. Otherwise all operating system vendors and distributions will come up with something completely different which will make it even harder for the application developers to do the right thing. Cheers, Sander _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
