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

Upgrade Protocol Handles to Follow the SPEC #1549

Open
whyrusleeping opened this issue Aug 3, 2015 · 6 comments
Open

Upgrade Protocol Handles to Follow the SPEC #1549

whyrusleeping opened this issue Aug 3, 2015 · 6 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@whyrusleeping
Copy link
Member

To get multistream interop between node and go, we need to agree on the official protocol names.

stream muxers:

  • spdystream -> /stream-muxer/spdy/3.1.0
  • yamux -> /stream-muxer/yamux/1.0.0
  • multiplex -> /stream-muxer/multiplex/1.0.0

ipfs protocols:

  • ping -> /ipfs/ping/1.0.0
  • dht -> /ipfs/dht/1.0.0
    • maybe use 'kademlia' in there somewhere
  • bitswap -> /ipfs/bitswap/1.0.0
  • diagnostics -> /ipfs/diag/1.0.0
@whyrusleeping
Copy link
Member Author

cc @diasdavid @jbenet

@daviddias
Copy link
Member

It would be good to avoid using the name DHT, to avoid the Peer VS Content routing. Right now I'm calling the routing part that uses kademlia, kad-router, as a module name. so maybe we can have: /ipfs/router/kad/1.0.0, so that in the future we might have /ipfs/router/anotherP2POverlayRouting/1.0.0 too.

For the record store, I haven't cored it yet, but probably /ipfs/record-store/1.0.0 would be good.

@whyrusleeping
Copy link
Member Author

as far as I know the record store isnt a protocol.

@whyrusleeping whyrusleeping added the need/community-input Needs input from the wider community label Aug 13, 2015
@daviddias daviddias changed the title Official ipfs protocol names Upgrade Protocol Handles to Follow the SPEC May 10, 2016
@daviddias
Copy link
Member

@whyrusleeping here is a ping to remind you to support the protocol multicodecs by spec, as described on:
https://github.com/ipfs/specs/blob/master/libp2p/7-properties.md#757-protocol-multicodecs

@whyrusleeping
Copy link
Member Author

depends on #3110

@momack2 momack2 added this to Inbox in ipfs/go-ipfs May 9, 2019
@Winterhuman
Copy link
Contributor

@whyrusleeping @daviddias Should this be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
No open projects
Development

No branches or pull requests

3 participants