Archive for the 'Foreign Policy' Category
Some of the usual suspects were there, Claude Berube, B. J. Armstrong and Dr. Martin Murphy – but there are many others who names presently may not be known to you, but whose papers will both inform and raise new questions for you to ponder.
The symposium goal:
To make sense of the relationship among maritime security, seapower, and trade, the EMC Chair will convene a symposium that brings experts from industry, the policy community, and the sea services. Participants will reflect on the importance of classic maritime thought and how changes in the shipping industry, trade patterns, and non-state use of the oceans impact future naval operations. The implications are important for understanding the types of missions combatant commanders will execute and the types of equipment and training the Navy must provide to support these missions. Keynote speakers will address the diplomatic and operational considerations of maritime cooperation.
Sure would like a webcast of these things . . . but without that, go read and enjoy.
Professor Anthony Clark Arend joins us to discuss International law. We discuss some basic definitions, and their influence on international actors, using the lens of Crimea and the Chinese ADIZ. I also learn later that my mic input has been the crummy laptop mic all month, explaining all my audio quality frustrations. Remember, subscribe on iTunes or Stitcher Stream Radio. Leave a comment and five stars!
Sea Control will be adding two monthly segments to its lineup: Sea Control Europe/Britain and Sea Control Asia-Pacific. We are joined by Natalie Sambhi of the Australian Strategic Policy Institute and Alexander Clarke of the Phoenix Think Tank. Today’s episode is a conversation with Nat and Alex about their backgrounds, their organizations, and their plans for their monthly series.
Sea Control discusses the Crimean Crisis, with three CIMSEC writers: Dave Blair, Viribus Unitis, and Robert Rasmussen. We discuss Russia’s aims and tactics, the Maidan movement, Ukrainian governance and passive resistance, and what this crisis means for Russia and the EU/NATO.
A. Denis Clift, former Naval Officer, president emeritus of the National Intelligence University, and Vice President for Operations of USNI, joins us to talk about his reflections on his time in the Antarctic, Cold War intelligence, life, and the United States Naval Institute. This is the first of a bi-monthly series that will be investigating his career during the Cold War.
Today’s extended episode is a chat on future threat projection with Dennis Smith of the Project on International Peace and Security from William and Mary, Chris Peterson of the Fletcher School’s Neptune Group, and Alexander Clarke of the Phoenix Think Tank. We talk about the next 5-10 years in maritime security, concentrating on global human security, china, and the economy. Please enjoy Sea Control 21- Threat Projection (download).
Remember, we are available on Itunes, Stitcher Stream Radio, and a bunch of other places my Google data can’t identify. Please, leave a comment and a five-star rating so we can get on the front page one day.
Benham Talebleu joins us to discuss Iran’s new President, their nuclear weapons program, and the larger strategic aims of the Islamic Republic. Remember to subscribe on Itunes or Stitcher Stream radio! Leave a comment and a five-star rating before telling all your friends.
Please enjoy Sea Control 19: Rouhani, Nukes, and Iran (download).
Lost to many whose news sources in the USA consists of the major newspapers and the standard networks, for most of the last dozen+ years, the conflict in Afghanistan has not been a USA-Centric battle; it has been a NATO run operation.
When the Commander of the International Security Assistance Force has been an American 4-star, the visuals can be misleading.
For most of the last decade, American forces were dominate in only one region of Afghanistan, the east. Other NATO nations from Italy/Spain in the west, Germany in the North, and Commonwealth nations and the Dutch in the south.
More important than the actual numbers involved, it was the Rules of Engagement, caveats, and the fickle nature of national politics that drove what effects those forces had on the ground.
The good, the bad, and the ugly of modern coalition warfare was all in view for all in Afghanistan, but outside small circles, has yet to be fully discussed.
Our guest for the full hour will be Stephen Saideman.
Stephen holds the Paterson Chair in International Affairs at Carleton University’s Norman Paterson School of International Affairs. He has written The Ties That Divide: Ethnic Politics, Foreign Policy and International Conflict and For Kin or Country: Xenophobia, Nationalism and War (with R. William Ayres) and NATO in Afghanistan: Fighting Together, Fighting Alone (with David Auerswald), and other work on nationalism, ethnic conflict, civil war, and civil-military relations. Prof. Saideman spent 2001-02 on the U.S. Joint Staff working in the Strategic Planning and Policy Directorate as part of a Council on Foreign Relations International Affairs Fellowship. He writes online at OpenCanada.org, Political Violence at a Glance, Duck of Minerva and his own site (saideman.blogspot.com). He also tweets too much at @smsaideman.
Join us live or pick the show up later by clicking here.
If you have had the pleasure of participating in coalition warfare you should find this interesting. If you haven’t, you might find it instructive.
James Bridger interviews adventurer extraordinaire, Rob Young Pelton, about his upcoming crowd-funded journey to find Jospeh Kony and further updates on the situation in Africa. Jim and Rob discuss civil wars, and piracy amongst others.
The episode finishes with an interview done on Federal News Radio, 1500AM, for their series “In Depth with Francis Rose.” Sean McCalley interviews our NEXTWAR Director, Matt Hipple, about his thoughts on what to watch in the coming year. They discuss Africa, China, drones, and informal military innovation/networks.
And remember… we are available on Itunes and Stitcher Stream Radio! Tell a friend, leave a comment, and rate 5 stars!
By Chap Godbey
This photo sort of looks like a ship, right? It is, but then again it’s also something else.
For this example, the vessel–an Iraqi patrol craft made by an American company and part of a U.S. foreign military sales contract–is not just one of the assets Iraq’s military needs to protect a very crowded and consequential waterspace. It’s also a multi-decade relationship, where both countries get to know each other on an operator-to-operator level as well as on other levels. That relationship can have strategic effects as the lieutenants become admirals, and the relationship builds trust, access, and communications paths outside the formal diplomatic process and regionally as well as bilaterally.
One of the patrol spaces this ship protects drives the entire country’s economy–the oil platforms and pipeline infrastructure–and its shipping. This is recognizable to a military planner, though the economic part takes a bit of wider thinking to understand how U.S. security cooperation fits into it with training and equipment. But let’s add something important on here: U.S. policy is to support Iraq’s reintegration into the region, and it’s a top foreign policy priority for the U.S. with regard to Iraq. The military sphere tends to be a bit easier in reconnection than some other spheres; navies, since they’re mobile sovereign territory in international waters, can be the fastest of those–especially when the U.S. is acting as an honest broker. To pull off that kind of multinational reintegration is not solely a military function, but can utterly depend on the military aspect. If the U.S. really wants a whole-of-Executive-Branch (much less whole-of-government) approach to a policy problem, DoD’s mass has to be subordinated to the overall effort, even when it might not necessarily make short term military sense.
The example above isn’t perfect. Security assistance in Iraq and Afghanistan has been far from the standard situation seen by a security cooperation office, and special authorities in the law made security cooperation in these countries much different than in other countries. A more forceful example would be where the host nation is paying for every penny of the asset, since feelings about “what ‘we’ are giving ‘them'” emotionally colors the discussion, and it’s worthwhile to emphasize that foreign military sales is not necessarily coming from the U.S. taxpayer. On the other hand, the nonmilitary effects of this ship and crew, and the regional effects of what this ship does and the separate bilateral relationships that navy has with regional navies and the U.S., are pretty clear and useful to bring out the challenge of thinking about security cooperation as more than arms sales or exercises.
Many folks seem to miss the nonmilitary and regional effects of the military-to-military relationship built out of security cooperation, or even that the process is heavily structured in U.S. law. This post about security cooperation misses important considerations about what security cooperation is and what it’s supposed to do (this one by the same author is better, though of different focus). A comment of mine on that War On the Rocks post identifies structural problems in the argument, and there are other opportunities for quibbling, but that post proves that it’s worthwhile to outline some basics of SC with a view towards those regional and extramilitary effects.
Security cooperation (SC) is not very familiar to most operators in the Department of Defense. SC’s a difficult skill set. SC can pay off not only as a force multiplier, but also to provide diplomatic effects which can be game-changing. DoD personnel may only experience SC once, as an exercise or engagement event, or by doing a tour that includes a collateral duty associated with foreign military sales (FMS). More experience is in the foreign area officer (FAO) commmunity, whose officers can wind up doing SC from several angles over multiple tours, but there aren’t many FAOs around. Because the skills needed are relatively obscure inside DoD, understanding of what SC is becomes fragmentary and often misses the point. American SC can suffer from that bad understanding. (The way U.S. government agencies in the Executive Branch staff and train for SC missions doesn’t help the problem, either.)
DoD isn’t the agency where SC initially gets defined—because SC is not solely a DoD mission; it’s a State mission for which Defense is the executive agent.
Let’s define some terms here. SC includes
- security assistance (SA), which itself includes
- foreign military sales (FMS) weapons sales,
- International Military Education and Training (IMET),
- a multi-page list of other programs that somehow fit or get shoehorned into the process, and
- security cooperation (Sc), a confusingly named subset of the bigger SC which mainly deals with exercise events with host nation or meetings between military personnel.
The first one, SA, is covered under federal law. (Note: IANAL and doing this off the top of my head.) U.S. Code Title 22 is the main law that covers diplomatic and consular functions and is for the Department of State what Title 10 is for DoD. The second part of security cooperation, the non-FMS part also called security cooperation, has rules under Title 22 but is more under a section of Title 10. That part of title 10 used is different from what you might expect, and it’s administered by personnel working under a different rule set than those under the full operational command of a COCOM. DoD personnel in country doing SC serve under the direction and supervision of the Chief of the United States Diplomatic Mission to that country (usually the U.S. ambassador to that country). Security cooperation, including security assistance, is a diplomatic function, under the Ambassador’s control in country. FMS cases and IMET and exercises have significant State Department approval and coordination–and additional coordination and approval by other agencies, and in some cases White House/Congressional approval–even though DoD has the mass and the executive agent role. The effect can sometimes be that the poor bureaucrat in the other agency is either like Horatius at the bridge or Niedermeyer in the riot, trying to get the massive influx of DoD people to go a different direction. It also can become counterintuitive, since American businesses might be fighting for the contract, or if one player–even a host nation–decides it’s worth lobbying for their interests more effectively to Congress than another player.
Note here that the Security Assistance Management Manual, the reference used in the War On The Rocks post, isn’t the controlling document. The law both trumps one agency’s manual and also highlights the diplomatic and interagency nature of SC. It also implies that the SC function is something we do as an ongoing and sustaining function of a country team, rather than something switched on once a COCOM has commenced large scale operations.
Since SC is a diplomatic function, one has to consider SC less like a military operation and more like a diplomatic operation. Results will be diffuse. They will have “one step forward two steps back” aspects. Results will be hard to measure in many respects. The effort will be like a coalition effort, with occasionally immense frustration on the ground and in the staff paying off strategically, but in different spheres than expected, or with effects long after the staffer is gone. For a planner looking for consistent positive results with a focused engineering-style goal oriented mindset this is anathema. A DoD planner or operator wants to get from point A to point B in a direct and uncluttered manner. Diplomacy, especially the work performed by Department of State colleagues on the country team on ground in country, is more chaotic and messy. If done right, SC advances the national interest of the United States; builds networks, access and relationships beneficial to the U.S.; eases stresses among and between partners; provides a common operating framework in the field; and provides a useful diplomatic tool as part of an embassy country team.
(Oh, by the way: There’s no Title 10 “command” in security cooperation organizations. There is no sheriff’s badge, no salad fork, no “forces”, even though the responsibility can weigh heavily, and DoD personnel could be in remote and dangerous locations. You’re a part of the embassy country team. There’s not even an organic Article 15 or medal-awarding authority, unless you’re a general for whom a COCOM has specifically delegated it in writing.)
For representatives of either agency to best advance U.S. national interest in the long term, both Defense and State have to be able to restrain some of their agency-level cultural impulses to achieve SC most effectively. Training, both in State’s A100 class for their newly commissioned officers, and at the Defense Institute for Security Assistance Management or similar venues for DoD personnel interacting with a country team, helps introduce the cultural difference to each agency. Other agencies with a hand in SC, such as the Departments of Commerce or Treasury, have a much smaller presence and make do with corporate knowledge and help from the larger groups interacting around them. (Homeland Security mainly interacts through Coast Guard personnel, who are more acquainted with DoD’s foibles and when in theater interact often with country teams with and outside the security cooperation office in the embassy.) Some aspects can cause real friction without planners realizing its source, such as when a J5 officer assumes there’s a J5 in State, or that a Post’s plan is written with the same process as DoD’s, or that the plan is followed as closely as a DoD plan would be. On the ground, people on the country team have to make it work through force of effort and personality.
The benefits of SC have national influence, not just military, from public affairs/public diplomacy to changing policies in a country. SC also has a regional influence: in the ability to use the U.S. effort as a go-between between two partners unhappy with each other, in the ability to build regional ties with the U.S. invited to play, and in the ability to influence regional decisions based on a calculation from a nation that has to deal with what the U.S. has done in the neighborhood. It could well be that host nation has no culture of maintenance and the equipment they paid for is failing. It could be that the country’s using the military to dispense largesse domestically, and the U.S. interest in improving capacity isn’t perfectly aligned with that national desire. It could be that there’s a Red Queen effect, where the security cooperation guys are running as hard as they can to stay in place capacity-wise. It could also be that those frustrating efforts pay off in unusual ways. The military planner will do well to reach out to those other American agencies, to actually listen and adjust planning based on that reaching out, to see the role of SC as more than military capacity building, and to plan for a long and difficult but rewarding SC effort.