Question, from an ignorant civilian perspective...
Given the extensive and negative publicity that has been drawn by actual or alleged civilian casualties from air strikes, and given the very public nature of the announcement under discussion here, is it possible that the announcement is aimed less at altering the tactical environment on the ground than at creating or reinforcing a perception of a shift away from the use of air power in environments where civilian casualties are likely?
I have no doubt that Gen. McChrystal wants and intends to reduce collateral damage, but I'm sure he also wants everyone in the picture to be aware of this intention. When a change like this is announced in the mass media before the new rule is even released, it suggests to me that there's a strong "for popular consumption" factor in the picture.
I would certainly agree with those here who point out that if the JDAM is option A and running away is option Z, consideration needs to be given to the options in between - with full awareness that options are restricted by circumstances.
Probably why I said this:
"...The 'change' as understood thus far is cosmetic -- it attacks the symptom, not the problem. I do not question the need for him to do that; I do strongly question WHY he should have to do that..." (emphasis added / kw)
Quote:
Originally Posted by
Tom Odom
Well said and I agree with all but would say in a case where the alligators have us by the ass we need to pass on draining the swamp. McChrystal has got to start somewhere, quickly.
It also seems you are corroborating my point that this is a bandaid and that we are attacking a symptom... ;)
Not sniping at you but I think this all too pervasive general idea and attitude "...where the alligators have us by the ass we need to pass on draining the swamp." is endemic in the Army, more so today as it has been increasing in intensity for over 20 years and that it is exactly why we are where we are in a great many respects.
We have a bad tendency today to put out fires instead of removing the combustibles that allow such fires. People acquire credit and gratification from 'fixing' things that are wrong -- and being seen to do so...
Few seem willing to put in the hard thankless effort required to change the direction of the elephant. That attitude is dangerous and is not good for the long term health of the institution -- or the nation.
I'd like to amend something I said earlier: "...that he has to do so is an indicator of institutional failure. The institution really needs to acknowledge that. Append: and fix it before it gets worse..."
ROE vs RUF - Good point ....
Quote:
from Cavguy
As a final note, although this thread started with the title ROE, we are really talking RUF - Rules for use of Force, which can be more restrictive than ROE. ROE in a legal way hasn't changed, and doesn't really cover specific weapons systems. It's more general. GEN McChrystal is changing the theater guidance for RUF. There is more than a semantic difference.
JP 1-04 (pp.73, 72):
Quote:
rules of engagement. Directives issued by competent military authority that delineate the circumstances and limitations under which United States forces will initiate and/or continue combat engagement with other forces encountered. Also called ROE. (JP 1-02)
....
rules for the use of force. Directives issued to guide United States forces on the use of force during various operations. These directives may take the form of execute orders, deployment orders, memoranda of agreement, or plans. Also called RUF. (JP 1-02)
Explanatory article, ROE vs RUF in Marine Corps Gazette (linked from SWJ Library).
Quote:
Because RUF generally assume a nonhostile host with a generally friendly population, RUF primarily focus on using force in self-defense as a matter of force protection based on mere presence—rather than an assigned operational mission—or using force in the exercise of a very limited law enforcement or security mission. ROE policy concerns tend to focus on relations with foreign actors and furthering international political objectives. RUF policy concerns tend to focus on domestic or host-nation political objectives and domestic or host-nation public opinion.
I find the distinction between ROE (in foreign ops) and RUF (in domestic ops) to be pretty straight-forward. Where the two are both programmed into the same operation (as JP 1-04 allows or requires ?), I understand the definitions ("will" vs "guide" ?), but do not really understand the possible implementations.
ROE vs RUF - added sources
I think MAJ Smith has revealed to us a real legal can of worms - as well as a project for education and training of soldiers that is beyond me.
Current SROE/SRUF and consequent ROE/RUF date from the complete 2005 overhaul of that system of rules. The changes are described, with various problem areas highlighted, by Major Daniel J. Sennott, Interpreting Recent Changes to the Standing Rules for the Use of Force, Nov 2007, The Army Lawyer DA PAM 27-50-414, pp.52-78.
MAJ Sennett sums the distinction between the SROE/ROE family and the SRUF/RUF family as follows (pp.52,53; footnotes omitted here - see original for extensive footnotes):
Quote:
The Department of Defense (DOD) released the current Standing Rules for the Use of Force (SRUF), dated 13 June 2005, in early July 2005. These rules are drastically different from prior versions. Both the format and the language have changed, but probably the most important modification is the addition of new terms and definitions. While some of the modifications serve to simplify the SRUF, other modifications may not be as favorably received. The SRUF, which are designed for use in the United States, and therefore based on domestic law, now include language that is identical to the Standing Rules of Engagement (SROE), which are rooted in international law. As a result, the potential for confusion in application of these two distinct sets of rules may be significant.
....
The DOD defines rules for the use of force as “[d]irectives issued to guide United States forces on the use of force during various operations.” This rather general definition is further augmented by the definition contained in the current SRUF: Standing Rules for the Use of Force “establish fundamental policies and procedures governing the actions to be taken by U.S. commanders and their forces during all DOD civil support and routine Military Department functions occurring within U.S. territory or U.S. territorial seas.”
Perhaps the best way to define SRUF is in the negative: SRUF are not SROE. The SROE “establish fundamental policies and procedures governing the actions to be taken by U.S. commanders and their forces during all military operations and contingencies . . . occurring outside U.S. territory . . . and outside U.S. territorial seas.” Although SRUF and SROE share some common principles, SRUF are based on domestic law, while SROE is largely based on international law. Therefore, any definitions and concepts contained in RUF must be rooted in the U.S. Constitution and domestic laws.
Not a doubt exists that the primary doctrinal use of the SRUF/RUF family was intended to be in domestic operations within the US.
That having been said, Niel is entirely correct in saying that the SRUF/RUF family can be used outside of the US without violation of doctrine. The Clamo article in the Marine Gazette expressly says that (e.g., references to "host nation", etc.). The 2008 Operational Law Handbook, chap 5, lays out the state of SROE/ROE and SRUF/RUF as its CLAMO authors saw it. Whether a specific extension of SRUF/RUF to a foreign operation is wise or not is not an issue for lawyers, military or civilian - it is a command decision.
The combo of SROE/ROE and SRUF/RUF is, to say the least, complicated. Can this combo result in the end state defined by Jon Custis:
Quote:
I don't view ROE as ironclad, nor do I view them as restrictive. Fail to train your troops properly in their execution, and they can be. For the most part they are permissive from my experience.
especially re: his "to train your troops properly in their execution" ?
It is not within my expertise to suggest education or training methods; but unless there is adequate education and training, all this complexity (add EOF - Escalation of Force to the mix) promises to become a mess (IMO).
It is within my expertise to wonder what the Federal courts will do with this. For the past 9 months, the DC District and DC Circuit have been deciding detainee cases based on a strict AUMF-LoW (LOAC) standard. As such, they have accorded NO constitutional rights to detainees other than a limited habeas right; at most, releasing them into the diplomatic custody of the US for possible future OCONUS transfer.
It will be interesting to see what SCOTUS will do with the concept that "definitions and concepts contained in RUF must be rooted in the U.S. Constitution and domestic laws" when SRUF/RUF are applied to Astan. I haven't the foggiest WAG as to whether the U.S. Constitution and domestic laws will become applicable to Astan as a consequence.
----------------------
As further support for Niel's legal position (that SRUF/RUF can be applied), JP 1-04 (cited in my prior post) allows - but does not require (that being a command decision as I interpret it) - use of SRUF/RUF in the Course of Action Development process, across a very broad spectrum:
Quote:
(pp.32-33)
(b) The joint force SJA reviews other staff section proposals for legal sufficiency. As an example, the joint force SJA assists other staff elements (typically the operations directorate of a joint staff [J-3] or the plans directorate of a joint staff [J5]), in determining whether the standing rules of engagement/standing rules for the use of force (SROE/SRUF) are sufficient to accomplish the mission, and, if not, which supplemental ROE/RUF measures are needed and why. The joint
force SJA should consider and assist other staff elements in considering, for example, whether and
under what circumstances the JFC should request or authorize the following: authority to declare forces as hostile (who and under what circumstances); use of riot control agents, offensive operations, and cross border operations; and use of all necessary means during special operations, collective self-defense (defense of non-US persons and property), beyond visual range engagement of airborne objects, exercise of national self-defense, use of wartime reserve modes, training or spotlighting with a directed energy weapon, collateral damage (LOAC-standard or minimum possible), attacking space assets, computer network attack, destruction of designated lines of communications or facilities, destruction of designated major supplies or resources, and detention of civilians. Other areas that require review include detention and interrogation operations, treatment of civilians, integration of contractor personnel, and intelligence operations.
Public Nature of the Directive
Quote:
Originally Posted by
lobo
The one thing that gets me is how widespread this information is, part of the way to win any conflict (or battle) is to deny the enemy information on our tactics and battle plans. Announcing to the world (and the enemy) what we will or will not do in a situation is just asking for some "smart" opponent to use this against our troops.
my other point to be made is how this can be confusing to anybody on the ground (or air), the last thing we need is for the troops and/or leaders to start second guessing themselves (or third....) for concern on how their action will be view by others.
just my two cents to a interesting thread
*plink, plink*
Lobo
Call me naive, but...
If you presume that the enemy will read this traffic... and that the enemy will then tend to fuse itself in large numbers to population centers in order to leverage a perceived seam in NATO/US RUF...
Maybe, just maybe... that is part of the design of the public release... in addition to assauging some Afghan sensibilities, perhaps a second order effect of the the wide spread release of the directive is exactly so the adversary will read and respond as mentioned above...
A significant problem in dealing with non-compliant forces in AFG is exactly the fact that after getting some "sch-onion" laid upon them in 2001, that got smart and stopped "pooling" into targetable entities...
Of course that's just a wag... stranger things etc etc etc
Time to make the donuts