Template IETF References and Terminology

This file is the curated authoritative reference, terminology, and dependency map for a real project pack.

Support-only staged material belongs under sibling references/; it may help local work, but it does not replace this file.

External reference pool

Separate references by weight so the project does not blur what is required for interoperability with what merely adds context.

Normative pool

List only the references a correct reader or implementer actually needs.

• [replace: RFC or standards document required by the draft]
• [replace: protocol grammar, media-type, data-model, or security reference]
• [replace: standards-track dependency that a cited mechanism relies on]

For each entry, consider adding a short purpose note such as — ABNF, — TLS requirements, or — media-type registration.

Informative pool

List supporting references that help orientation, history, examples, or implementation background.

• [replace: explanatory design document or historical note]
• [replace: background paper or prior draft]
• [replace: implementation documentation or reference manual]

Internal document dependency map

If the pack covers a suite, record how the documents depend on one another.

• [replace: foundational document] owns [replace: terminology, model, or format].
• [replace: dependent document] depends on [replace: foundational document] for [replace: definitions or behavior].
• [replace: document] may cite [replace: document] for [replace: narrow reason], but should not redefine it inline.
• [replace: project-wide rule about when to cross-reference versus duplicate text].

If the pack covers only one document, use this section to record external dependency ownership instead of cross-document ownership.

Terminology ownership

Use this section to pin each core term to one owner so vocabulary does not drift.

Terms owned by [replace: owning document or source]

• [replace: term A]
• [replace: term B]
• [replace: term C]

Terms owned by [replace: another owning document or source]

• [replace: term D]
• [replace: term E]

If a term is inherited from an external RFC instead of being locally defined, say so explicitly.

Citation hygiene notes

Record the pack-level citation rules that keep the drafts clean and consistent.

• [replace: cite narrowly to the exact owning document or section]
• [replace: do not duplicate long definitions across documents]
• [replace: do not import the full normative pool into every draft; cite only what each draft uses]
• [replace: informative implementation docs stay informative unless the authoritative corpus confirms the same rule]

Open decisions the project owner must settle

Delete this section once the pack is customized.

• [replace: unresolved normative reference choice]
• [replace: unresolved terminology owner]
• [replace: unresolved dependency or split between documents]