Summary

  • draft-ietf-opsawg-rfc5706bis-07, posted on 7 September 2026, remains an Internet-Draft in AD Evaluation. It is intended as Best Current Practice, but it is not yet an RFC or approved BCP.
  • Revision 07 newly lists five acceptable forms for the proposed always-present Operational Considerations section: substantive treatment, partial inapplicability, a no-new-considerations statement with rationale, an internal pointer, or an overview plus normative reference to a companion document.
  • The draft recommends a fixed location partly so tools can detect the section. A heading check, however, cannot say which of the five paths the authors took or whether the promised material is reachable.
  • Daniel Kade proposes a compact review-side disposition receipt. It would expose the claimed path and its locator without turning a checklist into protocol law or pretending to accept an operator’s deployment risk.

A new paragraph changes the review question

The current Datatracker record describes an active Operations and Management Area Working Group document, submitted to the IESG for publication and intended for Best Current Practice. Its state is AD Evaluation with a revised draft needed; no telechat is scheduled. The 7 September announcement calls revision 07 work in progress. If approved, the document would obsolete RFC 5706 and update RFC 2360. None of those future effects has happened merely because a new revision appeared.

The news is a small insertion with large review consequences. The official comparison shows that revision 06 did not contain the five-case list now found in Section 3.1 of revision 07. The earlier text required the section and described what good treatment should cover. The new text says the section is always present, then routes authors among five permissible forms.

That change shifts the useful question. A reviewer should no longer ask only, “Is the section there?” The sharper question is, “Which disposition is this document claiming, and where is the supporting treatment?”

Five valid answers are not one state

The first path is straightforward: the new protocol, extension or use raises operational and manageability issues, so the section discusses them. A transport might need failure signals, defaults, migration guidance, telemetry or interaction with existing tools.

The second path is selective. Some topics apply and others do not. The section should briefly explain why an item is irrelevant rather than leaving silence to carry the conclusion. This matters because absence can otherwise mean “considered and inapplicable,” “forgotten,” or “deferred.”

The third path applies when there are no new operational or manageability requirements at all. Section 3.2 supplies a fixed statement—“There are no new operations or manageability requirements introduced by this document”—and requires a brief rationale. The boilerplate is deliberately not enough on its own.

The fourth path avoids repetition. When the relevant considerations already sit elsewhere in the same draft, the section should summarize them and point to the exact locations. A pointer is therefore part of the answer, not decoration.

The fifth path handles a large companion treatment. The section provides a short overview and a normative reference to a separate document. That is a stronger dependency than an informative reading suggestion: review of the operational claim now depends on identifying and reaching another named text.

These outcomes are compatible with the same heading. They are not interchangeable. A substantive section asks whether the analysis is adequate. A partial-inapplicability claim asks whether each exclusion is justified. The no-new-considerations route asks whether the rationale survives contact with the protocol change. An internal pointer asks whether the destination actually contains the promised material. A companion reference asks whether the dependency is stable, normative and reviewed on a compatible timetable.

The detector sees less than the reviewer

Section 3.3 recommends placing Operational Considerations immediately before Security Considerations. Reviewers can find it more easily, and the draft says the placement could simplify development of tools that detect its presence.

That is a sound minimum. A linter can normalize headings and report a missing section. It can also recognize the exact no-new-considerations sentence with high confidence. It cannot safely classify the other four paths from unrestricted prose. “See Section 6” may be a real internal join or an empty gesture. A normative reference may hold the full operating model or only adjacent background. A long section may still omit the one deployment failure that matters.

The false assurance arrives when the binary result—heading present—travels farther than its limited meaning. Dashboards can turn it green. Shepherd summaries can inherit the green mark. A later implementer may read that as “operations reviewed,” although the automated evidence proved only that a line of Markdown or XML existed.

The reverse error matters too. A document may contain serious operating analysis in its data model or another section, as revision 07 explicitly permits, yet a crude checker may treat a short pointer section as thin. The classification must come from the author’s declared path and a reviewer’s judgment, not from length.

Add one small disposition receipt

The proportionate response is not a new mandatory schema inside every RFC. It is a compact review-side receipt, maintained with the draft’s other process evidence. Call it operational-disposition if a label is useful.

The receipt should identify the draft name and exact revision. It should select one primary outcome: substantive, partial-not-applicable, no-new-considerations, in-document-reference, or companion-document. It should give the section locator, and where relevant the internal destinations or normative companion reference. It should preserve the authors’ short rationale, a reviewer state such as unreviewed, concerns raised or reviewed, and any unresolved dependency.

One primary code need not deny mixtures. A substantive section may also declare two checklist topics inapplicable. The receipt can record those exceptions without losing the main route. What matters is that a later reader can distinguish a claim about content from evidence that someone assessed it.

The record should change when the draft revision changes. If an internal section moves, the locator must move. If a companion draft expires or becomes informative, the dependency should reopen. If an Area Director asks for revised text, “reviewed” should not silently survive as though it applied to unseen bytes.

This proposal does not replace the OPSDIR review template, working-group judgment or IESG authority. It makes their object legible. Nor does it contradict the draft’s view that missing tooling alone should not delay publication. The receipt can begin as a human-maintained line in a review; automation is optional.

The security addition shows why classification matters

Revision 07 also adds a paragraph on security operations. It observes that QUIC, TLS 1.3, Encrypted Client Hello and DNS over HTTPS encrypt metadata once visible to passive inspection. Designers are asked to acknowledge the tension between privacy and security visibility and to consider alternatives such as endpoint telemetry or logging without undermining privacy. The draft links the operational issue to the indicator lifecycle described by RFC 9424.

That paragraph is substantive operational analysis. It does not order endpoint surveillance, promise equivalent visibility or make absent tooling a publication veto. A disposition receipt would help preserve those distinctions: this is not a no-new-considerations case, and the operational response is not fully delegated to a companion document. The text names a tradeoff and a design question while leaving implementations and deployments to justify their choices.

The point is modest but consequential. A mandatory section can stop operational thought from disappearing entirely. Five explicit paths can stop authors from treating every short section as failure. A visible disposition can stop the heading itself from becoming counterfeit proof.

Sources