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. To the extent that folks agree with the above, it would be helpful to add discussion of this as a current issue in the Meyer & Lewis draft. To the extent that folks disagree with the above, then it would be helpful if the Meyer & Lewis draft explained why folks believe the existing deployed Internet does not have the same issue, and at least describe why the scenario outlined above doesn't. Cheers, Ran [EMAIL PROTECTED] _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
