[no subject]

["Mosley, Leonard" <len.mosley@twcable.com>]

"v6ops@ops.ietf.org"
	<v6ops@ops.ietf.org>
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...
Thread-Index: ActaaoseeoUFiTumTrOtp9zaN34IjgAAJV3A
Message-ID:
<EC91E98C3BC6A34B917F828067B9335C1535E733DE@PRVPEXVS07.corp.twcable.com>
References:
<EC91E98C3BC6A34B917F828067B9335C1535E73180@PRVPEXVS07.corp.twcable.com>
 <AANLkTin1gQhnS=w4+ehLyJOyO+mz0NNnz-4rD-N97ZEq@mail.gmail.com>
In-Reply-To: <AANLkTin1gQhnS=w4+ehLyJOyO+mz0NNnz-4rD-N97ZEq@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

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.

Tks,

Len...

-----Original Message-----
From: Cameron Byrne [mailto:cb.list6@gmail.com]
Sent: Wednesday, September 22, 2010 11:27 AM
To: Mosley, Leonard; behave@ietf.org; v4tov6transition@ietf.org; v6ops@ops.=
ietf.org
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.

Cameron

On 9/22/10, Mosley, Leonard <len.mosley@twcable.com> 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=
e
> WG's NAT-PT algorithms?
>
> 2)      Has anyone had any experience testing or implementing the statele=
ss
> algorithm for use cases involving IMS SIPv4 VoIP clients calling SIPv6
> clients and vice versa.  Such use cases assume an architecture where ther=
e
> 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=
ads
> as well as NAT-PT interaction with IMS-ALG.  If anyone can share at a
> high-level that would be great.
>
> Tks,
>
> 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 =
for
> the use 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
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this E-mail is strictly prohibited and may=
 be
> 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=
is
> 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.