[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: An alternative to 6to4 and teredo

Margaret Wasserman wrote:
many applications involve more than two parties, even if the interconnections
between components of those applications are two-party connections. a >2
component app often needs to be able to provide referrals from one component
to another - e.g. to say "if you need to access this component, contact it at
address A port P".

I've been thinking about this a lot lately, and I wonder...  Why do these
referrals need to be by IP address?  It would make more sense to
refer another party to a DNS name and port number.  Then the other party
can do its own DNS look-up, and make its own address selection decision.

Keith's argument is that DNS is too slow and not available.




if the network requires address selection in order to allow one 
component to

reach another, then it hinders operation of this kind of application.

and for a variety of reasons, DNS is often too ambiguous, too slow, or 
too

unreliable for DNS names to be used as general-purpose names for hosts.



If DNS is too ambiguous, slow or unreliable for this purpose, shouldn't we
fix DNS?



Yes!

If the referral model can be made to work with DNS, then many of
the issues with referrals and limited-scoped addresses would go
away (IMHO).

Regards,
Brian