Source note · Call transfer semantics REFER and Replaces
The RFC Editor's document information pages for RFC 7647 and RFC 8217 carry neither an Updated by field nor an Obsoleted by field, so the 2 documents that update RFC 3515 are not themselves updated or obsoleted.
Checked 2026-09-16
- Vendor
- IETF
- Product
- Session Initiation Protocol
- Subsystem
- Document status
- Deployment
- not restricted
- Region
- not restricted
- Release range
- not restricted
- Checked
- 2026-09-16
Sources
- RFC 7647: Clarifications for the Use of REFER with RFC 6665 — RFC Editor document information — IETF / RFC Editor · tier 1 standards and regulators · RFC Editor information pages for RFC 7647 and RFC 8217
Cite this note
APA
WarmTransfer. (2026, September 16). Call transfer semantics REFER and Replaces: source note xfersem-the-two-updating-rfcs-are-themselves-current. WarmTransfer. https://warmtransfer.net/knowledge/claims/xfersem-the-two-updating-rfcs-are-themselves-current
BibTeX
@misc{warmtransfer-claim-xfersem-the-two-updating-rfcs-are-themselves-current,
title = {Call transfer semantics REFER and Replaces: source note xfersem-the-two-updating-rfcs-are-themselves-current},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/xfersem-the-two-updating-rfcs-are-themselves-current},
note = {Source note xfersem-the-two-updating-rfcs-are-themselves-current, checked 2026-09-16}
}