Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Privacy

+ - Germany just decided to implement data retention-> 3

Submitted by
G'Quann
G'Quann writes "Starting next year, all communication providers in Germany will have to store all connection data for six months. This includes not only phone calls but also IP-addresses and e-mail headers. There had been a lot of protest against the new law, but it was ignored by the government. This sucks...

Here's a short summary with links to more detailed (but German) sources."

Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Germany just decided to implement data retention

Comments Filter:
  • Beyond all the legal/privacy issues, just how much storage would be necessary to archive six months of phone calls AND other communication? The costs seem like they'd be tremendous. Time to buy stock in Seagate?
    • by G'Quann (237134)
      It's not intended to store the content of the communication. Just the connection data, in the style of "x called y on 1.1.2009 1:23 for 24 minutes".

      Nevertheless, it requires some storage space. Communication providers also complained a lot about this bill. Just imagine the amount of e-mails sent every day (including spam). Even if you store only the connection data (header), it'll probably add up to quite a bit.
      • by rekoil (168689)
        Beyond the phone call logging, the requirements to log every IP connection is a HUGE burden. Effectively, every access router would have to export Netflow or sFlow data, or mirror traffic to an analysis device for logging. I work for a large ISP, and we do Netflow accounting today, but only for aggregate traffic analysis - for example we can know at any time how much traffic is going to a particular destination. We also turn on "sample" mode, which only reports data for a small percentage of the traffic goi

If you don't have time to do it right, where are you going to find the time to do it over?

Working...