3 ms·
>NAPTR is already misused for sip location imho Why? >Could they make it any more complicated than this? It may look messy, but complicated? You can write a
by wibblenut 17y ago
>NAPTR is already misused for sip location imho
Why?
>Could they make it any more complicated than this?
It may look messy, but complicated? You can write a parser in a few minutes. It's simple and it works.
- viraptor 17y agoMisused, because why should the client care about your routing? SIP already provides a way to drop the router from the path after relaying the first packet - why put the same exact capability onto DNS then? There are caching issues, routing delays caused by 3 resolver queries (NAPTR -> SRV -> A), etc. etc. Imho enum should be available only explicitly - not as the base routing mechanism. Complicated - because of regexes and usage of prefixes such as E2U which don't make sense here. Someone created a service based on a custom TLD and marks the entries as E2U even though they don't use E.164 numbers at all. If they cannot get it right, how can users understand it?