Source note · IPv6 for voice and UC platforms
RFC 4092 defines the SIP option-tag sdp-anat and says a SIP entity generating an offer that uses ANAT semantics SHOULD put sdp-anat in a Require header field.
Checked 2026-10-02
SIP entities generating an offer that uses the ANAT semantics SHOULD place the sdp-anat option-tag in a Require header field.
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP / ANAT
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 4092
- Checked
- 2026-10-02
Sources
- RFC 4092 info page: Usage of the SDP ANAT Semantics in SIP — IETF / RFC Editor · tier 1 standards and regulators · Info page abstract
Cite this note
APA
WarmTransfer. (2026, October 2). IPv6 for voice and UC platforms: source note ipv6-voice-rfc4092-sdp-anat-option-tag. WarmTransfer. https://warmtransfer.net/knowledge/claims/ipv6-voice-rfc4092-sdp-anat-option-tag
BibTeX
@misc{warmtransfer-claim-ipv6-voice-rfc4092-sdp-anat-option-tag,
title = {IPv6 for voice and UC platforms: source note ipv6-voice-rfc4092-sdp-anat-option-tag},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/ipv6-voice-rfc4092-sdp-anat-option-tag},
note = {Source note ipv6-voice-rfc4092-sdp-anat-option-tag, checked 2026-10-02}
}