1. A central server is required as the one which is stored on fully backed up storage. (yeah yeah, DVCS means there's a copy on everybody's desktop. All in the same building. Real backups are off site)
2. developers can't make a mess of the repository metadata. (On lkml Linus sometimes tells developers that he won't pull because the history is in a mess - but without a single gatekeeper you can't assume that none of the developers with commit rights won't introduce such a mess)
3. Svn authentication is delagated to the owners of the repository, it doesn't require sysadmins to get involved tweaking UNIX groups.
4. Svn provides the means to automatically check commits on the server, so eg all commit messages have a bug tracking number, changes conform to the coding standard, whatever)
5. Svn works properly on windows.
6. Svn can represent empty directories. AFAIK git can't.
It's nothing fundamental, but calling FUD and trying to tell svn users that the svn features they use and git/hg/bzr/etc don't have are useless is a waste of everybody's time. It would be great if somebody could set up the tools to support a corporate environment while also exploiting the advantages of a dvcs