NaibofTabr

Well shit, yeah, that “MUST be accepted and parsed” is pretty explicit. That sucks. What is even the point of revising standards? How the fuck do we ever get rid of some of these bad ideas?

#18 seems really bad, like no-one-has-ever-sanity-checked-this bad.

Yeah I feel like the correct answer for anything obsoleted by a more recent RFC should be “Invalid”.

Yeah, although maybe it’s good that they’re straightforward? No euphemisms, no pretense.

Er, yes but also this…

https://www.braintreesci.com/restraint-containment-handling/restraint/rat-restrainers/decapicones/

Make injections and decapitation quicker and easier with Braintree Scientific’s DecapiCones. Tapered plastic film tubes provide quick and easy restraint of rats, mice, and other small animals. I.P. injections can be made directly through the film! DecapiCones restrain post-decapitation kicking and prevent personal contact with feces or urine. A unique dispenser holds DecapiCones open and ready for use. Simply hold the DecapiCone in one hand and introduce the animal with the other. Animals enter readily, heading for the breathing hole at the small end. Roll and squeeze the large end closed. They may be used repeatedly for injections and simply discarded when soiled. For decapitation, hold at the rear and insert the small end into the decapitator.

They come in quantities of 200, in handy pre-loaded dispensers.

Realistically no organization has so many endpoints that they need IPv6 on their internal networks. There’s no reason to deal with more complicated addressing schemes except on the public Internet. Only the border devices should be using IPv6.

Hopefully if an organization has remote endpoints which are connecting to the internal network over the Internet, they are doing that through a VPN and can still just be assigned IPv4 addresses on dedicated VLANs when they connect.