Re: Why is .gov only for US government agencies?

[Tomas Lynch <tomas.lynch () gmail com>]

Spanish speaking countries .gob.$2lettercodecountry. No problem so far.

On Mon, Oct 20, 2014 at 8:05 PM, Mark Andrews <marka () isc org> wrote:
> In message <CAH_OBie1Xzzc_9Xo7wPwgQBgeT=F+0bbEGOw4c5dnjBfZTEJzw () mail gmail com>
> , shawn wilson writes:
> > On Mon, Oct 20, 2014 at 6:26 PM, Doug Barton <dougb () dougbarton us> wrote:
> >
> > > 3. Set a target date for the removal of those TLDs for 10 years in the
> > > future
> >
> > Because this worked for IPv6?
>
> Well there wasn't a target date set for the change to IPv6 and it
> is starting to happen pretty fast now.
>
> These are nameserver by IP type (IPv4 then IPv6).  For Alexa top
> 1000, Alexa AU zones, Alexa bottom 1000 of top 1M, Alexa GOV zones
> and TLD/Root zone.
>
> % foreach f ( tld-report/reports/*2014-10-20* )
> foreach? echo $f
> foreach? awk '$2 !~ /:/ { print $2}' $f | sort -u | wc
> foreach? awk '$2 ~ /:/ { print $2}' $f | sort -u | wc
> foreach? end
> tld-report/reports/alexa.2014-10-20T00:00:00Z
>     2178    2178   33180
>      513     513   11131
> tld-report/reports/au.2014-10-20T00:00:12Z
>     6343    6343   97529
>      726     726   16441
> tld-report/reports/bottom.2014-10-20T00:00:12Z
>     1788    1788   26945
>      416     416    9660
> tld-report/reports/gov.2014-10-20T00:00:12Z
>     1263    1263   18821
>      301     301    6765
> tld-report/reports/tld.2014-10-20T00:00:00Z
>     1602    1602   23035
>     1065    1065   20276
> %
>
> Or over all the servers
>
> % awk '$2 !~ /:/ { print $2}' tld-report/reports/*2014-10-20* | sort -u | wc
>    11805   11805  178630
> % awk '$2 ~ /:/ { print $2}' tld-report/reports/*2014-10-20* | sort -u | wc
>     2554    2554   53979
> %
>
> Now who says IPv6 hasn't taken off?
>
> Setting target dates helps.  Having a administator willing to pull
> the plug on the set date helps even more.  .ARPA was cleared of
> hosts because there was a date set and the last entries were removed
> even if the operators of the hosts weren't ready.  There was never
> any intention to remove in-addr.arpa.
>
> > > Obviously there are various implementation details for effecting the move,
> > > but application-layer stuff will be as obvious to most readers as it is
> > > off-topic for this list.
> >
> > In this case, it's all about the "application-layer stuff" - that'd be
> > the stuff to fail hard - mainframe IP gateways, control systems,
> > Lotus, Domino, etc. BIND is fine. Even most of the PHP apps would
> > (should, maybe) be fine. But that's not runs most of the gov.
> >
> > > Regarding the time period in #3, decommissioning a TLD is harder than you
> > > might think, and we have plenty of extant examples of others that have take
> > n
> > > longer, and/or haven't finished yet *cough*su*cough*.
> >
> > Do we really have any prior examples that are even .1 the size of the
> > usgov public system? Again, I'm not just referring to BIND and Windows
> > DNS (and probably some Netware 4 etc stuff) - this would be web, soap
> > parsers, email systems, vpn, and all of their clients (public,
> > contractor, and gov). Anything close to what y'all are talking about?
>
> Government departments get re-named all the time.  Many departments
> have already gone through name changes since coming onto the net.
> This would just be another one.
>
> Size really isn't a issue, there are more than enough staff to do this.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka () isc org