Re: Send-N draft: draft-bellis-enum-send-n-02 published
Duane <[email protected]>
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <[email protected]> |
Roy Arends wrote: > On Jul 1, 2008, at 12:19 AM, Duane wrote: > >> Clive D.W. Feather wrote: >> >>> The same happens if you put an A record at a higher level. So don't >>> do that. >> >> Only if you request ANY/ALL, if you specifically request NAPTR it >> shouldn't, which is why someone else suggested you make a new DNS type >> to store send-n against then naptr wouldn't break except for the case >> where someone requested ANY/ALL > > Regardless of the type at the higher name, simply the existence of a > name will cause wildcards not to expand for that name. Right so they should look into developing a proper routing protocol, something like BGP, which would give smart switches a complete view of the dial plan and then wouldn't need to send out dns queries and rely on third party systems being available since the information could be cached locally until an update arrived changing some routing information. -- Best regards, Duane