The DBMS-iTC uses public GitHub Issues and Discussions as its primary contact and review channels. This keeps proposed changes, rationale, decisions, and follow-up visible to reviewers and document editors.

Channel Use it for Start here

GitHub Issue

A specific defect, ambiguity, missing requirement, proposed wording change, evaluation-activity correction, or formal request for interpretation that should be tracked to resolution.

Choose an issue template

GitHub Discussion

A broader design question, early proposal, cross-document topic, community or membership question, or idea that would benefit from conversation before a concrete change is defined.

Start a discussion topic

Website issue

A broken link, inaccessible artifact, rendering defect, or problem with the public-review website rather than the technical content of a DBMS document.

Report a website problem

Before You Submit

  1. Sign in to a GitHub account. GitHub requires an authenticated account to open an issue or start a discussion.

  2. Search the existing issues and existing discussions for the same topic.

  3. Identify the affected document, version, section, table, or requirement identifier.

  4. Keep each issue focused on one independently resolvable change. Use a discussion when the scope or preferred resolution is not yet clear.

  5. Do not include confidential evaluation evidence, proprietary product information, credentials, or other material that should not be public.

Submit a Review Issue Using a Template

  1. Open the DBMS Documents issue-template chooser.

  2. Select Get started beside the template that best matches the comment.

  3. Keep the template’s title prefix and add a short, specific summary.

  4. Complete every relevant prompt. A proposed resolution or example replacement text makes a comment much easier to evaluate.

  5. Use the Preview tab to check formatting and links, then select Submit new issue.

  6. Follow the issue for questions, proposed edits, and the recorded disposition.

Table 1. Issue-template guide
Template Choose it when

cPP change request

The comment concerns the DBMS Base cPP, its security problem definition, conformance claims, SFRs, SARs, or supporting rationale.

PP-Module change request

The comment concerns the Cryptographic Functions, Cloud, or DBaaS PP-Module. Identify whether the impact is in Crypto + Cloud, Crypto + DBaaS, or both families.

SD change request

The comment concerns an Evaluation Activity, test, evidence expectation, evaluator guidance, or other Supporting Document content.

PP-Configuration change request

The comment concerns composition, compatibility, mandatory modules, conformance, or another PP-Configuration rule.

Request for Interpretation

A published requirement or Evaluation Activity needs a formal interpretation. Check the current Technical Decisions first and submit one question per request.

Information That Makes an Issue Actionable

Include the following whenever it applies:

  • Document title and version.

  • Section title, page, table, SFR, SAR, Evaluation Activity, or stable HTML link.

  • The current text or behavior that creates the problem.

  • The security, evaluation, interoperability, or editorial impact.

  • Proposed replacement text or a concrete resolution.

  • Relevant standards, implementation evidence, diagrams, or related issues and discussions.

Example 1. Example issue outline

Title: [MODULE CHANGE] Clarify the tenant identifier binding in FIA_USB.1/DBaaS

Document and location: DBMS DBaaS PP-Module 0.5, FIA_USB.1/DBaaS application note.

Problem: State the ambiguity and the interpretations a reader could reasonably reach.

Proposed resolution: Supply replacement wording or describe the intended rule precisely.

Composition impact: Crypto + DBaaS; identify any corresponding Supporting Document activity that also needs adjustment.

Start a Discussion Topic

  1. Open DBMS-iTC Discussions and search for an existing conversation.

  2. Select New discussion or use the direct discussion-category chooser.

  3. Choose the category that best fits the topic.

  4. Enter a descriptive title that names the technology area or document family.

  5. In the body, explain the context, affected documents, question to resolve, important alternatives, and your preferred direction if you have one.

  6. Select Start discussion and follow the topic for replies.

A strong discussion opening normally answers four questions:

  1. What decision or uncertainty should the community address?

  2. Which DBMS documents or review families are affected?

  3. What alternatives or constraints should participants consider?

  4. What outcome would allow the topic to become a concrete document change?

Move From Discussion to a Tracked Change

When a discussion produces a concrete change, open the appropriate issue template and include the discussion URL. The issue becomes the tracked unit of work; the discussion remains the background and decision record. Maintainers may also create an issue directly from a discussion when the topic is ready for implementation.

Direct Links

For more help with the GitHub interface, see GitHub’s guides to creating an issue and participating in a discussion.