Skip to content

Commit 72341fc

Browse files
committed
wip
1 parent 70a7665 commit 72341fc

File tree

1 file changed

+74
-0
lines changed

1 file changed

+74
-0
lines changed

src/ipips/ipip-xxxx.md

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

0 commit comments

Comments
 (0)