Re: Send-n, rat holes and real issues
Duane <[email protected]>
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <[email protected]> |
Rosbotham, Paul wrote: > So, for numbering plans where no complete number is a prefix of another (*), you should either get the NAPTR per today, or a Send-N, but not both. I can't help but think this doesn't belong in DNS, repeating hit after hit on name servers when the information could be dealt with at a local level has to be the better way to do it surely. > (*) I believe that in some countries that may not be the case, e.g. 01234567 and 01234567890 can exist as separate numbers...obviously there'd be issues in that scenario. I wonder if this made it into the send-n proposal, in any case this highlights further the need for a proper think about how to do this rather than going bull at a gate with something that sort of works but seems like a very nasty hack to me. There seems to be a lot of effort to 'fix' the analogue problem, the simple answer would be to move everyone to digital systems and when they hit dial that's the final number :D -- Best regards, Duane