On Jul 16, 2007, at 4:51 AM, Melinda Shore wrote:
Another problem is the lack of naming and lookup facilities. DNS
SRV records are probably going to be as good as it gets. VoIP
protocols and others that make use of embedded addresses actually
do have an advantage here, because they're able to transmit an
acquired address in the application signaling. However, that won't
help with servers, P2P, and so on.
Complex arrangements are currently are being establishing for peer-to-
peer communications. These arrangements entail a structure of IP
addresses used to navigate through various devices supporting
protocols like Teredo. DNS currently does not provide a specific
resource record type for this purpose, although conceivably fields
such as Priority within an SRV resource record could define a
topology structure. These addresses might then be employed at
different stages of a transport topology. DNS SRV records normally
return a list of IP addresses as additional information, where an
application would then need to arrange this information.
Although DNS is not normally used in this fashion, for our
application, DNS servers are updated every so many seconds where each
contains millions of records. This is done while responding to tens
of thousand of queries per second. DNS protocol is also commonly
used to track dynamic addresses assigned to residential routers.
These routers are then associated with internal hosts having a
dynamic address. Obviously DNS can handle very dynamic
environments. There is little infrastructure to support this type of
volatility at this time. This lack of support may change when the
marketplace desires non-proprietary solutions.
-Doug
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf