bk99.de entertain the web since 1997

bk99.de
RFC · TransportStandard explained

RFC 4960: SCTP: Message-oriented transport over multiple paths

Summary

RFC 4960 defines SCTP with message framing, multihoming and several independent streams per connection. RFC 4960 was superseded by RFC 9260. Transport protocols can structure reliability differently from TCP.

Ideas

  • Message boundaries are preserved.
  • Multiple streams reduce head-of-line blocking.
  • Multihoming allows alternative network paths.

Insights

  • Besides the technology, wide adoption depends heavily on operating systems and middleboxes.

Remarks

  • RFC 4960 has the status “Proposed Standard”; current errata and successor documents should also be checked.

Recommendations

  • Test SCTP through all firewalls and NAT boundaries.
  • Use multihoming only with monitored, truly independent paths.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2021

RFC 9000: QUIC: Secure transport over UDP

RFC 9000 defines QUIC with encrypted connections, multiple streams and path migration on top of UDP. Transport innovation can be rolled out over UDP without waiting for operating system kernels. Encrypted control data improves privacy and makes network diagnostics harder.

RFC · 1981

RFC 793: TCP: Reliable data streams over IP

RFC 793 defines TCP as an ordered, reliable and bidirectional byte stream between endpoints. RFC 793 was superseded by RFC 9293. TCP separates the reliability of transport from the unreliability of individual network paths.

RFC · 2001

RFC 3168: ECN: Signalling congestion without packet loss

RFC 3168 lets routers mark congestion in IP packets before queues have to drop packets. Packet loss is an expensive congestion signal and not strictly necessary. Cooperative endpoints can significantly reduce latency under load.