4 ms·
Sounds similar to Telnic https://datatracker.ietf.org/doc/html/draft-reid-dnsext-nkey-00 https://datatracker.ietf.org/doc/html/draft-reid-dnsext-nkey... https
by darkr 5y ago
Sounds similar to Telnic
https://datatracker.ietf.org/doc/html/draft-reid-dnsext-nkey-00 https://datatracker.ietf.org/doc/html/draft-reid-dnsext-nkey...
https://icannwiki.org/TelNic https://icannwiki.org/TelNic
- elliottinvent 5y agoThanks for your comment and for highlighting this. As a summary for others: Telnic (and Telnames) allowed people to store contact data in the DNS of their .tel domain name. > Sounds similar to Telnic Telnic used NAPTR records and was only available on .tel domains, NUM uses TXT and can be used on any domain name, by publishing a "_num" zone. Telnic was also "just" for contact data. What we're trying to do with NUM is make it possible to publish any kind of data. Contact data as just one "module".
- fredrivett 5y agoThe other key difference here as far as I understand, is that Telnic required you to register .tel domains, you couldn't bring your own domain and store contact information against that.