IANA has recently allocated 1.0.0.0/8 to APNIC, which hascaused a certain amount of concern that it is 'polluted' bypeople already using it for various reasons. Pollution in 1/8 is a report from RIPE Labson what happened when they announced routing for some bits of it as partof their debogonising work .

This is clearly going to be what they call 'interesting'.

(via Hacker News .)

Here is one of the less obvious perils of outdated documentation:

Suppose that you have some documentation that is out of date, but not inan obvious way; for example, you have an out of date network layoutdiagram . Since it's not obvious you don'trealize this right away, so you keep on updating the network layoutdiagram when you make changes to your actual network.

Except that faithfully updating an inaccurate network layout diagram isrelatively pointless. When you realize that it is incorrect, you are

The obvious traditional risk of outdated documentation in all its formsis that you rely on it and go wrong somehow; you trust the comments inthe source code and write your new code accordingly, and your changesdon't work. I think that this risk is especially acute for sysadmins,for two strongly related reasons.

First, much of our documentation tends to be about procedures, notsimple information. Following what is actually a wrong or incompleteprocedure is a great way to create spectacular failures on the spot.Worse