IPv6-IPv4 Translation mechanism for SIP-based services in Third Generation Partnership Project (3GPP) Networks
draft-elmalki-sipping-3gpp-translator-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Karim El Malki | ||
| Last updated | 2003-12-04 | ||
| 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
There have been discussions on the v6ops mailing list and at IETF meetings regarding the suitability of translators (i.e. NAT-PT) as mechanisms for IPv4 to IPv6 transition. It has often been stated that NAT-PT is not a mechanism to be recommended in general to solve the IPv6-IPv4 transition problem. There have also been discussions regarding special scenarios where some form of translators could be deployed if their use is documented appropriately. The aim of this draft is to document the rationale for using translators in 3GPP (Third Generation Partnership Project) networks for IPv6-only SIP- based IP Multimedia Subsystem (IMS) services and to describe a solution to the problem.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)