Summary

  • The 31 August procurement answers require source captions and transcripts as separate files and narration scripts distinct from slide decks, while leaving additional format choices open.
  • The updated tender already requires independently updatable modules and favors operation after the producer's contract ends. Ownership alone does not demonstrate that capability.
  • A small correction performed by the intended successor maintainer would test the handover without assessing or tracking learners. This is an editorial proposal, not a new IETF requirement.

The next correction is the useful test

A course can remain available long after its instructions stop being current. A tool changes, a procedure moves or a diagram needs a qualification. The original video still plays. The question is whether its owner can repair the teaching without commissioning the whole production again.

That question now has an unusually concrete basis in the IETF Administration LLC's new-participant training procurement. Its 31 August answers, question 2, distinguish the assets a maintainer receives from the presentation a learner sees. Source captions and transcripts should arrive separately rather than be burned into source video. Narration scripts must be separate from, and complement, the slides. The answer does not choose WebVTT or SRT; those formats occur in the question. Nor does it promise that every text change can avoid rendering video again.

The clarification gives practical shape to an existing requirement. The updated RFP calls for modular content, editable source files, rights assigned to the LLC and formats the LLC or a designated contractor can operate after the contract ends. It favors that independence over supplier-locked arrangements; it does not outlaw every proprietary tool. Ongoing updates are distinguished from included post-launch support and would be billed separately.

These are sensible procurement provisions. They are not yet evidence of a successful handover. As checked on 3 September, the procurement index still marks the project open. The original notice puts bids due on 11 September at 22:00 UTC. The Q&A expects deployment by 31 January 2027. No supplier, final price, finished course or tested maintenance arrangement is established by these documents.

Separate files need a working relationship

An editable script is useful only if its maintainer can identify which narration, slide and caption track it belongs to. A correction to one layer may change the timing or meaning of another. A folder containing all the files can therefore be complete as an inventory and incomplete as an operating handover.

The economical way to discover that difference is a representative correction rehearsal. Before accepting the handover, the buyer could agree one small, authorized revision and ask the intended successor maintainer to make it with the delivered materials and instructions. Where necessary, that means rebuilding the affected media, checking synchronization and accessibility, publishing through an authorized test path and restoring the previous version. Unchanged modules should remain undisturbed.

The record need not be elaborate: what changed, which assets and tools were needed, who approved the meaning, how much effort the exercise took and whether the original producer had to intervene. A successful test would establish one bounded capability, not that every future update will be effortless. A failed attempt would identify a handover task, not prove misconduct or justify discarding a useful course.

This is also different from measuring learners. Answers 11 and 12 expect neither learner assessment nor tracking as part of this project. A maintenance exercise tests the purchased material. It needs no personal learning history and makes no claim about analytics elsewhere on the hosting platforms.

Editing a lesson is not changing the rules

The RFP gives content sign-off to an LLC-designated contact, with access to subject experts. That role should remain distinct from operating the editing tools. RFC 8711 assigns the LLC administrative support, not authority over standards development. A maintainer can correct a lesson to match an authoritative process change; possession of its source files does not authorize a new process.

Lu Heng's agency-problem argument offers a useful question here: who controls the function, and who carries the cost when dependence persists? Applied narrowly, the answer is not to presume a bad supplier. It is to make the buyer's option to change suppliers usable. The strongest result is a well-supported course whose producer can be retained for good work, not because nobody else can revise it.

Sources