F27-LT: No
Rationale
LTP uses link-state cues and planned transmission schedules to suspend or resume recovery timers; SABR uses supplied contact plans. Neither selected mechanism specifies an agreement between participants negotiating receive windows and intervening inactivity.
Assessment method
Primary documentary and source assessment; no new runtime test
Source context
Primary specification or selected-version source; bounded composition assessment
Outstanding qualification
RFC 5326 sections 6.5–6.6 and SABR section 2.3.1. F32 planned routing and F33 interruption-aware recovery remain Yes. This No does not deny scheduled operation; no additional MAC/contact-negotiation protocol is selected.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round470.html
- round470-sources.json