RFC 6157: IPv6 Transition in the Session Initiation Protocol (SIP)

Publisher

IETF / RFC Editor

URL

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

Published

2011-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

• Under RFC 6157 each media description in an SDP answer must use the same network/address type as the matching media description in the offer, so an IP4 offer line cannot be answered with IP6 or the reverse. in context
• RFC 6157 says dual-stack (IPv4/IPv6) SIP user agents SHOULD use ICE procedures to gather both IPv4 and IPv6 addresses for every offer they generate, so that IPv4-only and IPv6-only answerers can both set up a session. in context
• RFC 6157 uses ICE, not ANAT, as its mechanism for IPv4/IPv6 media interworking and does not reference RFC 4091 or RFC 4092. in context
• RFC 6157 requires a SIP proxy that relays requests between IPv4 and IPv6 networks to be configured to Record-Route so it stays in the signalling path for the dialog. in context
• RFC 6157 recommends that SIP user agents support the STUN relay usage (TURN) so that, for example, an IPv6-only agent can get an IPv4 relayed address for media. in context
• RFC 6157 (IPv6 Transition in SIP) is a Standards Track RFC published April 2011 that updates RFC 3264 (the SDP offer/answer model). in context

Cite this source record

APA

WarmTransfer. (2011, April 1). RFC 6157: IPv6 Transition in the Session Initiation Protocol (SIP). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-6157-ipv6-transition-sip

BibTeX

@misc{warmtransfer-rfc-6157-ipv6-transition-sip,
  title  = {RFC 6157: IPv6 Transition in the Session Initiation Protocol (SIP)},
  author = {{WarmTransfer}},
  year   = {2011},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-6157-ipv6-transition-sip},
  note   = {IETF / RFC Editor, accessed 2026-10-02}
}