State secrets

It’s common knowledge that companies that provide access to the internet cooperate with law enforcement. The telephone companies have always been closely tied to emergency responders and the police — in times of need, people reach for telephones, and this close cooperation has allowed many rescuers to reach panicked callers. But the cooperative relationship springing from law enforcement’s surveillance needs is just as close.

In the NSA spying scandal, the administration has frequently claimed that to reveal the nature of network providers’ involvement with the apparently unlawful wiretapping would reveal secrets - and therefore this relationship can’t even be discussed in court. Now the director of national intelligence, Mike McConnell, is admitting that “the private sector” (the network operators) did indeed help out:

Now the second part of the issue was under the
president’s program, the terrorist surveillance program, the private
sector had assisted us. Because if you’re going to get access you’ve
got to have a partner and they were being sued. Now if you play out the
suits at the value they’re claimed, it would bankrupt these companies.
So my position was we have to provide liability protection to these
private sector entities.

And McConnell also says that people will die because we’ve been so public about our discomfort with this illegal wiretapping program.

It’s all pretty rich.

Q. So you’re saying that the reporting and the debate in Congress means that some Americans are going to die?


A. That’s what I mean. Because we have made it so public. We used to do these things very differently. . .

Comments

One Response to “State secrets”

  1. Anonymous on August 27th, 2007 12:14 am

    State secrets…?
    As a so-called ICANN Director (non-elected and planted by Esther Dyson and others) here are some cyberspace topics/questions you may want to spend more time on. [It appears that 99.9% of your topics are meat-space related and almost 100% of ICANN processes are meat-space oriented. Why is that ?]
    1. It is common knowledge that Netizens connect to the 32-bit legacy transport using 32-bit Address Spectrum.
    2. Address Spectrum is very similar to other spectrums commonly managed (in the US) by the FCC.
    3. People motivated by selling new protocols, technology, and religious agendas are currently running around cyberspace claiming that they will soon no longer have any more “virgin” Spectrum to lease. [They make sure people do not notice the 10s of millions of dollars they have banked, which now allows them to retire for the next 20 years.]
    4. A quick review of the 32-bit Spectrum shows that 50 of the 250 major allocations remain RESERVED. That is about 20%. Has the ICANN Board reviewed how well the other 80% is used ?

    Q1. What are those 50 Spectrum blocks RESERVED for ?
    Q2. What is the defined FAIR and OPEN process to obtain one or more of those Spectrum blocks ?
    Q3. What do companies pay ICANN per year for such Spectrum blocks ?
    Q4. How many, so-called, ICANN Directors know anything about Spectrum, the value of Spectrum, or about US FCC Spectrum Auctions ?
    Q5. Is the intention to make all of the Spectrum blocks below, Public Spectrum?
    Q6. Is it possible that so-called ICANN Directors “distract” people to meat-space topics to avoid dealing with cyberspace topics ?
    Q7. Is it true that the New ICANN Spin, for 2008, is that ICANN only does names, not addresses ?
    Q8. Is it also true that the New ICANN Spin is that all of the inter-locking of the same people profiting from names and addresses is “Pure Coincidence”, and was not some small clique's intended result ?
    Q9. Is it true that the recent secret meetings in Aspen resulted in agreement that the US FCC will handle Spectrum Allocations ?
    Q10. Is it true that the US FCC plans to immediately out-source that Spectrum Management to one of the Northern Virginia spook companies that was home-grown by ICANN to handle such matters ?

    000/8 Sep 81 IANA - Reserved
    001/8 Sep 81 IANA - Reserved
    002/8 Sep 81 IANA - Reserved
    005/8 Jul 95 IANA - Reserved
    007/8 Apr 95 IANA - Reserved
    010/8 Jun 95 IANA - Private Use A.NET
    014/8 Jun 91 IANA - Public Data Network E.NET
    023/8 Jul 95 IANA - Reserved
    027/8 Apr 95 IANA - Reserved
    031/8 Apr 99 IANA - Reserved
    036/8 Jul 00 IANA - Reserved
    037/8 Apr 95 IANA - Reserved
    039/8 Apr 95 IANA - Reserved
    042/8 Jul 95 IANA - Reserved
    046/8 Dec 92 IANA - Reserved
    049/8 Mar 98 IANA - Reserved
    050/8 Mar 98 IANA - Reserved
    100/8 Sep 81 IANA - Reserved
    101/8 Sep 81 IANA - Reserved
    102/8 Sep 81 IANA - Reserved
    103/8 Sep 81 IANA - Reserved
    104/8 Sep 81 IANA - Reserved
    105/8 Sep 81 IANA - Reserved
    106/8 Sep 81 IANA - Reserved
    107/8 Sep 81 IANA - Reserved
    108/8 Sep 81 IANA - Reserved
    109/8 Sep 81 IANA - Reserved
    110/8 Sep 81 IANA - Reserved
    111/8 Sep 81 IANA - Reserved
    112/8 Sep 81 IANA - Reserved
    113/8 Sep 81 IANA - Reserved
    114/8 Sep 81 IANA - Reserved
    115/8 Sep 81 IANA - Reserved
    173/8 Apr 03 IANA - Reserved
    174/8 Apr 03 IANA - Reserved
    175/8 Apr 03 IANA - Reserved
    176/8 Apr 03 IANA - Reserved
    177/8 Apr 03 IANA - Reserved
    178/8 Apr 03 IANA - Reserved
    179/8 Apr 03 IANA - Reserved
    180/8 Apr 03 IANA - Reserved
    181/8 Apr 03 IANA - Reserved
    182/8 Apr 03 IANA - Reserved
    183/8 Apr 03 IANA - Reserved
    184/8 Apr 03 IANA - Reserved
    185/8 Apr 03 IANA - Reserved
    186/8 Apr 03 IANA - Reserved
    187/8 Apr 03 IANA - Reserved
    197/8 May 93 IANA - Reserved
    223/8 Apr 03 IANA - Reserved

Got something to say?