Source note · Passing call context with SIP UUI and custom headers
RFC 6648 (BCP 178, June 2012) says creators of new application-protocol parameters SHOULD NOT prefix their names with 'X-' or similar constructs.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- custom headers
- Deployment
- any
- Region
- not restricted
- Release range
- BCP 178
- Checked
- 2026-10-02
Sources
- RFC 6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols (BCP 178) — IETF / RFC Editor · tier 1 standards and regulators · Section 3
Cite this note
APA
WarmTransfer. (2026, October 2). Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-rfc6648-no-new-x-prefix. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-rfc6648-no-new-x-prefix
BibTeX
@misc{warmtransfer-claim-sip-uui-context-passing-rfc6648-no-new-x-prefix,
title = {Passing call context with SIP UUI and custom headers: source note sip-uui-context-passing-rfc6648-no-new-x-prefix},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-uui-context-passing-rfc6648-no-new-x-prefix},
note = {Source note sip-uui-context-passing-rfc6648-no-new-x-prefix, checked 2026-10-02}
}