October 20, 2014--Operation Hesitation
Since Desert Shield (our war with Iraq to expel Saddam's army from Kuwait), Desert Storm (George H.W. Bush's war with Iraq), and Iraqi Freedom (George the Son's preemptive invasion of Iraq to finish the job he felt Daddy left unresolved)--I've been curious why our wars need names.
What's wrong with World War I, World War II, or the Korean War? Did our war in Vietnam have or need a name other than the Vietnam War? These seem descriptive enough.
Yes, various operations in wars since at least WW II had names--Overlord is perhaps best known. It was the code name for the allied invasion of Normandy, culminating on D-Day, June 6, 1944.
In truth the invasion didn't need a code name. Everyone who cared knew forces for a massive invasion were gathering in England. And no one was fooled by wondering what this Overlord was about. The Nazis knew the allies were coming. The most important thing they didn't know was where the cross-Channel invasion would occur, and having a code name didn't do anything to help hide the specifics of the plan. For some reason Eisenhower must have liked the feudal sound of Overlord. Perhaps that's how he regarded himself.
Come to think of it, why was June 6th called D-Day? Wiki says all invasion have d-days with the "d" standing for day or date. Get it? Nothing special.
But in regard to Operation Inherent Resolve, according to the New York Times, for three months the Pentagon has been hassled by the press to come up with a name for the bombings and drone attacks we have been inflicting on the Islamic State (or ISIS or ISIL).
Secrecy is not an issue otherwise the Pentagon wouldn't have shared the eventual code name with the waiting world--
The name Inherent Resolve is intended to reflect the unwavering resolve and deep commitment of the U.S. and partner nations in the region and around the globe to eliminate the terrorist group ISIL and the threat they pose to Iraq, the region and the wider international community.There was no concurrent mention of the fact that one key "partner nation," Turkey, geographically in the middle of the fighting, has thus far not only refused to become involved but has impeded our efforts, in effect holding us up for ransom--there will be no Turkish involvement, they say, until the U.S. agrees to directly support rebels fighting to overthrow Syrian president Bashar al-Assad.
Under pressure from the press I can just imagine the high-level discussions that went on for three months in the Pentagon and White House Situation Room while struggling to come up with an appropriate name for the operation.
"How about Operation Isolation?" the Chairman of the Joint Chiefs of Staff offered, all puffed up.
"I like that sir," his adjunct chimed in. "It's clever. Even includes a pun. ISIL, isolation. If I may say so, sir, very clever."
"This is a nasty business. No place for puns," growled the Chief of Naval Operations. "My boys are flying dangerous missions and--"
"Sorry to interrupt Chief," the Army Chief of Staff interjected, "But that's boys and girls." He sat back in his leather chair, self-satisfied, smiling.
"Correction accepted," conceded the Chief of Naval Operations. "We do have some wonderful gals flying those planes. Lives at risk. Just like the boys. Times have changed"
"How about Operation Hesitation," chuckled the Commandant of the Marine Corps. His colleagues glared at him. "You know, the CIC [Commander in Chief] was hesitant to get involved with those ISIS-ISIL folks. It's another quagmire. We all know that. he got beat up in the press pretty bad for indecision. Had to have those fellas' heads cut off before he got his ass in gear." No one made eye contact.
"Not that I blame him. Been there, done that. So maybe for once we should come up with one of these names--why we even need them I'll never know--that tells it like it is. Operation Hesitation could be the first." He puffed on his unlit pipe.
"Yeah, and we should have called Iraqi Freedom Operation Slam-Dunk," said the Vice Chair, all agitated.
"Or," offered the Commandant of the Coast Guard, "Operation Preemption," getting in on the act.
"Let's get serious guys. That's not going to fly," the Chairman admonished his colleagues, "We have to come up with something he'll go for. That suits him. You know, something academic sounding. A name with class." He rolled his eyes, feeling he had more important things to do.
"I have it," exclaimed the Chief of the National Guard, "How about Operation Enduring Resolve?"
"Huh?"
"I'm liking this," the naval commandant said, "The resolve part especially. Very Marine. Like Sempre Fi, but in English. Like it. Licking it."
"Your boys aren't even involved," the Chief of Naval Operations pointed, "No boots on the ground this time around. At least that's what he said. Just Mark's flyboys and my guys. And by guys I mean guys and gals of course." He winked.
"But I'm not liking the enduring business," the Chairman said, "Feels ominous to me. If I take your meaning it sounds like we'll be at this forever. I mean, if it's enduring. I'm not sure we'll be able to sell that."
"Good point. So how about inherent?" the Chief asked, "We want to indicate we're taking this seriously, that it's not going to be a slam-dunk. Going to take some time."
They all seemed to like that.
"I'll pass it along," the Chairman said, "Let's run it up the flagpole and see if it flies."
The rest is history. Or will be history.
Labels: Chairman of Joint Chiefs of Staff, Commander in Chief, Iraq, ISIL, ISIS, Islamic State, Joint Chiefs of Staff, Korean War, Operation Inherent Resolve, Overlord, Syria, Vietnam War, World War I, World War II
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home