RFC 7714: AES-GCM Authenticated Encryption in the Secure Real-time Transport Protocol (SRTP)

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc7714.html

Published

2015-12-01

Updated

unknown

Accessed

2026-09-23

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78); no-redistribution; short excerpts and locators only

Source notes citing this source

• RFC 7714 requires the AES-GCM SRTP authentication tag to be a full 16 octets and forbids truncating it. in context
• RFC 7714 registers the DTLS-SRTP protection profiles SRTP_AEAD_AES_128_GCM {0x00, 0x07} and SRTP_AEAD_AES_256_GCM {0x00, 0x08}. in context
• RFC 7714 registers the SDES crypto suites AEAD_AES_128_GCM and AEAD_AES_256_GCM for AES-GCM authenticated encryption in SRTP. in context
• In AES-GCM SRTP the RTP header fields (including sequence number, timestamp, SSRC and any header extensions) are authenticated as associated data but not encrypted. in context
• Any AES-GCM SRTP implementation must support both AEAD_AES_128_GCM and AEAD_AES_256_GCM. in context
• AES-GCM SRTP uses a 96-bit master salt, not the 112-bit salt of the AES-CM suites. in context

Cite this source record

APA

WarmTransfer. (2015, December 1). RFC 7714: AES-GCM Authenticated Encryption in the Secure Real-time Transport Protocol (SRTP). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-7714-srtp-aes-gcm

BibTeX

@misc{warmtransfer-rfc-7714-srtp-aes-gcm,
  title  = {RFC 7714: AES-GCM Authenticated Encryption in the Secure Real-time Transport Protocol (SRTP)},
  author = {{WarmTransfer}},
  year   = {2015},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-7714-srtp-aes-gcm},
  note   = {IETF / RFC Editor, accessed 2026-09-23}
}