[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: 3gpp transition solutions, revision -02
- To: <v6ops@ops.ietf.org>
- Subject: RE: 3gpp transition solutions, revision -02
- From: <Jasminko.W.Mulahusic@telia.se>
- Date: Fri, 8 Nov 2002 14:17:56 +0100
- Delivery-date: Fri, 08 Nov 2002 05:19:35 -0800
- Envelope-to: v6ops-data@psg.com
- Sender: owner-v6ops@ops.ietf.org
- Thread-index: AcKHIq+26S6eWct4Se++QeRqfLlc9AABeApQ
- Thread-topic: 3gpp transition solutions, revision -02
> This means that IMS itself has no interworking problems, no
> NATs, no NAT-PTs, and no IPv4 - it is only IPv6. Thus, there
> are no problems inside the IMS. The NAT-PT would come to the
> picture if, for instance, you have to place a call to another
> "system" that does not support v6. (It may be that you have
> to do another kind of translation as well, e.g. SIP to H.323,
> or SIP to ISUP, or whatever.)
>
> (BC) And if that is the case, the IWU that does this
> translation can be dual
> stacked, with its IPv6 stack talking to IMS and its IPv4 stack talking
> to the legacy system. If you do that, NAT-PT isn't needed.
>
that will take care of the signalling part. you still need a box to translate the media flow, which is not going through the ims.
jasminko