| Status | Author | Start Date | RFC PR | Related Issues |
|---|---|---|---|---|
(Draft / Proposed / Accepted / Implemented / Obsoleted) |
My Name <[email protected]> |
(fill me in with today's date, YYYY-MM-DD) |
(leave this empty) |
(leave this empty) |
Brief explanation of the feature.
Why are we doing? What problem will this solve?
Actual specific use cases. Who will benefit from this proposal? What is the expected outcome?
This is the bulk of the RFC. Explain the design in enough detail for somebody familiar with Brane Project to understand, and for somebody familiar with the implementation to implement. This should get into specifics and corner-cases, and include examples of how the feature is used. Any new terminology should be defined here.
Optional, if any special terms are used in this document, provide definitions and brief explanations about it. If it relies on another RFC, attach RFC PR link instead.
If present, explain the implementation strategy.
Why should we not do this? Please consider:
- Implementation costs
- Performance impact. Could this proposal cause serious performance degradation to Brane environment? If it is, does it comes with a solution to mitigate?
- Impact on distribution of the Brane project. Could this proposal support or can be interoperable with the platform requirements?
- Configuration complexity. Does this proposal require separate provisioning step or additional setup?
What other designs have been considered? What is the impact of not doing this?
Optional, Prior art that is existing solution that might accomplish the same as this proposal.
Optional, but suggested for first drafts. What parts of the design are still TBD?