Refresh Public Suffic List to the latest version

Refresh Public Suffic List to the latest version

This updates from revision
28e17a0f8f26f1bddfbd62d9861b223efa7792bc (2016-07-06)

to revision
4dcaacaf593dde7e2a34436913c24af3bf2bdb06 (2016-08-16)

R=pkasting@chromium.org
BUG=626532
Committed: https://crrev.com/702d65e434b5a41965f5b9fbe644e9e4300157b6
Cr-Commit-Position: refs/heads/master@{#412419}

[Ryan Sleevi, 2016-08-17 00:48:17]

The ICANN removals are because several TLD operators were unable to demonstrate
they could be delegated to.

The PSL adds entries when ICANN has signed the contracts and is preparing to
begin the load testing phase, as after load testing complete, it's delegated to
the root. Several of these failed the load test, so ICANN booted them.

[Peter Kasting, 2016-08-17 01:01:50]

LGTM

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
File net/base/registry_controlled_domains/effective_tld_names.dat (left):

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
net/base/registry_controlled_domains/effective_tld_names.dat:7025: //
africamagic : 2015-03-05 Electronic Media Network (Pty) Ltd
The theme of this CL: If your name has "(Proprietary) Ltd" in it, you can't run
a TLD.

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
File net/base/registry_controlled_domains/effective_tld_names.dat (right):

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
net/base/registry_controlled_domains/effective_tld_names.dat:6534: // lib.de.us 
Issue #243 - Moved to Private section at request of Ed Moore
<Ed.Moore@lib.de.us>
I read the issue log here, and honestly, I kinda feel like the PSL site should
go into way more detail on the distinction between public, private, and no
record on this list.  It sort of appears at first as if it has to do with
whether an ICANN registry runs the TLD, but that's not really it at all.

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
net/base/registry_controlled_domains/effective_tld_names.dat:7306: // blog :
2015-05-14
Kinda curious why a few of these have owner names removed.

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
net/base/registry_controlled_domains/effective_tld_names.dat:10667:
us-east-1.amazonaws.com
This is now alphabetical, but the way it doesn't have ".compute" in it like
every other entry makes me wonder if it's actually correct.  Can somebody check
with Amazon?

[Ryan Sleevi, 2016-08-17 01:18:43]

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
File net/base/registry_controlled_domains/effective_tld_names.dat (right):

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
net/base/registry_controlled_domains/effective_tld_names.dat:7306: // blog :
2015-05-14
On 2016/08/17 01:01:50, Peter Kasting wrote:
> Kinda curious why a few of these have owner names removed.

ICANN's data feed - https://newgtlds.icann.org/newgtlds.csv - is sending
incomplete data.

I've poked ICANN a few times, but no complete answer. Some were due to
transitions (e.g. delegated to one party, party fails testing, then they enter a
registration contract with another registry for that TLD), but that doesn't
explain this case. There's a total of 42 domains with that issue.

They're working on a new datafeed that provides additional information, but we
haven't switched to it yet.

https://codereview.chromium.org/2248253002/diff/1/net/base/registry_controlle...
net/base/registry_controlled_domains/effective_tld_names.dat:10667:
us-east-1.amazonaws.com
On 2016/08/17 01:01:50, Peter Kasting wrote:
> This is now alphabetical, but the way it doesn't have ".compute" in it like
> every other entry makes me wonder if it's actually correct.  Can somebody
check
> with Amazon?

Already having discussions with Amazon on how best to manage these entries, so
added that to the thread :)

[Ryan Sleevi, 2016-08-17 01:18:47]

The CQ bit was checked by rsleevi@chromium.org

[commit-bot: I haz the power, 2016-08-17 01:19:19]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-17 01:59:14]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-17 02:01:02]

Description was changed from

==========
Refresh Public Suffic List to the latest version

This updates from revision
28e17a0f8f26f1bddfbd62d9861b223efa7792bc (2016-07-06)

to revision
4dcaacaf593dde7e2a34436913c24af3bf2bdb06 (2016-08-16)

R=pkasting@chromium.org
BUG=626532
==========

to

==========
Refresh Public Suffic List to the latest version

This updates from revision
28e17a0f8f26f1bddfbd62d9861b223efa7792bc (2016-07-06)

to revision
4dcaacaf593dde7e2a34436913c24af3bf2bdb06 (2016-08-16)

R=pkasting@chromium.org
BUG=626532

Committed: https://crrev.com/702d65e434b5a41965f5b9fbe644e9e4300157b6
Cr-Commit-Position: refs/heads/master@{#412419}
==========

[commit-bot: I haz the power, 2016-08-17 02:01:03]

Patchset 1 (id:??) landed as
https://crrev.com/702d65e434b5a41965f5b9fbe644e9e4300157b6
Cr-Commit-Position: refs/heads/master@{#412419}