RFC 6889: Analysis of Stateful 64 Translation

Publisher

IETF / RFC Editor

URL

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

Published

2013-04-01

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

IETF Trust Legal Provisions; no-redistribution; short excerpts and locators only

Source notes citing this source

• Because NAT64 rewrites only IP and transport headers, IPv4 address literals inside SIP headers and SDP c= lines cross a NAT64 untranslated. Without ICE, media latching or an SBC/ALG, an IPv6-only phone behind NAT64 is likely to get one-way or no audio with an IPv4-only SIP peer. inferred in context
• RFC 6889 identifies referrals as a NAT64 hazard: when a node on the IPv4 side passes the other endpoint's address to a node that cannot reach the NAT64, the referred connection fails. in context
• RFC 6889 (Informational, April 2013) concludes that stateful NAT64 creates no SIP-specific problem: the usual NAT traversal techniques (ICE, SIP keepalives, media latching, embedded SIP ALGs) apply when a NAT64 is in the path. in context

Cite this source record

APA

WarmTransfer. (2013, April 1). RFC 6889: Analysis of Stateful 64 Translation. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-6889-stateful-64-analysis

BibTeX

@misc{warmtransfer-rfc-6889-stateful-64-analysis,
  title  = {RFC 6889: Analysis of Stateful 64 Translation},
  author = {{WarmTransfer}},
  year   = {2013},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-6889-stateful-64-analysis},
  note   = {IETF / RFC Editor, accessed 2026-10-02}
}