13
edits
Public Suffix List/Use Cases: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "The PSL is being used for more things than was originally intended, and various edge cases, which need to be "in" for one use but "out" for another, are ca...") |
No edit summary |
||
| Line 35: | Line 35: | ||
| appspot.com | | appspot.com | ||
|} | |} | ||
[pkasting] Three questions: | |||
* 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?) | |||