- ii) pass the other party both the identifier and a current, working
address for that endpoint.
thus requiring me to continue to use IP addresses in referrals.
actually this is a fairly common tactic;
indeed. or at least, this isn't the first time it's been seen (and my
now-expired I-D describing the best way for apps to deal with NATs mentioned
something similar). but it doesn't really solve the problems associated with
ambiguous addresses. it still doesn't provide a reliable way to talk to that
host in the presence of ambiguous addresses. it only keeps you from
mistakenly talking to the wrong host when two hosts use the same address.