Re: [BEHAVE] BoF request: STUN Control Usage
"Adam Fisk" <adamfisk@gmail.com> Fri, 08 June 2007 21:03 UTC
Return-path: <behave-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwlcl-00022w-GB; Fri, 08 Jun 2007 17:03:59 -0400
Received: from behave by megatron.ietf.org with local (Exim 4.43) id 1Hwlcj-0001z9-SP for behave-confirm+ok@megatron.ietf.org; Fri, 08 Jun 2007 17:03:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwlcj-0001z1-Is for behave@ietf.org; Fri, 08 Jun 2007 17:03:57 -0400
Received: from wx-out-0506.google.com ([66.249.82.226]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwlci-0006Dr-93 for behave@ietf.org; Fri, 08 Jun 2007 17:03:57 -0400
Received: by wx-out-0506.google.com with SMTP id t5so785614wxc for <behave@ietf.org>; Fri, 08 Jun 2007 14:03:56 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=QeFlmcwbgEj86SWwwLNpWKFAdT6UGBmFOHekjPrXAIBQOMMjVOBhkFj3AOLI+ERSKQG4qyTNoWduoz7MvlGPsXaqr5s2QtKKY8RU+8gZZmOWIMp2htAi5jxFBcLkEnWWS/ffw/ppPRfXTpYrVFBeI56sKryjiL/V6dZYChTa27Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ZQTmmd7xZWDpxbeoS44WvIZzwUaEURypMZnBRCzpGZ+Bl5R7F7x3md38LNyQ3EjpJ64zNdHgkdNNUrbAwwovwUs2OQpBqoTHBpCb/O/bJlLRE/vGomDilSDCn6u7UlKvME6zaloHRcTwi2jEBao/5rUoKSpgzM50EmxTcz4XrxQ=
Received: by 10.90.90.16 with SMTP id n16mr3466752agb.1181336635097; Fri, 08 Jun 2007 14:03:55 -0700 (PDT)
Received: by 10.90.56.13 with HTTP; Fri, 8 Jun 2007 14:03:55 -0700 (PDT)
Message-ID: <f40963db0706081403k4bff37c1v2af9cbfe10fdbbb8@mail.gmail.com>
Date: Fri, 08 Jun 2007 17:03:55 -0400
From: Adam Fisk <adamfisk@gmail.com>
To: Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] BoF request: STUN Control Usage
In-Reply-To: <025901c7aa0e$4c428380$1ea36b80@amer.cisco.com>
MIME-Version: 1.0
References: <f40963db0706081257q2aad74b5te4e8ed40130ffaed@mail.gmail.com> <025901c7aa0e$4c428380$1ea36b80@amer.cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: behave@ietf.org, Erkki.Koivusalo@nokia.com
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1727544411=="
Errors-To: behave-bounces@ietf.org
On 6/8/07, Dan Wing <dwing@cisco.com> wrote: > > > Any idea how many of the deployed SIP servers use UDP? > > There is some information from SIPit 20, > https://www.sipit.net/SIPit20_Summary but of course that > lacks market share information. Interesting. So it looks like most implementations support both. I wonder how many of those actually use the UDP implementation over the TCP in terms of what clients actually connect with. I know I wouldn't, but I wonder. > Additionally, under high traffic rates from a single IP > address (such as a bunch of SIP clients behind a single NAPT), > draft-heffner-frag-harmful describes problems with reassembly > which I doubt are sufficiently appreciated by those running > SIP over UDP. I would think there would be many issues along these lines. It has to be one of the thorniest parts of any implementation in any case. > To summarize, I believe you're saying if UDP keepalives create > too much load on your server or network, just use TCP. Basically. Put a slightly different way, if no one's using UDP in practice anyway, then the TCP keep alive mechanism doesn't seem too onerous. There unfortunately seems to be little way to get a solid answer to that question, though, so I'm not sure where to go with it. Thanks. -Adam
_______________________________________________ Behave mailing list Behave@ietf.org https://www1.ietf.org/mailman/listinfo/behave
- [BEHAVE] BoF request: STUN Control Usage Dan Wing
- RE: [BEHAVE] BoF request: STUN Control Usage David Barrett
- RE: [BEHAVE] BoF request: STUN Control Usage Dan Wing
- RE: [BEHAVE] BoF request: STUN Control Usage David Barrett
- RE: [BEHAVE] BoF request: STUN Control Usage Dan Wing
- RE: [BEHAVE] BoF request: STUN Control Usage David Barrett
- RE: [BEHAVE] BoF request: STUN Control Usage Erkki.Koivusalo
- RE: [BEHAVE] BoF request: STUN Control Usage Christer Holmberg (JO/LMF)
- Re: [BEHAVE] BoF request: STUN Control Usage Pete Cordell
- Re: [BEHAVE] BoF request: STUN Control Usage Jonathan Rosenberg
- RE: [BEHAVE] BoF request: STUN Control Usage David Barrett
- Re: [BEHAVE] BoF request: STUN Control Usage Adam Fisk
- RE: [BEHAVE] BoF request: STUN Control Usage Dan Wing
- Re: [BEHAVE] BoF request: STUN Control Usage Adam Fisk
- Re: [BEHAVE] BoF request: STUN Control Usage Rémi Denis-Courmont
- RE: [BEHAVE] BoF request: STUN Control Usage David Barrett
- Re: [BEHAVE] BoF request: STUN Control Usage Magnus Westerlund
- [BEHAVE] NAT control and STUN - some thoughts Markus.Isomaki
- RE: [BEHAVE] BoF request: STUN Control Usage Markus.Isomaki
- Re: [BEHAVE] NAT control and STUN - some thoughts Melinda Shore
- Re: [BEHAVE] BoF request: STUN Control Usage Iljitsch van Beijnum
- RE: [BEHAVE] BoF request: STUN Control Usage Dan Wing
- RE: [BEHAVE] NAT control and STUN - some thoughts Markus.Isomaki
- Re: [BEHAVE] BoF request: STUN Control Usage Magnus Westerlund
- announcing SAFE mailing list [was: RE: [BEHAVE] B… Dan Wing