Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specs 2.0 & libp2p book #110

Open
2 of 16 tasks
ghost opened this issue Nov 11, 2018 · 1 comment
Open
2 of 16 tasks

Specs 2.0 & libp2p book #110

ghost opened this issue Nov 11, 2018 · 1 comment

Comments

@ghost
Copy link

ghost commented Nov 11, 2018

(some preliminary brainstorming based on a discussion with @whyrusleeping, @bigs)

Goal

Revise/update/improve libp2p specs and provide clearer usage guidance

List of proposed documents

1. Base wire formats

2. libp2p book / Usage

(some of these could be considered specs, others would be non-mandatory "suggested usage" guides)

  • a doc describing exactly how these are tied together, a spec for the ‘swarm’
  • document describing how dialing works.
  • document describing the ‘libp2p api’. Which is not language specific, but a broader description of the capabilities of each subsystem in terms of what it does.
  • Better diagrams (see https://github.com/libp2p/libp2p/issues/55)

3. Libp2p ‘builtin’ protocols

4. Other

  • probably also something on NAT Traversal
  • Also need a multiaddr spec (there may exist one, but lets make sure its "proper")

Format notes:

  • Everything in markdown, organized into a gitbook. Gives us a nice website UI, or users can print it all to a single PDF.
@ghost ghost changed the title Specs 2.0 Specs 2.0 & libp2p book Nov 11, 2018
@raulk
Copy link
Member

raulk commented Mar 13, 2019

The non-normative technical walkthrough I'm writing covers these topics. @yusefnapora is working on docs.libp2p.io. We have docs under control -- we just need to get specs aligned now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant