| aip | title | status | type | author | created | updated | requires (optional) | replaces (optional) |
|---|---|---|---|---|---|---|---|---|
<to be assigned> |
<AIP title> |
<Draft | Active | Final> |
<Meta | Feature | Misc> |
name1 <addr1>, name2 <addr2> ... |
<yyyy-mm-dd> |
<yyyy-mm-dd> |
<AIP no.(s)> |
<AIP no.(s)> |
- An AIP number will be assigned by an editor.
- A filename
aip-<draft_title_abbr>.mdis suggested when opening a pull request to submit your AIP.
Simply summarize your AIP's function(s) and/or any notable aspect...
Briefly describe the issue(s) being addressed and the solution(s) to be implemented... (~200 words)
Specifically describe the 0-1 walkthrough of any new feature. (The specification should be detailed enough to allow competing, interoperable implementations for any of the current Agora platforms.)
Flesh out the specification by describing why particular design decisions were made. (The rationale should describe alternate designs that were considered and related work.)
Attach an implementation proposal in your way as an appendix to this section. (The implementation must be completed before any AIP is given status "Final", but it need not be completed before the AIP is accepted.)
Copyright and related rights waived via CC0.