Use credentials for message integrity
04STUN defines short-term and long-term credential mechanisms and integrity attributes.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 9 ↗
RFC 8489 · § 9EXAMPLE
3 / 3
03
The server verifies integrity before accepting the authenticated request.
The server verifies integrity before accepting the authenticated request.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 5389RFC 8489 § 19
This revision adds DTLS-over-UDP and SHA-256 message-integrity support and updates retransmission-timer guidance.
Read the updated RFC section ↗A message integrity HMAC provides different protection from the CRC-based FINGERPRINT attribute.
- A message integrity HMAC provides different protection from the CRC-based FINGERPRINT attribute.
- Long-term authentication uses challenge material such as realm and nonce as specified.
The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy