Interoperability Impacts of IPv6 Interworking with Existing IPv4 SIP Implementations
draft-klatsky-sipcore-ipv6-impact-ipv4-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Carl Klatsky , Olle E. Johansson , Rifaat Shekh-Yusef , Andrew Hutton , Gonzalo Salgueiro | ||
| Last updated | 2015-04-08 (Latest revision 2014-10-05) | ||
| 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
This document captures potential impacts to IPv4 SIP implementations when interworking with IPv6 SIP implementations. Although some amount of interworking translation will occur at the network and application layers, an IPv4 SIP application may still encounter a SIP message with some IPv6 values in it, resulting in unforeseen error conditions. Such potential scenarios will be identified in this document so that SIP application developers can define solutions to handle these cases. Note, this document is not intended to be an exhaustive list, rather to provide an overview of some of the more commonly encountered potential scenarios.
Authors
Carl Klatsky
Olle E. Johansson
Rifaat Shekh-Yusef
Andrew Hutton
Gonzalo Salgueiro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)