RFC 8760: The Session Initiation Protocol (SIP) Digest Access Authentication Scheme

Publisher

RFC Editor / IETF

URL

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

Published

2020-03-01

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

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

Source notes citing this source

• A registrar that offers only SHA-256 digest challenges to a UA that supports only MD5 will probably cause authentication to fail, which shows up as repeated challenges or an abandoned registration. inferred in context
• RFC 8760 updates RFC 3261 to allow SHA-256 and SHA-512/256 in SIP digest authentication. in context
• RFC 8760 keeps MD5 only for backward compatibility with RFC 2617 and marks its use NOT RECOMMENDED. in context
• Under RFC 8760 a UAS may send several WWW-Authenticate or Proxy-Authenticate headers in order of preference, and a UAC seeing several for the same realm should use the topmost one it supports. in context
• RFC 8760 requires a UAS to always include a qop parameter in WWW-Authenticate and Proxy-Authenticate header values. in context

Cite this source record

APA

WarmTransfer. (2020, March 1). RFC 8760: The Session Initiation Protocol (SIP) Digest Access Authentication Scheme. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-8760-sip-digest-sha256

BibTeX

@misc{warmtransfer-rfc-8760-sip-digest-sha256,
  title  = {RFC 8760: The Session Initiation Protocol (SIP) Digest Access Authentication Scheme},
  author = {{WarmTransfer}},
  year   = {2020},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-8760-sip-digest-sha256},
  note   = {RFC Editor / IETF, accessed 2026-09-25}
}