Communications Survivability Function

Disrupting or deceiving the downlink is a communications-availability attack the survivability obligation speaks to, but the parent technique also covers inhibiting ground and spacecraft functionality by non-RF means, which link recovery does not reach.

Jamming the link to suppress the downlink is a communications-jamming attempt in the practice's own terms; a mission that can recover the link defeats the evasion the technique buys.

Flooding the command path is a communications-availability attack, and a mission designed to recover link service recovers from it. The practice names jamming and spoofing rather than flooding, so the relevance is real but the excerpt does not reach the technique's mechanism directly.

The practice names spoofing, but its subject is the communications link, whereas the parent spoofing technique spans forged sensor measurements, internal bus messages, and navigation signals as well. The dominant scope sits outside the practice, so this is addresses rather than mitigates.

Deliberately typed down from the mitigates carried by its uplink and downlink sub-techniques. The parent spans PNT jamming as well, and the BPG splits PNT survivability into a separate practice (MI-INTG-02), so this practice covers most but not all of the parent's scope. Under the universal-strict standard partial scope coverage is addresses.

The practice requires the mission to be able to recover from communications jamming, and uplink jamming is that case exactly: the defining vector (RF interference denying the command path) and the whole of the technique's scope fall inside the practice's stated obligation. This is one of the few pairings in the corpus where the source text names the technique's own mechanism rather than a generalisation of it.

Downlink jamming denies the telemetry path, and the practice's survivability obligation covers the communications link in both directions. Defining vector and dominant scope are both inside the practice.