CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 22:46:11 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=lVaXK6HHiFOEYyWBo7Wbyvr0clpBSKHFwUhZGjClrtk-1760136371-1.0.1.1-I.c91zvepfR3DDANxxMS8hW1VRl25G5OUwaO1hWJDPfUz2Vlx5UogwAzdbKCk3pGiAgInN1gnErby05HlpEtXgk3A2883gkNZm3dxhS4eYM; path=/; expires=Fri, 10-Oct-25 23:16:11 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c9a6fa58973e92-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5928 » RFC Editor
Search RFCs
RFC 5928
Traversal Using Relays around NAT (TURN) Resolution Mechanism, August 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Updated by:
- RFC 7350, RFC 8553
- Author:
- M. Petit-Huguenin
- Stream:
- IETF
- Source:
- behave (tsv)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5928
Discuss this RFC: Send questions or comments to the mailing list behave@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5928
Abstract
This document defines a resolution mechanism to generate a list of server transport addresses that can be tried to create a Traversal Using Relays around NAT (TURN) allocation. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us