Moving forward with multiaddr

[victorb]

Speaking with @lgierth we've come up with a preliminary todo list for making multiaddr fit for general usage:

• Outline use cases (fill them out probably)
  • dns over https should be included
• Consilidate discussions about paths in segment values (url/unix paths)
• Come up with multiaddr interface (what functions every implementation should expose)
• Encoding/Decoding (WIP: Document encoding/decoding algorithm #54)
• Figure out how to handle partial decoding of multiaddr
  • Basically be able to parse selected parts of a multiaddr even if there is missing codecs, allowing custom/experimental codecs
• Update the entire ecosystem (go+js+rust first)
• Document dnsaddr + (dnslink)
  • make dnslink/dnsaddr separation clearer

[Stebalien]

Try to figure out a way to allow partial decoding of multiaddrs where segments aren't understood (missing codecs). Currently, a missing codec means one can't know the length of the value and can't decode the address.

We should at least come up with a way to allow custom/experimental codecs. That'll cover most of this use-case.

[alanshaw]

#102 resolves some of that last item...

[ethindp]

I posted about encoding/decoding on #54; just posting this here in case nobody notices. I'm not sure if its too late... I was going to implement an IPFS library but then saw that the multiaddr format wasn't specified in terms of encoding/decoding so that lead me to that PR.