Use this file for shared front-matter defaults. The items in Reusable defaults are assumed unless the project owner records an override; the items in Project-specific decisions must still be supplied explicitly.
Reusable defaults
Unless the project says otherwise:
- Draft source format: kramdown-rfc Markdown
.md - Public default deliverable: rendered plain-text
.txt - Intermediate artifact: RFCXML
.xml - Reference pool source:
references.md - Additional rendered forms: HTML or PDF only when the project explicitly treats them as published outputs
These defaults keep the pack aligned with the repo-level IETF workflow without forcing every project to restate the same toolchain facts.
Project-specific decisions that still need human input
Do not leave these to tool defaults or template inheritance:
- per-document
title - real author/editor names and affiliations
- submission stream /
submissiontype - intended status / category
- abstract anchor or promise for each draft
- document name / filename convention when it matters externally
- workgroup, area, consensus, or other stream-specific boilerplate fields if applicable
- any project-specific provenance or ratification wording
Authorship and provenance boundary
Record the front-matter rules that belong to this project.
- The author block should reflect the real human authors/editors for the draft.
- If the project requires provenance, transformation, or ratification wording, record the exact allowed wording here rather than improvising it in each brief.
- If only some documents may carry special provenance text, list that boundary explicitly.
- If no special provenance text is allowed, say so here.
Per-document metadata worksheet
Duplicate or extend this table for each real deliverable in the project.
| Document | Title | Stream | Status | Abstract anchor | Special front-matter constraints |
|---|---|---|---|---|---|
[replace: document name] |
[replace: full title] |
[replace: stream] |
[replace: intended status] |
[replace: one sentence describing what the abstract must promise] |
[replace: provenance, boilerplate, naming, or no special rule] |
[replace: document name] |
[replace: full title] |
[replace: stream] |
[replace: intended status] |
[replace: one sentence describing what the abstract must promise] |
[replace: provenance, boilerplate, naming, or no special rule] |
Optional shared metadata conventions
Use this section only if the suite truly shares these conventions.
[replace: keywords, area, workgroup naming, or document-family title prefix][replace: whether requirement-keyword boilerplate is expected in all documents or only some][replace: any project-specific publication or render exception to the default .txt/.xml/.md chain]
What stays outside this file
Do not restate repo-level render mechanics here. For kramdown-rfc and xml2rfc structure, validation, warning triage, and rendered-example checks, use ../../toolchains/kramdown-rfc-mechanics.md.