I'm not in agreement with the proposed solution because it puts even more burden on the client. I think the question one needs to ask before the jumping head first on the engineering solution is: what harm can overlapped prefixes cause?
Assuming this would be a transient error condition, the worst possible situation is a client that flips a coin and picks a random PID. Remember that Applications that have ALTO clients should not rely on guidance to work, so an ALTO client should be always prepared to fall back to regular routing. The ALTO Server operator by this time should have looked at some log entry, detected the problem and will work on fixing it. -RP From: "Y. Yang" <[email protected]<mailto:[email protected]>> Date: Saturday, November 9, 2013 12:38 AM To: IETF ALTO <[email protected]<mailto:[email protected]>> Subject: [alto] New text on handling overlapping prefixes To handle both Non-Overlapping and Overlapping Network Maps, an ALTO Client moves any IP prefix that is defined in more than one PIDs into a special PID named .OVERLAP, and then applies the longest-prefix matching algorithm. A future extension of this document may redefine how overlapping prefixes are handled.
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
