Re: [v4tov6transition] Any Experience with Using Behave's Stateless NAT-PT for IMS-SIP VoIP Application...

"Mosley, Leonard" <len.mosley@twcable.com> Wed, 22 September 2010 15:46 UTC

Return-Path: <len.mosley@twcable.com>
X-Original-To: v4tov6transition@core3.amsl.com
Delivered-To: v4tov6transition@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54A1128C102; Wed, 22 Sep 2010 08:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.837
X-Spam-Level:
X-Spam-Status: No, score=0.837 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SXspGcgd8Z2V; Wed, 22 Sep 2010 08:46:24 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by core3.amsl.com (Postfix) with ESMTP id 3DCDC28C0EF; Wed, 22 Sep 2010 08:46:20 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.56,407,1280721600"; d="scan'208";a="132388794"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 22 Sep 2010 11:46:33 -0400
Received: from PRVPEXVS07.corp.twcable.com ([10.136.163.35]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Wed, 22 Sep 2010 11:46:32 -0400
From: "Mosley, Leonard" <len.mosley@twcable.com>
To: Cameron Byrne <cb.list6@gmail.com>, "behave@ietf.org" <behave@ietf.org>, "v4tov6transition@ietf.org" <v4tov6transition@ietf.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>
Date: Wed, 22 Sep 2010 11:46:32 -0400
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
Subject: Re: [v4tov6transition] Any Experience with Using Behave's Stateless NAT-PT for IMS-SIP VoIP Application...
X-BeenThere: v4tov6transition@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <v4tov6transition.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v4tov6transition>
List-Post: <mailto:v4tov6transition@ietf.org>
List-Help: <mailto:v4tov6transition-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 15:46:26 -0000

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" algorithms (yes, normally implemented in an SBC for RTP/UDP/IP-version translation) and its interaction with an IMS network (VoIP network) requesting translation 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 Stateless 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 Behave
> WG's NAT-PT algorithms?
>
> 2)      Has anyone had any experience testing or implementing the stateless
> algorithm for use cases involving IMS SIPv4 VoIP clients calling SIPv6
> clients and vice versa.  Such use cases assume an architecture where there
> 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 loads
> 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 this
> E-mail and any printout.
>

--
Sent from my mobile device

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 this E-mail and any printout.