Add connectivity site references

[salmad3]

Context

Adds references to the new connectivity site: connectivity.libp2p.io

• Added a simple reference section doc.
• Added to left nav bar.
• Added ending sentence on the transport index.
• closes #218

Latest preview

Please view the latest Fleek preview here.

[filecorgi]

• Image optimization came back clean!
• Hugo build was successful! found div [

  Exchange Bytes

  When you make a connection from your computer to a machine on the internet, chances are pretty good you’re sending your bits and bytes using TCP/IP, the wildly successful combination of the Internet Protocol, which handles addressing and delivery of data packets, and the Transmission Control Protocol, which ensures that the data that gets sent over the wire is received completely and in the right order.

  Because TCP/IP is so ubiquitous and well-supported, it’s often the default choice for networked applications. In some cases, TCP adds too much overhead, so applications might use UDP, a much simpler protocol with no guarantees about reliability or ordering.

  While TCP and UDP (together with IP) are the most common protocols in use today, they are by no means the only options. Alternatives exist at lower levels (e.g. sending raw ethernet packets or bluetooth frames), and higher levels (e.g. QUIC, which is layered over UDP).

  The foundational protocols that move bits around are called transports, and one of libp2p’s core requirements is to be transport agnostic. This means that the decision of what transport protocol to use is up to the developer, and an application can support many different transports at the same time. Learn about the fundamentals of transport protocols in libp2p.

  To better visualize the types of libp2p connections, check out the connectivity site which outlines the different types of connectivity in libp2p.

  • Listening and Dialing

  Transports are defined in terms of two core operations, listening and dialing. Learn about how peers use both interfaces in libp2p.

  • QUIC

  QUIC is a new transport protocol that provides an always-encrypted, stream-multiplexed connection built on top of UDP. Learn about QUIC and how it is used in libp2p.

  • WebTransport

  WebTransport is a new specification that uses QUIC to offer an alternative to WebSocket. Conceptually, it can be considered WebSocket over QUIC.Learn about WebTransport and how it is used in libp2p.

  • WebRTC

  WebRTC is a new specification that uses QUIC to offer an alternative to WebSocket. Conceptually, it can be considered WebSocket over QUIC.Learn about WebTransport and how it is used in libp2p.

  ] found div [

  Connectivity in libp2p

  Check out the connectivity site for types of connectivity in libp2p.

  ]