[190519] in North American Network Operators' Group
Re: New ICANN registrant change process
daemon@ATHENA.MIT.EDU (David Conrad)
Wed Jul 6 15:20:56 2016
X-Original-To: nanog@nanog.org
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAL9jLabTmTQM6z--F75=f4Xy7-AT5ane0SLznRMoMvHzQQNZyw@mail.gmail.com>
Date: Wed, 6 Jul 2016 08:53:30 -1000
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--Apple-Mail=_7DA0DFB7-FFF2-4EEF-B151-EC75A9CBAA05
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On Jul 6, 2016, at 7:23 AM, Christopher Morrow <morrowc.lists@gmail.com> =
wrote:
> On Mon, Jul 4, 2016 at 3:03 PM, Jay Ashworth <jra@baylink.com> wrote:
>> Seems to me that the proper thing to be done would have been for
>> Registries to deauthorize registrars on the grounds of continuous =
streams
>> of complaints.
>>=20
>>=20
> <devils advocate hat>
> On what metric? Pure volume? Percent of registrations? type of =
complaint by
> similar x/y?
> </devils advocate hat>
By the terms the Registry sets in the Registry/Registrar Agreement and =
to which the Registrar agrees in order to sell the Registry's names.
> there are 'lots of complaints' against some registrars, but if you =
have
> ~20% of the .TLD market you're prone to get more volume than a 1%er, =
right?
There's this concept called "normalization", e.g., complaints per 100 =
delegations or some such.
> Also, this isn't REALLY the registrY's problem is it?
Depends on whether or not the Registry wants their TLD to be associated =
with spam/malware distribution/botnet C&C/phishing/pharming and be =
removed at resolvers via RPZ or similar. Ultimately, the Registries are =
responsible for the pool the Registrars are peeing in -- it's the =
Registry's namespace, is it not?
> i love how icann makes avoiding blame so easy.
I love how people love to blame ICANN.
Regards,
-drc
(speaking only for myself)
--Apple-Mail=_7DA0DFB7-FFF2-4EEF-B151-EC75A9CBAA05
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQEcBAEBCgAGBQJXfVOqAAoJENV6ebf0/4rX9L8H/j5lQ4ac+1n2D3wPHafCfPB5
Jm2ZsQIykeD5M/KIA73UkSYmkOWWDIbTpCIJZb9mf0Q2BvgB4OlpUHykzl5WNaZQ
oy714HNhwiE0Ho7J2GtZFna5TEgHa8kxfifvxVh6hEBG7DYq9TO/is3rTw1u0x3B
LWylA1sSMXsRHpYZ/v6v1E2kwOzYgwNMY6VFaNef1+UXKtoHd+grjuCK3bLKjKxX
mHooSwEgsJYWpa73gEV5LJFj7t2JQshjautLnMikpXhUuzjjJsM/Zdu/gap+R6Mq
x39mb/OZluTrNr76zqH9Kz1qaY9VBF6lA317PhHqHPpfLyVwwOoXWPsX73Aghqg=
=Rz0B
-----END PGP SIGNATURE-----
--Apple-Mail=_7DA0DFB7-FFF2-4EEF-B151-EC75A9CBAA05--
