Where can i find a list off all the protocol codes?

[fd]

Not just the ones in protocols.csv

[jbenet]

@fd multiaddr is brand new, and we're adding protocols as we need them. Hence still small. Which protocols are you looking for? Happy to add them.

I should mention that we're starting to look at -- but haven't added support for -- addresses like this:

# ipfs node address, with hash of public key
/ip4/10.20.30.40/tcp/1234/ipfs/QmZSWmvJdrjtUo9TAVnRnRZbMfgcVbMbwMBhvsYTjBZ9es

# multiaddr specifying tls cypher
# 0xcc14 = TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
/ip4/10.20.30.40/tcp/1234/tls/cc14/ipfs/QmZSWmvJdrjtUo9TAVnRnRZbMfgcVbMbwMBhvsYTjBZ9es/

[jbenet]

And, i should also mention that I intend to distribute the multiaddr source and protocol table using IPFS itself, so that code can be self-describing.

[fd]

@jbenet Well I was looking into this as it might come in handy for my telehash (Go) implementation.

Btw seems like ipfs is a good fit for telehash.

[jbenet]

@fd cool, let me know what protocols you need multiaddr to support and we'll add them.

Btw seems like ipfs is a good fit for telehash.

Thanks, but I think we'll stick to our own mesh. Depending on another project like that is not going to be good for us. :( I also don't think that JSON is the right serialization.

Telehash is described as JSON + UDP + DHT, and I think this is shortsighted. I think we don't want to force any of the serialization, the transport, or the routing. The approach we're taking with IPFS is that every component is pluggable, with clean self-describing abstractions. (hence multiaddr, multihash, and soon multicodec)

(but I'm really glad Telehash is seeing solid work + support!)

[jbenet]

And @fd, come hang out in #ipfs in freenode.

[fd]

@jbenet There is no definitive list I could give you as telehash is completely plug-able. But a short list would be: (not all of these are are implemented atm.)

• udp
• tcp
• ipv4
• ipv6
• web sockets
• webrtc
• bluetooth

I also don't think that JSON is the right serialization

JSON is mainly used internally. As a user of the telehash stack you don't have to use JSON. But I agree that JSON can be too verbose at times.

Depending on another project like that is not going to be good for us

At the moment it would definitely not be a good idea to run ipfs over telehash as everything is still very much in flux. But in the long run I think does make sense to consolidate the networking stacks developed by many of the redecentralized/distributed/p2p projects out there. And that is exactly what telehash is aiming for.

Anyways, ❤️ ipfs

[jbenet]

@jbenet There is no definitive list I could give you as telehash is completely plug-able.

Looks to have changed, which is great! :)

At the moment it would definitely not be a good idea to run ipfs over telehash as everything is still very much in flux.

If telehash has become pluggable, it may be worth discussing at some point. We are going to implement message routing eventually (i.e. proper overlay network), and perhaps should interop or maybe we can help.

[yalamerde]

Why not mentioning NDN here?

@rynomad once also used telehash to route Federated Wiki from browser to browser.

[ghost]

There's a protocols.csv file in the root of this repository now, and some of the implementations have the same file, with the protocols they support.