W3C home > Mailing lists > Public > public-mw4d@w3.org > April 2009

Re: Intro

From: Henri Asseily <hasseily@telnic.org>
Date: Wed, 8 Apr 2009 16:10:36 +0300
Message-ID: <68F68E17-B817-4FC1-9E3D-BBAA6497BF46@telnic.org>
To: <public-mw4d@w3.org>
On Apr 8, 2009, at 3:47 PM, Kai Hendry wrote:

> Any top level domain can serve NAPTR & LOC records right? I don't see
> why you need a .tel TLD for this specific purpose.

.tel is specifically for the purpose of publishing contact  
information. No A or CNAME records are allowed.
You dont _need_ a .tel, but knowing it's a .tel guarantees that  
certain features and APIs are there.
(specifically the Telhosting and friending APIs)

> By that logic, shouldn't there be a specific TLD for LOC  
> records? .geo?

It's not a question of TLD to record type mapping, it's what you do  
with the record types. NAPTRs can be used for almost anything, they're  
essentially key/value pairs (even better, they're domain/key/regex  

> And I guess it isn't specific, because people will also be using .tel
> simply for A records, right?

No. Can't do A or CNAME. Prohibited.
Allowed are MX, NINFO, TXT, NAPTR, LOC and generic.
But beyond that, there are structure definitions to the TXT and NAPTR  
records specifically for contact info purposes.

Received on Wednesday, 8 April 2009 13:11:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:07:08 UTC