SIP Issues in Dual-stack Environments
draft-persson-sipping-sip-issues-dual-stack-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jasminko Mulahusic , Hakan Persson | ||
| Last updated | 2003-02-27 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The advent of IPv6 in addition to IPv4 makes hosts and servers dual- stack. SIP communications can be used in both environments but there is little understanding what will happen if some nodes are dual-stack while others, presently the majority, is IPv4 only enabled. This document describes some scenarios and associated issues when dual- stack users and servers try to communicate with IPv4 only hosts using SIP. It is not evident that interoperability is achieved, and if that is not the case, this would severely limit the usability of both SIP and IPv6.
Authors
Jasminko Mulahusic
Hakan Persson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)