RFC 8656 — Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)

Publisher

RFC Editor / Internet Engineering Task Force

URL

https://www.rfc-editor.org/rfc/rfc8656.txt

Published

2020-02

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

IETF Trust legal provisions; permitted

Source notes citing this source

• RFC 8656 advises using a TURN server only when a direct communication path cannot be found, noting that relaying is costly to the TURN server's provider. in context
• RFC 8656 defines four transports between a TURN client and server (UDP, TCP, TLS over TCP and DTLS over UDP) and specifies that TURN always uses UDP between the server and the peer. in context
• RFC 8656 of February 2020 is the current Traversal Using Relays around NAT specification, defined as relay extensions to STUN, and its own header records that it obsoletes RFC 5766 and RFC 6156. in context

Cite this source record

APA

WarmTransfer. (n.d.). RFC 8656 — Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-8656-turn

BibTeX

@misc{warmtransfer-rfc-8656-turn,
  title  = {RFC 8656 — Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)},
  author = {{WarmTransfer}},
  year   = {2020},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-8656-turn},
  note   = {RFC Editor / Internet Engineering Task Force, accessed 2026-09-16}
}