Home › Entities › request_for_comments › RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism

RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism

request for comments publication
Place request_for_comments Q47463277
Press Enter · cited answer in seconds

RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism

Summary

RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism is a Request for Comments[1].

Key Facts

  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism authored Traversal Using Relays around NAT (TURN) Resolution Mechanism — author (P50): Marc Petit-Huguenin[2].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's instance of is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — instance of (P31): Request for Comments[3].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's publisher is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — publisher (P123): Internet Engineering Task Force[4].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's DOI is recorded as 10.17487/RFC5928[5].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's language of work or name is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — language of work or name (P407): English[6].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's publication date is recorded as +2010-08-01T00:00:00Z[7].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's RfC ID is recorded as 5928[8].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's main subject is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — main subject (P921): Traversal Using Relays around NAT[9].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's work available at URL is recorded as https://tools.ietf.org/html/rfc5928[10].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5928.txt[11].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5928.txt[12].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5928.txt.pdf[13].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's number of pages is recorded as {'unit': '1', 'amount': '+11'}[14].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's title is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism[15].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's amended by is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — amended by (P2567): RFC 7350: Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)[16].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's amended by is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — amended by (P2567): RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names[17].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's cites work is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — cites work (P2860): RFC 2119: Key words for use in RFCs to Indicate Requirement Levels[18].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's cites work is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — cites work (P2860): RFC 2782: A DNS RR for specifying the location of services (DNS SRV)[19].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's cites work is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — cites work (P2860): RFC 3958: Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)[20].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's cites work is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — cites work (P2860): RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2[21].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's cites work is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — cites work (P2860): RFC 5389: Session Traversal Utilities for NAT (STUN)[22].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's cites work is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — cites work (P2860): RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)[23].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's cites work is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — cites work (P2860): RFC 2629: Writing I-Ds and RFCs using XML[24].
  • RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's DBLP publication ID is recorded as journals/rfc/rfc5928[25].

Body

Designation and Status

RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism's instance of is recorded as Traversal Using Relays around NAT (TURN) Resolution Mechanism — instance of (P31): Request for Comments[3].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  4. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  5. [6] ↑ . RFC Index. Retrieved . wikidata.org.
  6. [7] ↑ . RFC Index. Retrieved . wikidata.org.
  7. [8] ↑ . RFC Index. Retrieved . wikidata.org.
  8. [9] ↑ . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . wikidata.org.
  11. [12] ↑ . RFC Index. Retrieved . wikidata.org.
  12. [13] ↑ . RFC Index. Retrieved . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC Index. Retrieved . wikidata.org.
  15. [16] ↑ . RFC Index. Retrieved . wikidata.org.
  16. [17] ↑ . RFC Index. Retrieved . wikidata.org.
  17. [18] ↑ . wikidata.org.
  18. [19] ↑ . wikidata.org.
  19. [20] ↑ . wikidata.org.
  20. [21] ↑ . wikidata.org.
  21. [22] ↑ . wikidata.org.
  22. [23] ↑ . wikidata.org.
  23. [24] ↑ . wikidata.org.
  24. [25] ↑ . DBLP Dataset 2021-01-02. Retrieved . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-5928-traversal-using-relays-around-nat-turn-resolution-mechanism
MLA “RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-5928-traversal-using-relays-around-nat-turn-resolution-mechanism.
BibTeX @misc{4ortxyz_rfc-5928-traversal-using-relays-around-nat-turn-resolution-mechanism_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-5928-traversal-using-relays-around-nat-turn-resolution-mechanism}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism — https://4ort.xyz/entity/rfc-5928-traversal-using-relays-around-nat-turn-resolution-mechanism (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-5928-traversal-using-relays-around-nat-turn-resolution-mechanism · Last refreshed: