Ukraine request yikes

JASON BOTHE jbothe at
Tue Mar 1 23:27:07 UTC 2022

Not sure how I feel about this. My thoughts have always been to leave government out of Internet operations or otherwise they get comfortable and will want to make decisions that we may not be comfortable with. 

During wartime, I would think the desire would be to have them connected in order to have access to information and knowledge as necessary. If the idea is suppress Russia from performing bad actions, disconnecting their tld(s) will not solve this and is just a bad approach all around. 


> On Mar 1, 2022, at 16:22, George Herbert <george.herbert at> wrote:
> I don’t hear anyone in the networks field supporting doing it.
> It was a yikes that the request was made, but not looking at all likely to happen IMHO.
> -george  
> Sent from my iPhone
>>> On Mar 1, 2022, at 2:12 PM, Brian R <briansupport at> wrote:
>> The problem with all this talk, especially with trusted international neutral organizations, is that once they bend they will never be trusted again.  Shutting off the routes, removing TLDs (or keeping them because of politics), etc will cause irreparable damage to these organizations.  Bowing to governments, politics, etc does not have a path back from future control.
>> This is a recommendation that will only hurt people (China, North Korea, [even the USA], etc all do this to control their people).  Governments will get around whatever the limitations are, it may take them time and resources but they will get around it.  Freedom of information is the only way to help people understand the reality of what is going on in the world (galaxy, universe, etc).
>> Brian
>> Technological solutions for Sociological problems 
>> From: NANOG < at> on behalf of Bryan Fields <Bryan at>
>> Sent: Tuesday, March 1, 2022 1:23 PM
>> To: nanog at <nanog at>
>> Subject: Re: Ukraine request yikes
>> Hash: SHA256
>> On 3/1/22 4:08 PM, David Conrad wrote:
>> > See .SU.
>> >
>> > (SU was moved from allocated to "transitionally reserved” back when the
>> > USSR broke up. My recollection is that an agreement was reached by which
>> > .SU users would be migrated out to appropriate new ccTLDs, that is, the
>> > ccTLDs based on ISO codes created for former Soviet republics, and no new
>> > entries would be added to .SU. However, when ICANN tried to propose a plan
>> > to finalize removing .SU from the root (around 2006 or so), the operators
>> > of .SU reopened registrations and complained to the US Dept. of Commerce,
>> > who were overseeing ICANN performance of the IANA Functions contract.
>> > Eventually, the Russian government was able to convince ISO-3166/MA to move
>> > SU to “exceptionally reserved” (like UK, EU, and a number of others) and
>> > forward motion on removing .SU from the root essentially ceased.)
>> I know someone (non-Russian) using .su for a funny name ending in .su.  This
>> is non-political and caters only to an English speaking audience.  These were
>> registered in the last few years, so they are still open and taking the
>> registrations.
>> I would ask what of .ly used for various URL shorteners, and .kp or .cn?  All
>> these are representing evil countries too, why do they get a pass.  I'm
>> certain they would argue .us should be revoked for the same.
>> This would break connectivity, and that's a bad thing.
>> - -- 
>> Bryan Fields
>> 727-409-1194 - Voice
>> kUA+QQ//Z9ovTSFqVEunql2guHAN3xWaNpCpuNJCGM68dJTBSWrPEY0zFXlmZG1k
>> 0TWrSrRSoWogiJmRvaOuFx6KxkaADqZaZq6OFaCw3jvyFGULw+auyuATGlhnUL8p
>> CV0AbovPUnoAef1qJdglFkqnfrGBxeBGsgRIM8tx2l/G+zq5MdMnCx9cM+JmmN1y
>> b+jrV4oekgXRZLAMI/sA9clMAXUmlgReRvit8YBccunkmMP8naQ92vj9dvVGZld0
>> hGguK2a7vFXpDiW5o0nFe5GRdGIqM0aWUz6p0qkB9JudkZkAyEqSpCePZky4LdAt
>> ebh9544PZu/vllQjv3L6vENlCURcifTIRSevcwfKZtos7UG4mJI1UQ51OLTRjB7a
>> nqYkVNJSQJ+dXZFLPoRHNUOu4+1MAyozpDeMJzMsr4a7Ru2lh0AOTiXxDaSRhOd+
>> 2s3rQigh/l6cP/x9iM7+f+rInHzPihHfjbwcxhyqd12EFxgTe3hvi9JlRSe18RYw
>> bnDKQg3xKp1eIk0sZMeLyIWDERjsMxIuEP9MuKHp+oTCrLq6MFSgUiFan7M5Pk2t
>> mwB3sbFuwkVzfmDbbnbelll30ukXQM3d7KVp2AHbsvI6hNs6zHZgRb7ZgGrR9Ep5
>> 6UlYqVqQOWtYNujNxYRgzemFI6lgJj8GHyDeh0wLRCP0aw/ATPg=
>> =KK8e
>> -----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the NANOG mailing list