[175376] in North American Network Operators' Group
Re: Why is .gov only for US government agencies?
daemon@ATHENA.MIT.EDU (Jared Mauch)
Tue Oct 21 01:44:26 2014
X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <BDD10A31-FEA4-4096-AC60-18F7D8B0563E@pch.net>
Date: Tue, 21 Oct 2014 01:44:14 -0400
To: Bill Woodcock <woody@pch.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> On Oct 20, 2014, at 9:30 PM, Bill Woodcock <woody@pch.net> wrote:
>=20
>=20
> On Oct 21, 2014, at 9:23 AM, Jared Mauch <jared@puck.nether.net> =
wrote:
>=20
>> Breaking tons of things is an interesting opinion of "why not=94.
>=20
> Eh. Off the top of my head, I see two categories of breakage:
>=20
> 1) things that hard-code a list of =93real=94 TLDs, and break when =
their expectations aren=92t met, and=20
>=20
> 2) things that went ahead and trumped up their own non-canonical =
TLDs for their own purposes.
>=20
> Neither of those seem like practices worth defending, to me. Not =
worth going out of one=92s way to break, either, but=85
>=20
> And in the latter case, like =93alternate roots,=94 that=92s not an =
argument against creating more TLDs=85 They=92ve already been created. =
It=92s an argument against doing so in an uncoordinated manner, which is =
the source of the breakage.
I=92ve had operational issues introduced by *TLD operators and choices =
they made. I=92m not going to document them here, but by using the root =
zone as a dumping ground for vanity addresses (e.g.: .google) highlights =
something that can be properly dealt with through normal processes.
The number of things which will change from a predictable result to a =
unpredictable result (similar to when someone decided to wildcard .com) =
will continue to increase.
Thankfully we can now receive email from spammer@example.google as it =
properly resolves and validates(!). (this is just one example).
- Jared=
