- Start Date: YYYY-MM-DD
- RFC Type: feature / decision / informational
- RFC PR:
- RFC Status: draft
One paragraph explanation of the feature or document purpose.
Why are we doing this? What use cases does it support? What is the expected outcome?
The reason this decision or document is required. This section might not always exist.
[Metrics to help support your decision (if applicable).]
If an RFC does not know yet what the options are, it can propose multiple options. The preferred model is to propose one option and to provide alternatives.
Why should we not do this? What are the drawbacks of this RFC or a particular option if multiple options are presented.
- What parts of the design do you expect to resolve through this RFC?
- What issues are out of scope for this RFC but are known?