[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Date: Wed, 22 Sep 2010 11:46:32 -0400
Subject: RE: [v4tov6transition] Any Experience with Using Behave's Stateless
NAT-PT for IMS-SIP VoIP Application...
Thread-Topic: [v4tov6transition] Any Experience with Using Behave's
Stateless NAT-PT for IMS-SIP VoIP Application...
Content-Type: text/plain; charset="us-ascii"
Yes sir Cameron, hence, my queries below. Most of the SIP-SDP-RTPv4 to SIP-=
SDP-RTPv6 lab evals I've seen have utilized the deprecated NAT-PT, so I was=
curious about anyone's experience yet with the Behave group's "newer" algo=
rithms (yes, normally implemented in an SBC for RTP/UDP/IP-version translat=
ion) and its interaction with an IMS network (VoIP network) requesting tran=
slation services from it.
From: Cameron Byrne [mailto:email@example.com]
Sent: Wednesday, September 22, 2010 11:27 AM
To: Mosley, Leonard; firstname.lastname@example.org; email@example.com; v6ops@ops.=
Subject: Re: [v4tov6transition] Any Experience with Using Behave's Stateles=
s NAT-PT for IMS-SIP VoIP Application...
When you must translate between protocols, most service providers use
sip b2bua aka an sbc.
On 9/22/10, Mosley, Leonard <firstname.lastname@example.org> wrote:
> Greetings Fred et al, I had a couple of inquiries concerning use of the
> Behave WG NAT-PT algorithms:
> 1) I was wondering what vendors currently are implementing the Behav=
> WG's NAT-PT algorithms?
> 2) Has anyone had any experience testing or implementing the statele=
> algorithm for use cases involving IMS SIPv4 VoIP clients calling SIPv6
> clients and vice versa. Such use cases assume an architecture where ther=
> is a co-existence period in the network consisting of both "legacy" SIPv4
> clients and "newer" SIPv6 (dual-stack and/or v6-only) clients.
> 3) I'm curious about RTP performance under moderate to heavy call lo=
> as well as NAT-PT interaction with IMS-ALG. If anyone can share at a
> high-level that would be great.
> Len Mosley
> Time Warner Cable
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely =
> the use of the individual or entity to which it is addressed. If you are =
> the intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this E-mail is strictly prohibited and may=
> unlawful. If you have received this E-mail in error, please notify the
> sender immediately and permanently delete the original and any copy of th=
> E-mail and any printout.
Sent from my mobile device
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.