Re: [rtcweb] NAT behavior heuristics

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Sun, 05 August 2012 22:42 UTC

Return-Path: <tireddy@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B55521F8578 for <rtcweb@ietfa.amsl.com>; Sun, 5 Aug 2012 15:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3NceABvaGFMX for <rtcweb@ietfa.amsl.com>; Sun, 5 Aug 2012 15:42:18 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 53B9621F8577 for <rtcweb@ietf.org>; Sun, 5 Aug 2012 15:42:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tireddy@cisco.com; l=1781; q=dns/txt; s=iport; t=1344206538; x=1345416138; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=WFdSx7eV/WwF0UsoV/m82ivVHTubEG2K9Cmw7iREqh4=; b=VpGqRhqJYDjm2zn/b/Lco+2dz00MV9v+SydYu4Uq1rI7ltBrr6Mw4Sd/ D5sT3iX8gZtAMGfUbwAI+e76XhBgyDw4HV/B5OEbH3YVwxk90+y0dLJFE 4czkaSx7LK+kIUkUPcdvelVFw75GdwRhcWj40MGHH6oYfIgTlPLMWXJi4 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAGj2HlCtJV2d/2dsb2JhbABFuTyBB4IgAQEBAwESASc/DAQCAQgOAwQBAQEKFAkHIREUCQgCBA4FCBqHXAMGBgubL5UeDYlOimNnhiRgA5N2gmeJdYMdgWaCXw
X-IronPort-AV: E=Sophos;i="4.77,715,1336348800"; d="scan'208";a="108661679"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 05 Aug 2012 22:42:18 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q75MgHtC020215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 5 Aug 2012 22:42:17 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.216]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0298.004; Sun, 5 Aug 2012 17:42:17 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Cameron Byrne <cb.list6@gmail.com>
Thread-Topic: [rtcweb] NAT behavior heuristics
Thread-Index: Ac1w1ovfvzUgFxvbR0qnhkeGI2kOuAAVj+eAAAB2nYAAdXC7AAAK960AAAlqvrAACyyyAAAKKo2w
Date: Sun, 5 Aug 2012 22:42:17 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A1477C1BA@xmb-rcd-x10.cisco.com>
References: <038b01cd70d6$8c5bc870$a5135950$@com> <CABkgnnW+pCnDZuYHDj6=7xdqRwM6AO48RrC1xhMrvFZbUBgtyw@mail.gmail.com> <04ff01cd7104$be09bed0$3a1d3c70$@com> <501E1E40.8070203@jesup.org> <CAD6AjGTrd0d9dm5HC2xr=ZAU2DmU55Sdkm6rH8NO4sJMMuLScA@mail.gmail.com> <913383AAA69FF945B8F946018B75898A1477C17F@xmb-rcd-x10.cisco.com> <CAD6AjGTEH+12WfKavx7H_xpfeynEL6W33L9nD98_vztVodGTuA@mail.gmail.com>
In-Reply-To: <CAD6AjGTEH+12WfKavx7H_xpfeynEL6W33L9nD98_vztVodGTuA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.78.115]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19088.001
x-tm-as-result: No--48.235100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Randell Jesup <randell-ietf@jesup.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "phdgang@gmail.com" <phdgang@gmail.com>
Subject: Re: [rtcweb] NAT behavior heuristics
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Aug 2012 22:42:19 -0000

> -----Original Message-----
> From: Cameron Byrne [mailto:cb.list6@gmail.com]
> Sent: Sunday, August 05, 2012 4:22 PM
> To: Tirumaleswar Reddy (tireddy)
> Cc: Randell Jesup; rtcweb@ietf.org; phdgang@gmail.com
> Subject: Re: [rtcweb] NAT behavior heuristics
> 
> On Sun, Aug 5, 2012 at 3:05 PM, Tirumaleswar Reddy (tireddy)
> <tireddy@cisco.com> wrote:
> >> Fyi. I have not seen any traction for pcp anywhere in the mobile
> space.
> >
> > http://tools.ietf.org/html/draft-chen-pcp-mobile-deployment-01
> describes usage of PCP in Mobile Deployments.
> >
> > --Tiru.
> >
> 
> Yep, that's  an I-D.
> 
> And, it says things like "Without
>    the particular considerations , PCP may not provide desirable
>    outcomes.  Some default behaviours may even cause negative impacts
> or
>    system failures in a mobile environment.  "
> 
> Got an operators with a timeline on supporting it?  How about a mobile
> OS that plans to support PCP, because you will need both.  And, that
> would be interesting information.

In my conversation Nokia supports PCP and my understanding is it can be implemented as library in user space without any support from kernel.

> 
> I asked around in Vancouver about PCP, and all the operators i spoke
> to said no-plans, no motivation.  But, that was a small sample.
> 
> In any event, my only point is that RTCWEB should NOT be counting on
> PCP.  If PCP is a tool you have, use it.  My point: it is not a tool
> you have.

Yes, If the tool is gets deployed in future it will not just help RTCWEB and various other applications. Even with IPv6 this draft refers to Firewalls deployed by Mobile Networks and Firewalls usually timeout UDP sessions in 30 seconds.

--Tiru.

> 
> CB