[dns-wg] Re: ORSN-SERVERS.NET

>>>>> "JFC" == JFC (Jefsey) Morfin <jefsey at jefsey.com> writes:

    JFC> what ORSN does is risk containment. Suppose the ICANN/NTIA
    JFC> root is hacked.  The ORSN file is not affected. This provides
    JFC> a protection. 

Could I please have some of whatever drugs you're taking? :-)

IIUC this ORSN nonsense uses the root zone file as a starting
point. So presumably any errors that get introduced there will be
passed on to ORSN and its fellow travellers, no?

    JFC> Let imagine that a terrorist atomic bomb blows
    JFC> Washington-West (the top worldwide target and an US working
    JFC> hypothesis). The propagation through the internet would be
    JFC> times devastating than the bomb itself on the USA.  

First of all, I think most people would accept that any loss of life
is far, far more devastating than the ability to route packets and
make DNS lookups.

Secondly, the root zone doesn't change much: TLDs renumber one of
their servers now and again. Even if a major catastrophe destroyed the
ability to change the root zone for a while -- I very much doubt that
-- this would at worst be a minor inconvenience for TLD operators and
the DNS in general. Good TLD managements will keep the old name
servers running for at least a month or two after a renumbering. In
fact a strong case can be made for NOT changing the root zone after
such an event for stability reasons.

Finally, suppose Something Bad has happened and the root can't be
changed. Why would a TLD then choose to update their info in this
bogus ORSN root while the info in the real root was unchanged?
Wouldn't that lead to precisely the sort of inconsistency and network
partitioning that the ORSN people claim they want to avoid?