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

Randell Jesup <randell-ietf@jesup.org> Thu, 15 September 2011 19:10 UTC

Return-Path: <randell-ietf@jesup.org>
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 885CE21F8B50 for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 12:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 UWvWvjUglKEl for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 12:10:33 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 6643521F8B33 for <rtcweb@ietf.org>; Thu, 15 Sep 2011 12:10:31 -0700 (PDT)
Received: from [216.1.177.180] (helo=[172.16.169.201]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1R4HMV-00020l-M0 for rtcweb@ietf.org; Thu, 15 Sep 2011 14:12:40 -0500
Message-ID: <4E724E25.1000204@jesup.org>
Date: Thu, 15 Sep 2011 12:12:37 -0700
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: 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>
In-Reply-To: <CAD5OKxtt9phWr9Vrn5J1STxA9airR8g-tHMnddFP=QwrTHuPcA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
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: Thu, 15 Sep 2011 19:10:33 -0000

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).

-- 
Randell Jesup
randell-ietf@jesup.org