Source record · tier 1 standards and regulators
RFC 7044: An Extension to the Session Initiation Protocol (SIP) for Request History Information
- Publisher
- IETF / RFC Editor
- URL
- https://www.rfc-editor.org/rfc/rfc7044.html
- Published
- 2014-02-01
- Updated
- unknown
- Accessed
- 2026-09-25
- HTTP status
- 200
- License
- IETF Trust; RFC text may be reproduced with attribution under BCP 78; short excerpts and locators only
Source notes citing this source
- RFC 7044 is the Standards Track History-Info specification and obsoletes RFC 4244. in context
- RFC 7044 defines a Privacy priv-value 'history' that asks for History-Info entries to be anonymized, with a Privacy Service replacing un-anonymized targeted-to URIs with anonymous.invalid URIs at domain boundaries. in context
- Each History-Info entry carries a mandatory index parameter, written as dot-separated integers such as 1.1.2, that records the chronological order and branching of retargeting hops. in context
- RFC 7044 (February 2014) defines the SIP History-Info header, which records how and why a request reached its target through retargeting such as forwarding, and it obsoletes RFC 4244. in context
- History-Info entries can carry a Reason header with the SIP response code that caused the retargeting, for example 302 for unconditional forwarding, 486 for busy, 408 for timeout or 480 for temporarily unavailable. in context
Cite this source record
APA
WarmTransfer. (2014, February 1). RFC 7044: An Extension to the Session Initiation Protocol (SIP) for Request History Information. WarmTransfer. https://warmtransfer.net/knowledge/sources/ietf-rfc-7044-history-info
BibTeX
@misc{warmtransfer-ietf-rfc-7044-history-info,
title = {RFC 7044: An Extension to the Session Initiation Protocol (SIP) for Request History Information},
author = {{WarmTransfer}},
year = {2014},
url = {https://warmtransfer.net/knowledge/sources/ietf-rfc-7044-history-info},
note = {IETF / RFC Editor, accessed 2026-09-25}
}