09.01.2015 Views

spartans_in_darkness

spartans_in_darkness

spartans_in_darkness

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

=rell SEe~E=rh'eeMItHt'lX1<br />

Americans. These products were available at the<br />

time of the composition of the chronology. Yet<br />

why they were not <strong>in</strong>cluded is unknown.<br />

Obviously, their absence leaves the reader with<br />

the impression of Hanoi's overt aggression<br />

aga<strong>in</strong>st the American ships.<br />

(~//~I) The way the material is presented is<br />

also curious. Almost all of the SIGINT product<br />

<strong>in</strong>cluded for both 2 and 4 August has attached the<br />

reproduction of the orig<strong>in</strong>al <strong>in</strong>tercept of the DRV<br />

navy's messages: that is, the cipher and its<br />

decrypted Vietnamese text. This allows the reader<br />

to see the unfold<strong>in</strong>g of the SIGINT process,<br />

from <strong>in</strong>tercept to report.<br />

(S//8I) However, there is one glar<strong>in</strong>g exception<br />

to this: the 4 August translation of the socalled<br />

"after-action" report used by Secretary<br />

McNamara and President Johnson as primary<br />

evidence of the attack. In fact, only the translation<br />

is <strong>in</strong>cluded, and it is there only as "a sample."<br />

Consider<strong>in</strong>g the importance attached to it by the<br />

adm<strong>in</strong>istration, as we saw earlier, this is a very<br />

odd way of present<strong>in</strong>g this piece of critical<br />

evidence. It would seem that the NSA orig<strong>in</strong>ators<br />

of the chronology would have added the complete<br />

cipher and Vietnamese text to bolster the case<br />

for an attack. Yet the translation stands alone.<br />

S<strong>in</strong>ce we know that the <strong>in</strong>tercept used to produce<br />

the translation currently is miss<strong>in</strong>g, might we<br />

ask if they were already "miss<strong>in</strong>g" shortly after<br />

the <strong>in</strong>cident itself and the composition of the<br />

chronology<br />

(S//S1) F<strong>in</strong>ally, the chronology does not<br />

address the problem of the total lack of<br />

North Vietnamese C3I related to the supposed<br />

4 August attack. Not surpris<strong>in</strong>gly, there are samples<br />

of the C3I from the 2 August attack. Yet,<br />

aside from the so-called "attack" message and the<br />

purported "after-action" report, there is noth<strong>in</strong>g<br />

for 4 August. We have commented on this before.<br />

The argument that the material may not have<br />

been available <strong>in</strong> early August might have had<br />

some slight relevance. The chronology might<br />

have been the vehicle for address<strong>in</strong>g this shortcom<strong>in</strong>g.<br />

However, fully two months later, there is<br />

still noth<strong>in</strong>g <strong>in</strong>cluded of the enemy's C3I - the<br />

huge gap is not addressed, much less expla<strong>in</strong>ed,<br />

by NSA.<br />

(Sl/Sf) Over the years, the chronology came<br />

to be the source book for responses to congressional<br />

<strong>in</strong>quiries <strong>in</strong>to the Gulf of Tonk<strong>in</strong> <strong>in</strong>cidents.<br />

That is, the other 90 percent of related SIGINT<br />

product was not offered to any congressional<br />

<strong>in</strong>vestigat<strong>in</strong>g committees. Instead, the chronology<br />

became, by virtue of its position as an "official"<br />

report, the only source for background on the<br />

Gulf of Tonk<strong>in</strong> <strong>in</strong>cidents.<br />

(T~//~I) The first <strong>in</strong>vestigation came <strong>in</strong> early<br />

1968 when the Senate Foreign Relations<br />

Committee, under the chairmanship of Senator<br />

William Fulbright, who had steered the Gulf of<br />

Tonk<strong>in</strong> Resolution through the Senate, opened<br />

hear<strong>in</strong>gs on the <strong>in</strong>cident. Secretary of Defense<br />

Robert McNamara was called <strong>in</strong> to testify. Prior<br />

to his testimony, he requested that the pert<strong>in</strong>ent<br />

COMINT on the <strong>in</strong>cidents be given to him. The<br />

NSA and the Defense Intelligence Agency were<br />

reluctant to have the SIGINT used; both agencies<br />

were fearful that the exposure would compromise<br />

the then current capabilities aga<strong>in</strong>st the North<br />

Vietnamese.V" Ultimately, Secretary McNamara<br />

was given the contents of the chronology, as was<br />

the Senate committee as well. The result<strong>in</strong>g hear<strong>in</strong>gs<br />

did noth<strong>in</strong>g to clear up the confusion.<br />

McNamara argued for the attack, cit<strong>in</strong>g the various<br />

SIGINT reports, though he seemed to mix up<br />

what was <strong>in</strong> them, and left observers sometimes<br />

confused.F" Many senators, look<strong>in</strong>g at the same<br />

chronology, rema<strong>in</strong>ed skeptical.<br />

(Sl/Sf) In August 1975, the Senate Select<br />

Committee on Intelligence, under the chairmanship<br />

of Senator Frank Church of Idaho,<br />

approached NSA about the Gulf of Tonk<strong>in</strong> <strong>in</strong>cident.<br />

The committee's <strong>in</strong>terest, though, may not<br />

have been <strong>in</strong> establish<strong>in</strong>g the validity of the <strong>in</strong>cident;<br />

their attention was focused on <strong>in</strong>formation<br />

Page 218<br />

'fOP SE6REli','60MIN'Fh'*1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!