|
| 1 | +--- |
| 2 | +# IPIP number should match its pull request number. After you open a PR, |
| 3 | +# please update title and update the filename to `ipip0000`. |
| 4 | +title: "IPIP-0504: Provider Query Parameter" |
| 5 | +date: YYYY-MM-DD |
| 6 | +ipip: proposal |
| 7 | +editors: |
| 8 | + - name: Vasco Santos |
| 9 | +relatedIssues: |
| 10 | + - link to issue |
| 11 | +order: 0504 |
| 12 | +tags: ['ipips'] |
| 13 | +--- |
| 14 | + |
| 15 | +## Summary |
| 16 | + |
| 17 | +<!--One paragraph explanation of the IPIP.--> |
| 18 | +This is the suggested template for new IPIPs. |
| 19 | + |
| 20 | +## Motivation |
| 21 | + |
| 22 | +AKA Problem Statement |
| 23 | + |
| 24 | +Clearly explain why the existing protocol specification is inadequate |
| 25 | +to address the problem that the IPIP solves. |
| 26 | + |
| 27 | +## Detailed design |
| 28 | + |
| 29 | +AKA Solution Proposal |
| 30 | + |
| 31 | +Describe the proposed solution and list all changes made to the specs repository. |
| 32 | + |
| 33 | +The resulting specification should be detailed enough to allow competing, |
| 34 | +interoperable implementations. |
| 35 | + |
| 36 | +When modifying an existing specification file, this section should provide a |
| 37 | +summary of changes. When adding new specification files, list all of them. |
| 38 | + |
| 39 | +## Design rationale |
| 40 | + |
| 41 | +The rationale fleshes out the specification by describing what motivated |
| 42 | +the design and why particular design decisions were made. |
| 43 | + |
| 44 | +Provide evidence of rough consensus and working code within the community, |
| 45 | +and discuss important objections or concerns raised during discussion. |
| 46 | + |
| 47 | +### User benefit |
| 48 | + |
| 49 | +How will end users benefit from this work? |
| 50 | + |
| 51 | +### Compatibility |
| 52 | + |
| 53 | +Explain the upgrade considerations for existing implementations. |
| 54 | + |
| 55 | +### Security |
| 56 | + |
| 57 | +Explain the security implications/considerations relevant to the proposed change. |
| 58 | + |
| 59 | +### Alternatives |
| 60 | + |
| 61 | +Describe alternate designs that were considered and related work. |
| 62 | + |
| 63 | +## Test fixtures |
| 64 | + |
| 65 | +List relevant CIDs. Describe how implementations can use them to determine |
| 66 | +specification compliance. This section can be skipped if IPIP does not deal |
| 67 | +with the way IPFS handles content-addressed data, or the modified specification |
| 68 | +file already includes this information. |
| 69 | + |
| 70 | +### Copyright |
| 71 | + |
| 72 | +Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). |
0 commit comments