3 ms·

Thanks for the reply. We can pre-populate the DNS of 441234567890.num.net with useful info until the rightful owner claims it. Which as I see it, is better tha

Thanks for the reply. We can pre-populate the DNS of 441234567890.num.net with useful info until the rightful owner claims it. Which as I see it, is better than what we’ve got now - which is that phone numbers are not resolvable on the internet except through closed APIs and even then in limited examples. The long term plan is to use a TLD for this eg .telephone (or whatever) but the bigger picture is that if you own a phone number that’s a unique identifier - it needs to be represented on the internet so we can interrogate it and then find WhatsApp / Skype / Zoom alternatives.

toast0 6y ago
What's the differencd between what you're proposing and ENUM (e164.arpa) other than being public (maybe?)
- elliottinvent 6y ago
  It was doomed because it was delegated to each country and there was registries and registrars appointed in each country and almost all failed to get the point across. I think ENUM had huge potential but the execution was horrible. It was also victim to proprietary system trend - Skype, FaceTime, WhatsApp audio What we’re proposing (which is public in DNS) doesn’t replace ENUM - we still need a way to covert phone numbers into SIP to connect VOIP calls using an open standard. What we’re proposing helps connect the proprietary systems to those phone numbers. As well as caller ID and other really useful stuff - like alternative ways to connect on social media etc.