14
edits
Changes
Added some additional use cases, more coming
| com, co.uk
| appspot.com
|-
| TLD Validation in programming languages
| Numerous programming languages use the PSL to validate form entries or logic determining validity of TLDs where PSL is used to validate the rightmost apex of TLD.
|
|
|
|-
| Anti-Spam
| The rightmost apex of TLDs is reviewed for validity on return/sender addresses as a basic check, using match in PSL as initial pass/fail to reduce processing time.
|
|
|
|-
| Whois client software
| Use of PSL to track delta/changes/additions to list of possible TLD extensions for purposes of determining whois servers for distributed clients.
|
|
|
|}
* I don't know whether the cookie "question" is precisely correct. Are there situations where one organization should be able to read/write another organization's cookies? For example, should a page on appspot.com be able to read a page on foo.appspot.com?
* I don't think I understand the "history sorting" case completely. What are some concrete examples of this? In an ideal world, would this distinguish between subdomains which are conceptually "different sites" from the parent domain (e.g. mail.google.com versus google.com) and those which are not?
* We should probably consider hypothetical future cases involving ICANN's new "sell anyone their own TLD" policy, like whether we need to do anything special if someone buys a TLD and tries to make it directly navigable via an A record. (Is there some organization which has the authority to approve or reject such actions?)[Jothan] Will track this
