Skip to main content

RFC-0002: Common mixnet terms and keywords

  • RFC Number: 0002
  • Title: Common mixnet terms and keywords
  • Status: Raw | Discussion | Prototype | Implementation | Finalized | Rejected | Superseded
  • Author(s): <Name (GitHub Handle)>
  • Created: <YYYY-MM-DD>
  • Updated: <YYYY-MM-DD>
  • Version: v0.x.x (Raw), v1.x.x (Finalized)
  • Supersedes: RFC-YYYY (if applicable)
  • References: [Related RFCs or Documentation Links]

Abstract​

Provide a brief and clear summary of the RFC, outlining its purpose, context, and scope.

Motivation​

Explain the problem this RFC aims to solve. Discuss existing limitations, technical gaps, and why the proposed solution is necessary.

Terminology​

Define key terms, abbreviations, and domain-specific language used throughout the RFC.

Specification​

Comprehensive description of the proposed solution, including:

  • Protocol overview
  • Technical details (data formats, APIs, endpoints)
  • Supported use cases
  • Diagrams (stored in assets/ and referenced as ![Diagram](assets/diagram-name.png))

Design Considerations​

Discuss critical design decisions, trade-offs, and justification for chosen approaches over alternatives.

Compatibility​

Address backward compatibility, migration paths, and impact on existing systems.

Security Considerations​

Identify potential security risks, threat models, and mitigation strategies.

Drawbacks​

Discuss potential downsides, risks, or limitations associated with the proposed solution.

Alternatives​

Outline alternative approaches that were considered and reasons for their rejection.

Unresolved Questions​

Highlight questions or issues that remain open for discussion.

Future Work​

Suggest potential areas for future exploration, enhancements, or iterations.

References​

Include all relevant references, such as:

  • Other RFCs
  • Research papers
  • External documentation