Update on e164.org verification calls

[evilbunny]

After numerous requests and a fair bit of discussing this afternoon, we came to the conclusion that there is no more risk in verifying against information stored in e164.arpa then there is in the current system of sending calls out via the PSTN network.

In fact there could be less risk since deployment is fairly limited and the benefit in attacking e164.arpa to have details listed with e164.org seems kind of pointless, it would be easier to hijack the phone call we send out.

Although this may not be beneficial to many people due to lack of world wide deployment.

[stuartri]

EvilBunny,
Could you please elaborate a little more on what this thread is about. Obviously I have missed the previous discussion.

Could you also tell me how e164.org and e164.arpa tie together. Which should be the master source for enum or does it not matter? I thought that RFC 3761 refers to a e164.arpa domain for dns lookup withing the context of mapping pstn numbers to dns entries.

Any feedback would be appreciated.

Thanks Stuart

[evilbunny]

Originally Posted by stuartri

EvilBunny,
Could you please elaborate a little more on what this thread is about. Obviously I have missed the previous discussion.

Could you also tell me how e164.org and e164.arpa tie together. Which should be the master source for enum or does it not matter? I thought that RFC 3761 refers to a e164.arpa domain for dns lookup withing the context of mapping pstn numbers to dns entries.

Short answer is they don't, although people can tell us to use information in their zone to send verification calls to instead of using the PSTN to send out verification calls...