>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.
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.
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?