Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)

"Dan Wing" <dwing@cisco.com> Fri, 16 September 2011 18:01 UTC

Return-Path: <dwing@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 141E021F85AA for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 11:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.191
X-Spam-Level:
X-Spam-Status: No, score=-103.191 tagged_above=-999 required=5 tests=[AWL=-0.592, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ZfLp6NN4J8G9 for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 11:01:47 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 780DB21F8582 for <rtcweb@ietf.org>; Fri, 16 Sep 2011 11:01:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=876; q=dns/txt; s=iport; t=1316196243; x=1317405843; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=ZLceKa3cnssqTvnc8NyueZ8ngEC+7uIQpK1WL52z+Fs=; b=G7WGc9+eCBAkD6zfkztxWVkCQrXmfDqe9CUpVw8qiAFzbfT6uPmBWIv/ vOH5OWVV1HKvaiZJwoml7QiSKjyKXwrdScIKy3MolEMphOZONXWumTxHm aDmOrP0msf19k4fLccQDcciNckc4fOojkQY11nLzSANdomjnC5vT7QDmN g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqwAAEKOc06rRDoJ/2dsb2JhbABCmGGBbI0Sd4FTAQEBAQMICgEXEEsBAwIJDwIEAQEBIwQHGSMKCQgBAQQBEgsXh1mWGQGeLoZ4BIdvnSc
X-IronPort-AV: E=Sophos;i="4.68,394,1312156800"; d="scan'208";a="2604729"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 16 Sep 2011 18:04:02 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p8GI429e020690; Fri, 16 Sep 2011 18:04:02 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Randell Jesup'" <randell-ietf@jesup.org>, <rtcweb@ietf.org>
References: <CABw3bnO+85i-TtuqS+P4n+rYgyxyoASc8HXpADhy4QPTC0_szA@mail.gmail.com> <6F469757-6B5C-4DC9-BC34-026F34C7E508@phonefromhere.com> <CAD5OKxvCSJWS+F72P_WOFapmtffkLCSSe3A-rDEUOhNjWcoh4A@mail.gmail.com> <E44893DD4E290745BB608EB23FDDB7620B39D8@008-AM1MPN1-043.mgdnok.nokia.com> <CAD5OKxtt9phWr9Vrn5J1STxA9airR8g-tHMnddFP=QwrTHuPcA@mail.gmail.com> <4E724E25.1000204@jesup.org>
In-Reply-To: <4E724E25.1000204@jesup.org>
Date: Fri, 16 Sep 2011 11:04:02 -0700
Message-ID: <092201cc749b$0450aa50$0cf1fef0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acxz23Z/F/tohcldR+Sq5iOFh/8D3wAvzcJQ
Content-Language: en-us
Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)
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: Fri, 16 Sep 2011 18:01:48 -0000

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Randell Jesup
> Sent: Thursday, September 15, 2011 12:13 PM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket
> Transport for Session Initiation Protocol (SIP)
> 
> On 9/15/2011 11:57 AM, Roman Shpount wrote:
> > Actually SIP over UDP is what is typically used for mobile apps now.
> > If you are doing SIP from the public IP, you do not need to maintain
> > the connection even if TCP/TLS is used.
> 
> Markus had a point: SIP over UDP requires keepalives if it's behind a
> NAT as well.  So maybe it's not such a big difference, depending on the
> keepalive rates needed (and for UDP circa 30 sec is typical).

PCP could help with that, 
http://tools.ietf.org/html/draft-ietf-pcp-base-13#section-7.3

-d