Closed Bug 1157446 Opened 10 years ago Closed 10 years ago

need more info about private domains in Public Suffix List

Categories

(Core Graveyard :: Networking: Domain Lists, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: erikvanderpoel, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36 Steps to reproduce: I read the documentation at publicsuffix.org. Actual results: I did not fully understand the "PRIVATE" domains. Expected results: It would be nice to have a bit more info about the so-called "PRIVATE" domains. For example, what are the differences between ICANN and PRIVATE domains? How should a domain owner decide which one to submit a rule for? How do the publicsuffix.org maintainers decide which section to put a rule in? When rules are moved from one section to another, what considerations are there? Why is "google" in the ICANN section while "blogspot.com" is in the PRIVATE section? It would be good to have guidelines for ICANN vs PRIVATE both so that everyone can understand what they are and so that everyone can check whether those guidelines are being followed (and submit amendments if not).
ICANN domains are those delegated by ICANN or part of the IANA root zone database. The authorized registry may express further policies on how they operate the TLD. Those all go in the ICANN section. The private section are amendments submitted by the domain holder, as an expression of how they operate their domain security policy. They are not delegated by IANA - they are simply the authorized registrant. The policy is spelled out in https://wiki.mozilla.org/Public_Suffix_List That's how it plays out. The policy is simply that the authorized representative can submit amendments. For a TLD, that is the delegated registry. For a registerable domain name, it is the domain name registrant.
I've added an explanation to http://publicsuffix.org/list/. Thanks for the reminder :-) Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Thanks, Gerv and Ryan!
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.