Re: "Permanent" DST

Changing the relationship between local time and true solar noon to provide more or less sunlight during certain times of the day and certain times of the year is a totally suboptimal solution. Its like changing your oil by rotating your entire car while holding the oil filter stationary. But

Re: "Permanent" DST

All of this. The reason that the proposal is always worded "Permanent Daylight Savings Time" is that there are a non-trivial number of people who genuinely believe that with DST we get more sunlight. Not more sunlight during the hours when most people are awake, literally more sunlight. In a

Re: "Permanent" DST

On 3/15/22 19:28, Sabri Berisha wrote: - On Mar 15, 2022, at 12:35 PM, nanog nanog@nanog.org wrote: But how will we remember to change the batteries in our smoke and CO2 detectors then? Don't worry, they'll remind you. At 3am. With an annoying beep. If only it were that easy. The

Re: Not Making Use of 240/4 NetBlock

I think I basically understand the policy and allocation processes. What I was looking for was some characterization of the current trends for IPv4 requests, particularly how urgent and worthy they might be and the amount of space being sought. RIRs will receive those requests. The rest of us

Re: "Permanent" DST

- On Mar 15, 2022, at 12:35 PM, nanog nanog@nanog.org wrote: Hi, > But how will we remember to change the batteries in our smoke and CO2 > detectors > then? Don't worry, they'll remind you. At 3am. With an annoying beep. Thanks, Sabri

Re: Not Making Use of 240/4 NetBlock

> On 16 Mar 2022, at 02:54, Owen DeLong via NANOG wrote: > > Having spent nearly 15 years on the ARIN Advisory Council, I think I’m able > to claim some detailed knowledge on the subject. > > In general, the RIRs themselves maintain neutrality about such things, > looking to their >

Re: Making Use of 240/4 NetBlock Re: 202203151549.AYC

> On 16 Mar 2022, at 07:27, Abraham Y. Chen wrote: > > Hi, Tom: > > 1)" better to have that conversation via the appropriate IETF > channels. ":Thanks for the recommendation. I would appreciate > very much if you could guide us to the specific contact. Before we

Re: "Permanent" DST

Once upon a time, Jay R. Ashworth said: > This also, as I understood it, why high-school is always the first grade > level which starts, and ends, the school day (often 7a-2p or so). Not "always"... high school starts 30-40 minutes later than the younger kids here. -- Chris Adams

Re: "Permanent" DST

- Original Message - > From: "Keith Stokes" > There are plenty of arguments that the existing school hours aren’t best for > educating children so the better answer might be to make school hours match > later daylight hours. As it turns out, there's a deeper answer here: There are

Re: "Permanent" DST

Once upon a time, Dave said: > Folks for most systems, this is a change to a single file. Not a really hard > thing to accomplish For lots of up-to-date servers running a current and well-maintained operating system, this will be mostly easy (except that if you maintain hundreds of servers,

Re: "Permanent" DST

On 3/15/2022 1:19 PM, Andy Ringsmuth wrote: On Mar 15, 2022, at 2:40 PM, Eric Kuhnke wrote: If Canada doesn't do the same thing at the same time, it'll be a real hassle, dealing with a change from -8 to -7 crossing the border between BC and WA, for instance. It has to be done consistently

Re: "Permanent" DST

There are plenty of arguments that the existing school hours aren’t best for educating children so the better answer might be to make school hours match later daylight hours. > On Mar 15, 2022, at 5:23 PM, Matthew Huff wrote: > > They don't want their names on it when what happened in the

Re: "Permanent" DST

And here's the NPR story which leads with "the Senate passed a bill": https://www.npr.org/2022/03/15/1086773840/daylight-saving-time-permanent-senate I really don't know why that site does not list it, because it certainly should. But here you are. On March 15, 2022 6:07:36 PM EDT, Matthew

Re: "Permanent" DST

"where did this bill come from in the first place?" The whitehouse, Sen. Sheldon Whitehouse (Sponsor), Sen. Marco Rubio (Co-sponsor) On Tue, Mar 15, 2022 at 3:47 PM Elmar K. Bins wrote: > dedel...@iname.com (Dave) wrote: > > > Folks for most systems, this is a change to a single file. Not a

Re: "Permanent" DST

S.623 as amended, literally hundreds of Tweets in the last 2 hours tell me. Yeah, this just happened today. That would be why NPR lead with it on the 4 p.m. newscast. On March 15, 2022 6:07:36 PM EDT, Matthew Petach wrote: >Please provide a link documenting this claim. > >I have been reviewing

Re: "Permanent" DST

It appears that Mel Beckman said: >-=-=-=-=-=- >We already have this problem with Arizona, which never changes time for the >summer. Sure it does. It switches from MST to PDT. Helpfully, John

Re: "Permanent" DST

with all this discussion, i have not seen any post of this classic and most critical explainer https://www.youtube.com/watch?v=k4EUTMPuvHo

RE: "Permanent" DST

They don't want their names on it when what happened in the 70s happens again. The effect of setting everything to DST and staying there is that in the winter, especially in the norther latitude it will be pitch dark during most of the morning when children get picked up at school bus stops.

Re: "Permanent" DST

Please provide a link documenting this claim. I have been reviewing the actions listed on congress.gov, and this is not an action listed as having taken place. https://www.congress.gov/bill/117th-congress/senate-bill/623/all-actions?overview=closed#tabs The last action shown for this bill was

Re: "Permanent" DST

Dave wrote: > Folks for most systems, this is a change to a single file. Not a really hard > thing to accomplish Oh, hah, good one. I twitch with mild PTSD thinking about the last time there was change to DST in the US[1], and how everybody quickly found out that e.g., Java, databases,

Re: "Permanent" DST

On Tue, Mar 15, 2022 at 02:06:50PM -0700, Brandon Svec via NANOG wrote: > "..rational time worldwide"? Like all of China in one timezone and Mumbai > :30 off center? and Arizona? and that one county in Idaho? The word "rational" does not belong in a sentence discussing timezones or even

Re: "Permanent" DST

> > On Mar 15, 2022, at 2:06 PM, Jay Ashworth wrote: > > It violates the international rule determining what your time zone should be > based on what your longitude is. > > That is not trivial. It’s an informal convention, not “rule”, and it not vaguely consistent in practice now.

Re: "Permanent" DST

> On Mar 15, 2022, at 1:01 PM, Mel Beckman wrote: > > We already have this problem with Arizona, which never changes time for the > summer. Except for the Navajo Nation…

Re: "Permanent" DST

> > I’m all for giving up the time change, but the standard should probably > still be UTC offset. > That's literally what the text of the bill does. On Tue, Mar 15, 2022 at 5:08 PM Eric Tykwinski wrote: > What I don’t understand, is why change time, just change working hours. > I’m all for

Re: "Permanent" DST

Oh. This was "Unanimous Consent"? AKA "I want to vote for this, but *I do not want to be held responsible for having voted for it when it blows up*?" I'd missed that; thanks. - Original Message - > From: "Tom Beecher" > To: "Eric Kuhnke" > Cc: "nanog@nanog.org list" > Sent: Tuesday,

Re: Bombs and Hackers are Battering Ukraine's Internet Providers

:: Despite obliterated terrain and internet wires, fire-blackened data centers, curfews, lack of light, :: and the danger of death from above, the fixers go out and turn the internet back on so Ukrainians :: can stay in touch with one another and get word out beyond borders, to

Re: "Permanent" DST

On Tue, Mar 15, 2022 at 12:22:14PM -0700, Jay Hennigan wrote: > On 3/15/22 12:19, Dave wrote: > >Ending DST is a really good idea. > > > >Moving 15 degrees East not so much but let’s face it, the environmental > >impact statement will take forever to write > > Moving 15 degrees east would put

Re: "Permanent" DST

    On 3/15/2022 9:22 AM, Jay Hennigan wrote: On 3/15/22 12:19, Dave wrote: Ending DST is a really good idea. Moving 15 degrees East not so much but let’s face it, the environmental impact statement will take forever to write Moving 15 degrees east would put Washington DC in the

Re: "Permanent" DST

On 2022-03-15 14:37, Eric Tykwinski wrote: What I don’t understand, is why change time, just change working hours. I’m all for giving up the time change, but the standard should probably still be UTC offset. If you work 9-5, change it to 10-6.  Every company can post working hours on their

RE: "Permanent" DST

In the 70's, you couldn't check your smartphone to find out when a business was open, so there was a certain assumption that it would be open not only during "normal business hours", but that it would be consistent throughout the year. We live in a completely different world today, where I'd

RE: "Permanent" DST

Agreed, it seems pretty foolish to move us to “permanent” DST instead of just going with standard time, as far as offset from UTC goes. If I had my way, the world would just use UTC and drop all the timezone stuff. But small steps, getting rid of the DST change is a good start. Jason From:

Re: "Permanent" DST

"..rational time worldwide"? Like all of China in one timezone and Mumbai :30 off center? and Arizona? and that one county in Idaho? I can't agree with any technical objections because there is already the need to account for all these bizarre details worldwide and even DST in the US changed in

RE: "Permanent" DST

Probably worse for the people who border Indiana; we always wonder if we're on the same time as who we're dealing with, depending on where in Indiana the other person is. From: NANOG On Behalf Of Paul Ebersman Sent: Tuesday, March 15, 2022 3:35 PM To: Eric Kuhnke Cc: nanog@nanog.org list

Re: "Permanent" DST

I would say if something passes the United States Senate in our current political environment by unanimous consent (which this did) , I kinda feel like there won't be a ton of issues with everybody figuring out how to line themselves up appropriately. On Tue, Mar 15, 2022 at 5:01 PM Eric Kuhnke

RE: "Permanent" DST

Not sure about your state, but in mine we’re mandated by law to have the new smoke/co2 detectors with 10-year sealed batteries in place by Jan 2023. I’m not sure I can even buy one locally that isn’t a 10-year. Jason From: NANOG On Behalf Of PJ Capelli via NANOG Sent: Tuesday, March 15, 2022

Re: "Permanent" DST

Actually I think the proposed bill leaves AZ and HI on standard time.  The bill's primary focus is on stopping the changing of the clock twice a year. Arizona time is supposedly MST all year but it is not consistent.  The Indian nations adopt their own

Re: "Permanent" DST

Ok, this just in from MST3K: “The change will take place at noon earth time.” -mel via cell On Mar 15, 2022, at 4:53 PM, Kain, Becki (.) wrote:  Wouldn’t that move Detroit into Lake Erie? From: NANOG On Behalf Of james.cut...@consultant.com Sent: Tuesday, March 15, 2022 4:16 PM To: Jay R.

Re: "Permanent" DST

It has been bubbling under for some years-there are about I think it's 10 or 11 states which have already passed state laws changing it, pending that the federal law blocking those be dropped-that's the Uniform Time Act of 1966 if I have the title correct. And to reply to somebody else his

Re: "Permanent" DST

> On Mar 15, 2022, at 13:11, Kain, Becki (.) wrote: > >  > What does Arizona do since you’re saying all of N America has to be the same? > Arizona doesn’t do daylight time at all. They stay MST year-round. During the summer they are the same as California.

Re: "Permanent" DST

What I don’t understand, is why change time, just change working hours. I’m all for giving up the time change, but the standard should probably still be UTC offset. If you work 9-5, change it to 10-6. Every company can post working hours on their website. Obviously for most of us, it’s a moot

Re: "Permanent" DST

Sure, but you imply that the proposed alternative=-going to permanent DST--is only a trivial change to, and it is not. It violates the international rule determining what your time zone should be based on what your longitude is. That is not trivial. On March 15, 2022 4:25:21 PM EDT,

Re: "Permanent" DST

That is true but at present everything business related in BC has a clear expectation of being in the same time zone as WA/OR/CA, and AB matches US Mountain time. On Tue, 15 Mar 2022 at 13:35, Paul Ebersman wrote: > eric> If Canada doesn't do the same thing at the same time, it'll be a > eric>

Re: "Permanent" DST

eric> If Canada doesn't do the same thing at the same time, it'll be a eric> real hassle, dealing with a change from -8 to -7 crossing the eric> border between BC and WA, for instance. It has to be done eric> consistently throughout North America. You must not have ever dealt with Indiana, where

Re: Making Use of 240/4 NetBlock Re: 202203151549.AYC

Hi, Tom: 1)    " better to have that conversation via the appropriate IETF channels. ": Thanks for the recommendation. I would appreciate very much if you could guide us to the specific contact. Before we attempt to do so, however, it would be prudent to report the history of our team's

RE: "Permanent" DST

Wouldn't that move Detroit into Lake Erie? From: NANOG On Behalf Of james.cut...@consultant.com Sent: Tuesday, March 15, 2022 4:16 PM To: Jay R. Ashworth Cc: nanog@nanog.org list Subject: Re: "Permanent" DST WARNING: This message originated outside of Ford Motor Company. Use caution when

Re: "Permanent" DST

Folks, for most, this change removes the twice yearly disruption of their circadian rhythm and consequent surge of accidents and injuries. My timely recommendation, which also require change to a single file, is to stick to “standard” time year round making solar high noon closer to 12:00.

Re: "Permanent" DST

dedel...@iname.com (Dave) wrote: > Folks for most systems, this is a change to a single file. Not a really hard > thing to accomplish Well... 1 - I'm surprised anybody is running local timezones on their systems at all 2 - I like how american politics is capable of creating new problems;

Re: "Permanent" DST

Since the nominal (15 degree slice) boundary between Mountain and Pacific goes right through the Phoenix metro area, it sort of makes sense that Arizona would stay on the same time year round. Michael > On 15 Mar 2022, at 15:44:12, Mel Beckman wrote: > > We already have this problem with

Re: "Permanent" DST

My understanding is that Russian time zones are one hour “east” of where they should be and that China, despite its size, is a single time zone. So this proposal isn’t unique. Whether it’s good is a different question… Michael > On 15 Mar 2022, at 15:44:46, Brian R wrote: > > Thanks for

Re: "Permanent" DST

> > 2) Move every square inch of US territory 15 degrees to the east. Mind if I ask where you got this? Nowhere can I find an article or bill referencing this specific point. This article

Re: "Permanent" DST

> On Mar 15, 2022, at 2:40 PM, Eric Kuhnke wrote: > > If Canada doesn't do the same thing at the same time, it'll be a real hassle, > dealing with a change from -8 to -7 crossing the border between BC and WA, > for instance. It has to be done consistently throughout North America. Nah, not

Re: "Permanent" DST

WaPo has a been there done that item today. https://www.washingtonian.com/2022/03/15/the-us-tried-permanent-daylight-saving-time-in-the-70s-people-hated-it/ On Tue, Mar 15, 2022 at 3:11 PM Jay R. Ashworth wrote: > In a unanimous vote today, the US Senate approved a bill which would > > 1)

Re: "Permanent" DST

So to clarify/muddy the situation further... Time zones do not fall purely on the 15 degree lines on a globe. As such, the location of the sun overhead is locality specific within a timezone. Don’t let the enemy of done win here. ;) > On Mar 15, 2022, at 2:44 PM, Brian R wrote: > > Thanks

Re: "Permanent" DST

On Mar 15, 2022, at 3:11 PM, Jay R. Ashworth wrote: > > In a unanimous vote today, the US Senate approved a bill which would > > 1) Cancel DST permanently, and > 2) Move every square inch of US territory 15 degrees to the east. While I thoroughly agree with item 1, I suggest that the seismic

Re: "Permanent" DST

Folks for most systems, this is a change to a single file. Not a really hard thing to accomplish Dave > On Mar 15, 2022, at 3:19 PM, Dave wrote: > > Ending DST is a really good idea. > > Moving 15 degrees East not so much but let’s face it, the environmental > impact statement will take

Re: "Permanent" DST

On 3/15/22 12:40, Eric Kuhnke wrote: If Canada doesn't do the same thing at the same time, it'll be a real hassle, dealing with a change from -8 to -7 crossing the border between BC and WA, for instance. It has to be done consistently throughout North America. That would be no different than

RE: "Permanent" DST

What does Arizona do since you’re saying all of N America has to be the same? From: NANOG On Behalf Of Eric Kuhnke Sent: Tuesday, March 15, 2022 3:41 PM To: Jay R. Ashworth Cc: nanog@nanog.org list Subject: Re: "Permanent" DST WARNING: This message originated outside of Ford Motor Company.

Re: "Permanent" DST

Interesting - AZ would join PDT as UTC-7. I wonder if they'd switch to line up with the rest of MDT. - Thomas Scott | mr.thomas.sc...@gmail.com On Tue, Mar 15, 2022 at 3:47 PM wrote: > Apparently this also adjusted the calendar, making today 2022-04-01 ? > >

Re: "Permanent" DST

Thanks for finding the clarification on this Ray. I'm with the OP Jay that this will cause long term problems. The 15 degrees is not mentioned in the document just the change from "Standard Time" to "Daylight Time" permanently (they probably don't even understand it is in 15 degree

Re: "Permanent" DST

We already have this problem with Arizona, which never changes time for the summer. -mel via cell On Mar 15, 2022, at 3:40 PM, Eric Kuhnke wrote:  If Canada doesn't do the same thing at the same time, it'll be a real hassle, dealing with a change from -8 to -7 crossing the border between BC

Re: "Permanent" DST

On 3/15/22 12:26, Ray Van Dolson via NANOG wrote: I think this is essentially the bill: https://www.congress.gov/bill/117th-congress/house-bill/69/text Not finding anything about 15 degrees. The 15 degrees is kind of a joke. It means that "high noon", when the sun is at zenith, would occur

Re: "Permanent" DST

Ok, so the fifteen degrees is bogus, nothing moves, and all that is really happening is standard time is ending. The OP here wins an award for “obfuscating reality”. No sweat. Fixing all the systems to comply with the new time rules is billable :) -mel via cell > On Mar 15, 2022, at 3:36

Re: "Permanent" DST

If Canada doesn't do the same thing at the same time, it'll be a real hassle, dealing with a change from -8 to -7 crossing the border between BC and WA, for instance. It has to be done consistently throughout North America. On Tue, 15 Mar 2022 at 12:35, Jay R. Ashworth wrote: > The bill is

RE: "Permanent" DST

Well, it would create term limits -Original Message- From: NANOG On Behalf Of Jay Hennigan Sent: Tuesday, March 15, 2022 3:22 PM To: nanog@nanog.org Subject: Re: "Permanent" DST WARNING: This message originated outside of Ford Motor Company. Use caution when opening attachments,

Re: "Permanent" DST

Apparently this also adjusted the calendar, making today 2022-04-01 ?

Re: "Permanent" DST

On Tue, Mar 15, 2022 at 12:33 PM Ray Van Dolson via NANOG wrote: > I think this is essentially the bill: > https://www.congress.gov/bill/117th-congress/house-bill/69/text > > Not finding anything about 15 degrees. 360 / 24 = 15. Because we'd standardize on DST instead of the old railroad time

Re: "Permanent" DST

But how will we remember to change the batteries in our smoke and CO2 detectors then? Sent from ProtonMail for iOS On Tue, Mar 15, 2022 at 3:19 PM, Dave wrote: Ending DST is a really good idea.Moving 15 degrees East not so much but let’s face it, the environmental impact

Re: "Permanent" DST

The bill is "permanently move all US time zones one hour earlier (-8 thru -5 is replaced permanently with -7 thru -4). They are *calling it* "permanent DST", but that's not really what's happening, in my engineering appraisal. Or my geopolitical one, but I don't lay claim to professional

RE: "Permanent" DST

I think this is essentially the bill: https://www.congress.gov/bill/117th-congress/house-bill/69/text Not finding anything about 15 degrees. Ray -Original Message- From: NANOG On Behalf Of Mel Beckman Sent: Tuesday, March 15, 2022 12:19 PM To: Jay R. Ashworth Cc: nanog@nanog.org

Re: "Permanent" DST

Permanent DST has the same effect as cancelling DST and moving all the timezones up one hour. Since timezones are roughly sliced every 15 degrees of ... longitude?, hefting the physical US 15 degrees eastward would have the same effect on timezones as just a legal glitch to change them. On 15

Re: "Permanent" DST

On 3/15/22 12:19, Dave wrote: Ending DST is a really good idea. Moving 15 degrees East not so much but let’s face it, the environmental impact statement will take forever to write Moving 15 degrees east would put Washington DC in the middle of the Atlantic Ocean. This might not be a bad

Re: "Permanent" DST

I don’t follow why cancelling DST has the effect of moving the US fifteen degrees to the east. Also, your subject line reads “permanent DST”, but from your language the bill will be permanent standard time. I haven’t read the bill, but I’m hoping you can explain your position more clearly.

Re: "Permanent" DST

Ending DST is a really good idea. Moving 15 degrees East not so much but let’s face it, the environmental impact statement will take forever to write Dave > On Mar 15, 2022, at 3:11 PM, Jay R. Ashworth wrote: > > In a unanimous vote today, the US Senate approved a bill which would > > 1)

"Permanent" DST

In a unanimous vote today, the US Senate approved a bill which would 1) Cancel DST permanently, and 2) Move every square inch of US territory 15 degrees to the east. My opinion of this ought to be obvious from my rhetoric. Hopefully, it will fail, because it's likely to be the end of rational

Re: Dropping support for the .ru top level domain

> > Other arguments are political, and I do not presume to set international > political policy. I only offer a technical opinion, not a political one. > Your technical opinion is what everyone is responding to. Dropping support for any TLD in the root zone DB is a terrible idea, period.

FCC Foreign SPonsorship Identification Rules Go Into Effect

https://www.fcc.gov/document/fccs-foreign-sponsorship-identification-rules-go-effect The Federal Communications Commission today announced a March 15, 2022 compliance date of sponsorship identification requirements that will now require broadcasters to disclose when foreign governments or

Re: Bombs and Hackers are Battering Ukraine's Internet Providers

There's a group of our colleagues working to help out where they can. Keep Ukraine Connected https://nogalliance.org/our-task-forces/keep-ukraine-connected/ FYI, -M< On Tue, Mar 15, 2022 at 1:22 PM Sean Donelan wrote: > > >

RE: Bombs and Hackers are Battering Ukraine's Internet Providers

Man,never has a network engineer's job been so hard and so important I wish them all the best of luck and the least of bombs. We used to only have to worry about backhoes -Original Message- From: NANOG On Behalf Of Sean Donelan Sent: Tuesday, March 15, 2022 1:19 PM To:

Bombs and Hackers are Battering Ukraine's Internet Providers

https://www.forbes.com/sites/thomasbrewster/2022/03/15/internet-technicians-are-the-hidden-heroes-of-the-russia-ukraine-war/?ss=cybersecurity=75eb5cdd2884 Images sent to Forbes by Kyivstar show what the conditions are like. Despite obliterated terrain and internet wires, fire-blackened data

Re: Dropping support for the .ru top level domain

Owen is spot on, and for people who say dropping .ru you won’t affect citizens, they are forgetting about email addresses. I have a friend at a .ru domain who hosts his email out of country, which leaves me with a reliable way to give him real news. -mel On Mar 15, 2022, at 12:08 PM, Owen

Re: Dropping support for the .ru top level domain

I’m reminded of a quote from “2010 The year we make contact”: “Just because our governments are behaving like asses doesn’t mean we have to.” (Roy Scheider as Dr. Heywood Floyd) Breaking any communications facility is, IMHO, counterproductive to all sides. Communication is almost always

Re: Not Making Use of 240/4 NetBlock

Having spent nearly 15 years on the ARIN Advisory Council, I think I’m able to claim some detailed knowledge on the subject. In general, the RIRs themselves maintain neutrality about such things, looking to their respective communities for input on what to do. However, so long as the IETF and

Re: Dropping support for the .ru top level domain

 Kind regards,Alexander Maassen Oorspronkelijk bericht Van: brian.john...@netgeek.us Datum: 15-03-2022 15:08 (GMT+01:00) Aan: Patrick Bryant Cc: "nanog@nanog.org list" Onderwerp: Re: Dropping support for the .ru top level domain I think you need to understand that these

Re: Dropping support for the .ru top level domain

I think you need to understand that these actions will only prolong the situation and likely make things worse. Less info is always worse than more. - Brian > On Mar 15, 2022, at 4:07 AM, Patrick Bryant wrote: > > I propose dropping support of the .ru domains as an alternative to the other >

Viaplay wrongly classifies IP as VPN

*cHi All,* I'm wondering if anyone here could help me out in reaching someone at Viaplay, we have customers that rent a internet connection from us as an ISP and are getting a message when trying to start something that they are behind a VPN, even at the office I have the issue (we are behind our

Not Making Use of 240/4 NetBlock

Dear NANOG-ers, Hope this email finds you in good health! Please see my comments below, inline... Le mardi 15 mars 2022, a écrit : > > Hi Barry, Thanks for your email, brother! > But the RIRs are the ones fielding requests for IPv4 space, and have > some notion of how policy implementation

Re: Dropping support for the .ru top level domain

I propose dropping support of the .ru domains as an alternative to the other measures discussed here, such as dropping Russian ASNs -- which *would* have the counterproductive effect of isolating the Russian public from western news sources. Blocking those ASNs would also be futile as a network