RFC 3514: New Bit Defined for IPv4 Headers

RFC 3514 was just released, with a new bit definition for use in the headers of IP packets. Because there are important security implications, anyone coding internet services (on either the client or server end) should probably take a look.

Comments

It's about time!

[Motherfucking Shit]

Finally, the scriptkiddie bit! Now we'll be able to drop all that pesky DDoS traffic with ease!

Re:Nasty!

[stevens]

Is there a link explaining why they chose that theme?

No link necessary. Matt's Script archive is well-known among Perl programmers as one of the densest collections of hole-ridden crappy code on the net.

There's even a project to write secure, well-written clones of his scripts so the poor bastards stuck with his can drop-in something that won't allow remote exploits on their machine. :-)

What a day!

[Ridge]

First this and now I noticed the W3C added an addendum to HTTP 1.1:

10.5.4.1 503.1 Slashdotted

The server is currently unable to handle the request due to a fucking slashdotting of the server. Visit slashdot.org for potential mirrors.

April 1st RFCs are always the most important...

[Bradee-oh!]

There may be some strange cosmic significance about April 1st, or just a series of amazing coincidences, but many RFCs published on April 1st are of amazing importance.

Potentially devastating Y10k problem

Lifesaving method to temporarily reroute ip in cause of equipment failure

Protocol to guarantee software engineer productivity and efficiency

Addressing ipv6 with incredible bandwidth savings

Planning ahead to Star Trek technology with current protocols and infrastructure

I don't even know what this one is about...

And many, many more. Any self-respecting network engineer should be especially familiar with all April 1st RFCs, in my opinion...