Skip to content

Latest commit

 

History

History
39 lines (25 loc) · 1.4 KB

0000-template.md

File metadata and controls

39 lines (25 loc) · 1.4 KB
Raw

Title-cased Name of the Feature

  • Status: proposed ("proposed", "agreed", "active", "implemented" or "rejected")
  • Type: (new feature, enhancement)
  • Related components: (if any)
  • Start Date: (fill me in with today's date, DD-MM-YYYY)
  • Discussion: (fill me in with link to RFC discussion - shepherd will complete this)
  • Supersedes: (fill me in with a link to RFC this supersedes - if applicable)
  • Superseded by: (fill me in with a link to RFC this is superseded by - if applicable)
  • Author: (your name)

Summary

One paragraph explanation of the feature.

Conventions

  • The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Motivation

Why are we doing this? What use cases does it support? What is the expected outcome?

Detailed design

This is the bulk of the RFC. Explain the design in enough detail for somebody familiar with the network to understand, and for somebody familiar with the code practices to implement. This should get into specifics and corner-cases, and include examples of how the feature is used.

Drawbacks

Why should we not do this?

Alternatives

What other designs have been considered? What is the impact of not doing this?

Unresolved questions

What parts of the design are still to be done?