If This Had Been An Actual Emergency
saridder writes "In an increasing attempt to regulate the Internet like the current PSTN, the US Government has asked the IETF to come up with a system to prioritize government and emergency worker traffic in the event of another disaster, much like the GETS system already in place for the PSTN. It's interesting to follow, because it's only an RFC, so you don't have to follow it. I probably won't be prioritizing government traffic on any of my routers." The story has a link to the ieprep working group if you want to get involved or comment. Perhaps this is a better way than GOVNET.
When I first read this, I was thinking of the application of routing theory to the movement of vehicles such as would be required in an emergency, which naturally led to...
If you thought TCP/IP over carrier pigeon had huge-azz latency, wait'll you try TCP/IP over government bureaucrat!
First, the IP datagram is printed on a form I-TCPIP by the former acting deputy chief. The scroll of paper is inserted into his briefcase and he's reassigned to acting director for international affairs.
At each hop, the source address is taken by the executive associate commissioner for field operations, and filed according to procedure. After he becomes regional director for the western region, he looks up the address of the next hop.
The next hop's address is glommed onto the datagram by the assistant commissioner for inspections, formerly the acting executive associate commissioner in the office of programs.
Finally, the router, upon receipt of the datagram, forwards it to the special counsel to the commissioner, who herself is then reassigned to assistant deputy executive associate commissioner for immigration services.
Six months after the hijackers initiate transmission via a high-delay, low-throughput, and low-altitude service, the router at the flight school gets the packet containing the 9/11 hijackers' visa approval notifications.
Security is not only a problem in a normal operation, as special measures (such as the firing of the incompetent) cannot be taken even when government bureaucrats are used in a tactical environment.
Please, there weren't enough obscure acronyms in this piece for your average government agency. We need more. Have someone get on this ASAP. We need more acronyms PDQ. We need to assign a DOAP and make sure they PATFT. That way we'll all be MHIB. Clearly LIAP for posts or we'd have LODT. So lets KUTGW with OAP and we'll all be VAFWWH.
I consider myself a tech-head, and if I can't make sense of a tech article at a glance after getting a Bachelors in Computer Science, something is wrong. I don't even know if I'm interested in this article. It has something to do with the internet, emergencies, and 9/11; and the rest is friggen jibberish. To add insult to injury, michael the slashdot moderator adds an unrecognizable acronym of his own!
PSTN? GETS? IEPREP? Not to mention the slightly better known RFC and IETF? This is crazy. IMHO, I shouldn't have to follow a link just to find out WTF the article is about. These kind of posters need to STFU or slashdot will be a FUBAR POS that just wastes my time.
DOAP: Designated Obscure Acronym Poster
PATFT: Post All The Friggen Time
MHIB: Much Happier I Bet
LIAP: Length Is A Priority
LODT: Lots Of Descriptive Terms
KUTGW: Keep Up The Good Work
OAP: Obscure Acronym Posts
VAFWWH: Very Appreciative For What We Had
// harborpirate
// Slashbots off the starboard bow!
Or "Turn on Cartoon Network."
Stupid sexy Flanders.