Summary

  • RFC 3716 identified Sandy Ginoza in 2004 as the full-time principal technical editor managing the RFC Editor queue and much of its contact with authors and the IESG. The team's stated goal was three pairs of eyes on every RFC, word for word.
  • A public June 2026 final-review trail for what became RFC 10008 shows edits to the Accept-Query definition, references and wording. Authors approve the final text; the RFC Production Center turns approved drafts into durable publications.

A queue behind the number

The number on an RFC looks inevitable once it is printed. In RFC 3716, the RFC Editor team described a less glamorous 2004 scene: Ginoza managed the publication queue and much of the daily exchange with authors and the IESG. The team wanted three pairs of eyes to read each RFC word for word and said it reached that goal in most cases. That was a staffing account from 2004, when she was listed as a full-time technical editor. The IETF's current profile now lists her as chair of the RFC Production Center and its advisory team.

The work survives in public traces. On 8 June 2026, a final-review archive message for RFC-to-be 10008 recorded changes attributed to Ginoza: quotation marks around Accept-Query where the field is defined, reference ordering, wording for parallelism, and changes made at an author's request. Other contributors appear in the same trail. The published RFC 10008 is the finished HTTP QUERY document. The archive shows people settling the exact presentation of a protocol text, one commit at a time.

Approval and publication have different desks

The current RFC Editor Model, RFC 9920, assigns content approval to each document stream and production to the RFC Editor function. Its Production Center edits and publishes across the streams. The RFC Editor's author guide says authors review and approve the changes before publication. That sequence gives an engineer two useful questions when a sentence matters: which body approved the substance, and which final text did the author sign off for the archive?

Ginoza's desk is where those questions meet. A reference in the wrong place, an ambiguous definition or an unapproved editorial change can outlive the meeting that produced it. The public record does not count bugs prevented by the 2026 edits; a before-and-after implementation test would be needed for that claim. It does show the publication chain doing work after approval. Standards gain authority when the final bytes and their handoff can be inspected.

Sources: RFC 3716; IETF profile; RFC 10008 final-review record; RFC 10008; RFC 9920; RFC Editor author guide.