RFC 5769: Test Vectors for Session Traversal Utilities for NAT (STUN)
In plain English — editorial summary, not part of the RFC
The Session Traversal Utilities for NAT (STUN) protocol defines several STUN attributes. The content of some of these -- FINGERPRINT, MESSAGE-INTEGRITY, and XOR-MAPPED-ADDRESS -- involve binary-logical operations (hashing, xor). This document provides test vectors for those attributes. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5769
- Published
- April 2010
- Authors
- R. Denis-Courmont
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5766Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Obsoleted
April 2010
- RFC 6062Traversal Using Relays around NAT (TURN) Extensions for TCP AllocationsCurrent
November 2010
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
- RFC 6156Traversal Using Relays around NAT (TURN) Extension for IPv6Obsoleted
April 2011
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 8016Mobility with Traversal Using Relays around NAT (TURN)Current
November 2016
- RFC 3489STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)Obsoleted
March 2003
- RFC 8656Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Current
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?