diff options
Diffstat (limited to 'draft-schanzen-r5n.xml')
-rw-r--r-- | draft-schanzen-r5n.xml | 32 |
1 files changed, 20 insertions, 12 deletions
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml index 2c25f77..729a4d6 100644 --- a/draft-schanzen-r5n.xml +++ b/draft-schanzen-r5n.xml | |||
@@ -199,18 +199,6 @@ Connectivity | |Underlay| |Underlay| | |||
199 | <section anchor="underlay" numbered="true" toc="default"> | 199 | <section anchor="underlay" numbered="true" toc="default"> |
200 | <name>Underlay</name> | 200 | <name>Underlay</name> |
201 | <t> | 201 | <t> |
202 | Discuss the DHT underlay concept here. | ||
203 | </t> | ||
204 | </section> | ||
205 | <section anchor="connectivity" numbered="true" toc="default"> | ||
206 | <name>Connectivity and addressing</name> | ||
207 | <t> | ||
208 | In the DHT overlay, a peer is addressable by its Peer ID. | ||
209 | The Peer ID is the 256-bit hash of the peer public key. | ||
210 | The peer public key is the public key of the corresponding | ||
211 | Ed25519<xref target="ed25519" /> peer private key. | ||
212 | </t> | ||
213 | <t> | ||
214 | In the network underlay, a peer is addressable by traditional | 202 | In the network underlay, a peer is addressable by traditional |
215 | means out of scope of this document. For example, the peer may | 203 | means out of scope of this document. For example, the peer may |
216 | have a TCP/IP address, or a HTTPS endpoint. | 204 | have a TCP/IP address, or a HTTPS endpoint. |
@@ -255,6 +243,8 @@ Y924NSHMMZ1N1SQCE5TXF93ED6S6JY311K0QT86G9WJC68F6XVZ0 \ | |||
255 | tor+onionv3://rasdflkjasdfliasduf.onion/ | 243 | tor+onionv3://rasdflkjasdfliasduf.onion/ |
256 | ]]></artwork> | 244 | ]]></artwork> |
257 | </figure> | 245 | </figure> |
246 | |||
247 | |||
258 | <!-- | 248 | <!-- |
259 | 1) The current API is always fire+forget, it doesn't allow for flow | 249 | 1) The current API is always fire+forget, it doesn't allow for flow |
260 | control. I think we need to add that, possibly for sending and receiving. | 250 | control. I think we need to add that, possibly for sending and receiving. |
@@ -344,6 +334,24 @@ see how we can offer even the most minimal protections against peer | |||
344 | </dd> | 334 | </dd> |
345 | </dl> | 335 | </dl> |
346 | </section> | 336 | </section> |
337 | |||
338 | <section anchor="overlay" numbered="true" toc="default"> | ||
339 | <name>Overlay</name> | ||
340 | <t> | ||
341 | In the DHT overlay, a peer is addressable by its Peer ID. | ||
342 | The Peer ID is the 256-bit hash of the peer public key. | ||
343 | The peer public key is the public key of the corresponding | ||
344 | Ed25519<xref target="ed25519" /> peer private key. | ||
345 | </t> | ||
346 | </section> | ||
347 | <section anchor="blockstorage" numbered="true" toc="default"> | ||
348 | <name>Block Storage</name> | ||
349 | <t> | ||
350 | </t> | ||
351 | </section> | ||
352 | <section anchor="messages" numbered="true" toc="default"> | ||
353 | <name>Message Processing</name> | ||
354 | </section> | ||
347 | <section anchor="routing" numbered="true" toc="default"> | 355 | <section anchor="routing" numbered="true" toc="default"> |
348 | <name>Routing</name> | 356 | <name>Routing</name> |
349 | <section anchor="peer_selection" numbered="true" toc="default"> | 357 | <section anchor="peer_selection" numbered="true" toc="default"> |