Username Password



Obama's high-risk Afghan plan

The proposed troop increase will intensify the conflict, but whether it will quell the insurgency is questionable, says Ayesha Khan

One large step: the commander-in-chief on December 1 announced the second Afghan "surge" of his term. Photograph: US Army/Tommy Gilligan

President Obama has finally made a decision: he has called for 30,000 more US troops to be deployed to Afghanistan to "finish the job" and "bring a successful conclusion to the war". This is one of Obama’s most important foreign policy decisions. It comes after months of deliberation and a painstaking consultative process. Yet for those who expected a paradigm shift, the outcome to this much-anticipated and long-awaited announcement has been an anti-climax.

For the president has not reconfigured US military engagement with Afghanistan. He has simply backed General McChrystal’s request for more troops and reaffirmed his commitment to a military strategy that has been under discussion and in the pipeline since before his inauguration. The narrowly defined military objective is to "disrupt, dismantle and defeat al-Qaeda" in Afghanistan and Pakistan.

The troop count is where the Obama administration diverges from its predecessor. President George W Bush took a "light footprint" approach, deploying few troops in places far apart. This failure in strategy is now being blamed for having missed the opportunity to quell the then nascent insurgency at the outset. Despite this, Afghanistan has been susceptible to mission creep. It witnessed a gradual but steady increment in troop numbers throughout the Bush administration – and now a jump in numbers under the Obama administration.

Obama is not giving General McChrystal the 40,000 extra soldiers he requested. But with a contribution of troops from other NATO allied countries – the total number is likely to meet McChrystal’s requirements to wage the desired counter-insurgency war being articulated. This will bring the number of troops in Afghanistan to more than 100,000 – reminiscent of the numbers present during the Soviet occupation in the 1980s.

Whether this troop surge will quell the insurgency is questionable. Early indications from the first increase of 21,000 soldiers announced earlier this year point to an exacerbation and escalation of violence, with military fatalities and civilian casualties reaching record high levels. The jury is still out on the impact of this troop surge, as military operations are ongoing. But more troops are likely to lead to an intensification of the war and a further militarisation of the Afghanistan-Pakistan border region. It is a high-risk, high-stakes strategy.

This troop surge is framed within an exit strategy. Obama wants a rapid deployment by early 2010 to "reverse the Taliban momentum", before handing over responsibility to Afghan forces and starting the withdrawal of US troops by July 2011. The president has made clear that the Afghan government needs to play its part in tackling the Taliban on its border. It is setting out plans to train quickly large numbers of the Afghan army to take over the fight, but this is not without its difficulties. The high rates of attrition, ethnic imbalances, and poor fighting capabilities of the Afghan army could undermine the counterinsurgency effort.

The number of troops, both Afghan and US/NATO, has become a defining factor in Obama’s "AfPak" strategy. The more important issue, however, is what these troops will do on the ground: how effective a counter-insurgency strategy they are likely to implement and how their increased presence is received by war-weary Afghans. It is these factors that will determine the future course and conduct of the war and how quickly US/NATO troops are able to enter into and then extricate themselves from the AfPak conflict.

As the current strategy plans for a surge and then an exit from Afghanistan, it inextricably links any successes there with Pakistan. It also points to the importance of tackling al-Qaeda and foreign militancy in Pakistan’s tribal belt. Conflating the two separate but parallel conflicts into one existential threat further complicates any exit strategy from the Afghanistan-Pakistan border region. It will take a well-formulated approach, not primarily determined by the troop surge, to tackle the Taliban on both sides of the Durand line.

02/12/2009

Comments

Share |
Comments
Name :
Message :






eZ debug

Clear cache:

Quick settings:

Notice: eZMySQLDB::query(0.000 ms) query number per page:0 Mar 12 2010 19:07:37
SET NAMES 'utf8'
Timing: Mar 12 2010 19:07:37
Module start 'content'
Timing: Mar 12 2010 19:07:37
Module end 'content'
Error: eZTemplate Mar 12 2010 19:07:37
Cannot retrieve attribute of a string
Warning: eZTemplate:def Mar 12 2010 19:07:37
Variable 'article_node' is already defined.
Timing: Mar 12 2010 19:07:37
End

Timing points:

CheckpointElapsedRel. ElapsedMemoryRel. Memory
Module start 'content' 0.0000 sec0.0895 sec 890.4102 KB273.9727 KB
Module end 'content' 0.0895 sec0.6444 sec 1,164.3828 KB4,639.5625 KB
End 0.7338 sec  5,803.9453 KB 
Total runtime:0.7630 sec
Peak memory usage:6,437.5039 KB

Time accumulators:

 Accumulator Elapsed Percent Count Average
ini_load
Load cache0.0424 sec5.1814%120.0035 sec
FindInputFiles0.0354 sec4.3200%120.0029 sec
Mysql Total
Mysql_queries0.0615 sec7.5110%720.0009 sec
Looping result0.0069 sec0.8441%720.0001 sec
Template Total0.6642 sec 81.1% 2 0.3321 sec
Template load0.0248 sec3.0273%20.0124 sec
Template processing0.6392 sec78.0512%20.3196 sec
Template load and register function0.0024 sec0.2891%10.0024 sec
override
Cache load0.0205 sec2.5092%140.0015 sec
Sytem overhead
Fetch class attribute name0.0052 sec0.6374%20.0026 sec
class_abstraction
Instantiating content class attribute0.0001 sec0.0065%20.0000 sec
General
String conversion0.0000 sec0.0023%10.0000 sec
dbfile0.2245 sec27.4124%120.0187 sec
Total script time:0.8189 sec

Templates used to render the page:

Usage countRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>design/esharp/templates/pagelayout.tplEdit templateOverride template
1content/datatype/view/ezstring.tpl<No override>design/standard/templates/content/datatype/view/ezstring.tplEdit templateOverride template
1node/view/li.tpl<No override>design/sydesy/templates/node/view/li.tplEdit templateOverride template
1content/datatype/view/ezobjectrelationlist.tplarticle/jargon/list.tpldesign/esharp/override/templates/article/jargon/list.tplEdit templateOverride template
1setup/debug_toolbar.tpl<No override>design/sydesy/templates/setup/debug_toolbar.tplEdit templateOverride template
      
 Number of times templates used: 5
 Number of unique templates used: 5
 Time used to render template usage: 0.0006 secs