| Newsgroups |
gmane.ietf.enum |
| Message-ID |
<[email protected]> |
Some technical points:
It seems undesirable to not allow the send-n record to be usable as a
wildcard. The reason is that if one has a partial dial string that
has not already been processed for send-n information, the only way to
check if there is a relevant send-n record is to do DNS lookups on all
prefixes of the string. That results in a lot of DNS lookups, which
is what the send-n mechanism was to avoid in the first place.
I am not familiar with the details of DNS wildcards, though, so there
may be no way to act on this concern.
The second issue is the use of the maximum number of digitsmax -- if
the owner of a higher-level node sets digitsmax, it can prevent the
delegated owner of a subtree from using more digits. Or rather, the
subtree can use more digits as long as the caller doesn't attempt to
use send-n to determine the end of the dial string. Indeed, it's not
clear that digitsmax saves DNS queires in any practical case. So
maybe digitsmax should be removed.
Dale