|
Red Move 3: Year 2030

Previous Move - ReCap
Summary
of Strategy
- D&D
leading to engineered Intel Failure, Coalition Exp
War expansion, regional alliance treaty
Expectations
v. Outcomes
- Paint
Blue as Big Bro, to OR/PU/BR, worked
- Regional
pact, though they still allow Blue in, e.g. ASEAN
- Engineered
Intel Failure (Milk Factory) worked
- BUT:
probably cant be relied on as a future strategy
Assessment
of success
- Turning
point, on the verge, right call to wait on fomenting civil strife,
would not be good move now

Move Brief - Objective
Solidify
our image as The Devil you know in the region, counter
Blue efforts to take credit/control
- Attempt
to ensure parts & support, to counter Blue FMS
- Not
aggressive, but Alliance standardization e.g. NATO
- Continue
maritime Exp. War alliance exercises in region
Assess
off-the-chart neighbors of our new Allies
- For
example, who is on the other side of Green?
Move Brief - Actions
Offer
to sponsor (C2, infrastructure, etc.) an alliance RRC
Emphasize
cultural friction incidents (whether engineered
or actual) e.g. soldiers/sailors on liberty, sex, drugs, and alcohol
Leverage
their human rights watch, give them something to find
- Covertly
give them something to find in one of the countries of interest
- They
cant have an FMS program with a HR violating country
- State
concerns of Blue militarizing region; CRAFT SPIN CAREFULLY!
Court
Reds in other Unified Commands (e.g.
bad guy on other side of Green)
Sell
legacy to partners with the emphasis on the support/parts and
regional coalition interoperability capability.
Engineer
Nuclear Free Zone to exclude all nuclear platforms (NZ paradigm).
Leverage
Red presence (students etc) in Blue and elsewhere.
Piracy
is a regional issue we can handle it.
Increase
regional law enforcement exercise activity small and
numerous, promoting interoperability. One of the foci for the security
alliance.
Minority Opinions
- Shouldnt
criticize Blue for FMS sales
- Ask
blue if they will sell to us?
links
title |