Note
RFC 2119
The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this document, when emphasized, are to be interpreted as described in RFC 2119.

Format

All published documents related to CTF 2 must have a unique document identifier (ID) which have the following format:

CTF2-<short name>-<major>.<minor>[r<revision>]
Table 1. Descriptions and roles of CTF 2 document ID parts
Part Description Bump may introduce new concepts, procedures, and formats? Bump may remove or change existing concepts, procedures, and formats?

<short name>

The capitalized short name of the document, unique amongst all the published CTF 2 documents (letters only).

N/A

N/A

<major>

The major version number of the document.

Yes

Yes

<minor>

The minor version number of the document.

Yes

No

<revision>

The revision letter of the document (from A to Z).

Document revisions are used to add examples, clarify existing concepts, fix grammar or content mistakes, or reword existing parts, for example.

No

No
Example 1. CTF 2 document ID

Consider this CTF 2 document ID:

CTF2-ANAME-1.2rC

Its parts are:

  • CTF2: This is a CTF 2 document.

  • ANAME: Document’s short name.

  • 1.2: First major version, third minor version.

  • rC: Revision C of the document.

References

The text of any published CTF 2 document must only use the document ID of another published CTF 2 document to which it refers, without the revision letter.

Example 2. CTF 2 document reference
If a CTF 2 producer applies CTF2-ANAME-1.2, …