Hello Paul,

On Tue, 04 Nov 2008 00:04:38 +0100, Paul Wouters <[EMAIL PROTECTED]> wrote:

On Mon, 3 Nov 2008, Yngve N. Pettersen (Developer Opera Software ASA) wrote:

FYI, this draft removes the central repository requirement, and moves the method for collecting the information out of scope.

Suggestions for how to collect the information are welcomed.

The other question is, how will people know where to find the information?

Good question.

The application will retrieve it where the vendor specifies. This is likely to be a mirror of the original repository, hosted by the vendor (like fraud protection is today).

The original repository (or repositories) can be built by vendor, crowd-sourced (example: PublicSuffix.org), hosted at the IANA, by the TLD registries, or somewhere else.

The major question is where to get good quality data for the repository, wherever it is hosted. For that there are serveral possible solutions, DNS extensions with a deep treewalking search to build a database, TLD registries providing information to a repository, volunteers gathering publicly available information about registry-like domains (e.g PublicSuffix) , etc.

My personal preference is that the TLD registries provide the information through some kind of web service, either hosted by them or mutually acceptable repository, that can then be collected/mirrored by the vendors. The registries are IMO the agents that are most likely to have accurate and up-to-date information about their domain structure.

Given the emergence of PublicSuffix, I decided it was time to separate the data collection method(s) from the distribution method of this specification.


--
Sincerely,
Yngve N. Pettersen
 
********************************************************************
Senior Developer                     Email: [EMAIL PROTECTED]
Opera Software ASA                   http://www.opera.com/
Phone:  +47 24 16 42 60              Fax:    +47 24 16 40 01
********************************************************************
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to