Composable and future-proof network addresses
Switch branches/tags
Nothing to show
Clone or download
gabcoh and Stebalien Fix protocols.csv to be a properly formatted csv file (#66)
use ; instead of , to avoid starting a new column.
Latest commit ad75a23 Jun 11, 2018

README.md

multiaddr

Composable and future-proof network addresses

Captain: @lgierth

Introduction

Multiaddr aims to make network addresses future-proof, composable, and efficient.

Current addressing schemes have a number of problems.

  1. They hinder protocol migrations and interoperability between protocols.
  2. They don't compose well. There are plenty of X-over-Y constructions, but only few of them can be addressed in a classic URI/URL or host:port scheme.
  3. They don't multiplex: they address ports, not processes.
  4. They're implicit, in that they presume out-of-band values and context.
  5. They don't have efficient machine-readable representations.

Multiaddr solves these problems by modelling network addresses as arbitrary encapsulations of protocols.

  • Multiaddrs support addresses for any network protocol.
  • Multiaddrs are self-describing.
  • Multiaddrs conform to a simple syntax, making them trivial to parse and construct.
  • Multiaddrs have human-readable and efficient machine-readable representations.
  • Multiaddrs encapsulate well, allowing trivial wrapping and unwrapping of encapsulation layers.

Multiaddr was originally thought up by @jbenet.

Use cases

  • TODO: unpack the shortcomings of URLs

    • example: hostnames in https://
      • can't sidestep DNS
      • can't use different SNI vs. Host headers
      • can't do http-over-utp
      • TODO check out how http/1.1 vs. http/2 is distinguished
    • rift between filesystem, web, and databases
  • TODO: case study: domain fronting

  • TODO: case study: tunnelling

  • TODO: case study: http proxying

  • TODO: case study: multi-hop circuit relay

  • TODO: case study: protocol migrations (e.g. ip4/ip6, 4in6, 6in4)

Encapsulation based on context

Although multiaddrs are self-describing, it's possible to further encapsulate them based on context. For example in a web browser, it's obvious that, given a hostname, HTTP should be spoken. The specifics of this HTTP connection are not important (expect maybe the use of TLS), and will be derived from the browser's capabilities and configuration.

  1. example.com/index.html
  2. /http/example.com/index.html
  3. /tls/sni/example.com/http/example.com/index.html
  4. /dns4/example.com/tcp/443/tls/sni/example.com/http/example.com/index.html
  5. /ip4/1.2.3.4/tcp/443/tls/sni/example.com/http/example.com/index.html

The resulting layers of encapsulation reflect exactly how the bidirectional stream between client and server is constructed.

Now you can imagine how based on the browser's configuration, the multiaddr might look different. For example you could use HTTP proxying or SOCKS proxying, or use domain fronting to evade censorship. This kind of proxying is of course possible without multiaddr, but only with multiaddr do we have a way of consistently addressing these networking constructions.

Specification

  • Human-readable multiaddr: (/<protoName string>/<value string>)+
    • Example: /ip4/127.0.0.1/udp/1234
  • Machine-readable multiaddr: (<protoCode uvarint><value []byte>)+
    • Same example: 0x4 0x7f 0x0 0x0 0x1 0x91 0x2 0x4 0xd2
    • Values are usually length-prefixed with a uvarint

Multiaddr and all other multiformats use unsigned varints (uvarint). Read more about it in multiformats/unsigned-varint.

Encoding

TODO: specify the encoding (byte-array to string) procedure

Decoding

TODO: specify the decoding (string to byte-array) procedure

Protocols

See protocols.csv for a list of protocol codes and names, and protocols/ for specifications of the currently supported protocols.

TODO: most of these are way underspecified

  • /ip4, /ip6
  • /dns4, /dns6
  • /dnsaddr
  • /tcp
  • /udp
  • /utp
  • /tls
  • /ws, /wss
  • /ipfs
  • /p2p-circuit
  • /p2p-webrtc-star, /p2p-webrtc-direct
  • /p2p-websocket-star
  • /onion

Implementations

TODO: reconsider these alpha/beta/stable labels

Contribute

Contributions welcome. Please check out the issues.

Check out our contributing document for more information on how we work, and about contributing in general. Please be aware that all interactions related to multiformats are subject to the IPFS Code of Conduct.

Small note: If editing the README, please conform to the standard-readme specification.

License

This repository is only for documents. All of these are licensed under the CC-BY-SA 3.0 license, © 2016 Protocol Labs Inc. Any code is under a MIT © 2016 Protocol Labs Inc.