RFC 8217 — Clarifications for When to Use the name-addr Production in SIP Messages

Publisher

IETF / RFC Editor

URL

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

Published

2017-08

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

IETF Trust / BCP 78; permitted with the RFC's own copyright and license notices intact

Source notes citing this source

• An attended transfer's Refer-To carries an escaped Replaces, which contains both a question mark separating the header from the URI and semicolons separating the dialog tags, so under RFC 8217 that Refer-To must be written in the name-addr form with angle brackets rather than as a bare address. inferred in context
• RFC 8217 updates RFC 3515 and RFC 3892 to require that where a SIP header field grammar allows a choice between the name-addr and addr-spec forms, the addr-spec form must not be used if its value would contain a comma, a semicolon or a question mark, and that any URI parameters are contained within angle brackets. in context

Cite this source record

APA

WarmTransfer. (n.d.). RFC 8217 — Clarifications for When to Use the name-addr Production in SIP Messages. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-8217-name-addr

BibTeX

@misc{warmtransfer-rfc-8217-name-addr,
  title  = {RFC 8217 — Clarifications for When to Use the name-addr Production in SIP Messages},
  author = {{WarmTransfer}},
  year   = {2017},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-8217-name-addr},
  note   = {IETF / RFC Editor, accessed 2026-09-16}
}