Re: [MMUSIC] Comments on ICE-TCP specification RFC 6544

Nigel Pattinson <> Thu, 27 June 2013 03:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DFF7921F8F29 for <>; Wed, 26 Jun 2013 20:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id h603DqbDGT1N for <>; Wed, 26 Jun 2013 20:41:11 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3A4DE21F84A8 for <>; Wed, 26 Jun 2013 20:41:10 -0700 (PDT)
Received: from ([]) by with esmtp (Exim 4.72) (envelope-from <>) id 1Us34w-0004uY-Lo for; Wed, 26 Jun 2013 20:41:08 -0700
Date: Wed, 26 Jun 2013 20:41:02 -0700
From: Nigel Pattinson <>
Message-ID: <>
In-Reply-To: <>
References: <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [MMUSIC] Comments on ICE-TCP specification RFC 6544
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 27 Jun 2013 03:41:16 -0000

jakubadamek wrote
> could you please tell me roughly how much time it took to implement the
> RFC? 

That's difficult to say - we started from scratch, so had to implement STUN,
TURN (client and server), as well as Jingle. Probably the ICE portion was 2
- 3 man months.

jakubadamek wrote
> And how well does it work for you?

We haven't shipped yet, but it seems like it will work fine. However in
practice we suspect the outcome will be that host candidates will be used
within a LAN, and a relayed connection in almost all other cases. We have
all the usual ICE code for server and peer reflexive candidates, and for
simultaneous open TCP candidates, but we expect that the cases where they
can be successfully used to establish a connection will be rare.

Also as my previous post suggested, your TCP code may need to be more
different from UDP than the specification might lead you to believe.

In the end, if a relayed connection is an acceptable outcome and
peer-to-peer is a bonus, then ICE-TCP seems worth investigating. But if
peer-to-peer is the priority UDP might be the way to go.


View this message in context:
Sent from the IETF - mmusic mailing list archive at