Excerpts from RJ Atkinson at 09:00:09 -0500 on Tue 9 Dec 2008: > Off the top of my head, it seems to me that this issue already exists > in the deployed IPv4 Internet and also in the deployed IPv6 Internet. > > If one considers a multi-homed end-system (i.e. one that is > directly connected to multiple IP subnetworks), that host needs > to make a decision about which source IP address to use > to communicate. > > If it is communicating with a remote node that is also multi-homed > (same definition), then it needs to make a decision about which > destination IP address to use to communicate (typically this is > a choice from the set of A/AAAA records that the first host found > in the DNS for the remote node). > > Few multi-homed hosts participate in intra-domain routing. > Fewer participate in inter-domain routing. So nearly all hosts > wanting to correspond cannot use knowledge from the routing > system to make a better informed decision about either the > source address to use or the destination address to use.
This is a good point -- individual devices that are multihomed already face that situation. Is there any deployed use of multiple simultaneous paths? What is new is the opportunity to do something more with it given locator/identifier separation. "Here's this cool new tool, but to use it you have to install new wiring in your house and by the way your electric bill will double." Scott _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
