Re: [MMUSIC] Trickle ICE for SIP Questions

"Stach, Thomas" <thomas.stach@siemens-enterprise.com> Tue, 09 July 2013 21:21 UTC

Return-Path: <thomas.stach@siemens-enterprise.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17E9111E8172 for <mmusic@ietfa.amsl.com>; Tue, 9 Jul 2013 14:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 6qRGhHHL04zy for <mmusic@ietfa.amsl.com>; Tue, 9 Jul 2013 14:21:28 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 1B9BE21F9D4E for <mmusic@ietf.org>; Tue, 9 Jul 2013 14:21:12 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 4285623F0602; Tue, 9 Jul 2013 23:21:07 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.137]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Tue, 9 Jul 2013 23:21:07 +0200
From: "Stach, Thomas" <thomas.stach@siemens-enterprise.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] Trickle ICE for SIP Questions
Thread-Index: AQHOd/eUM0XqJDBgnkG3edAtUHILLJlUd8BAgAGKMgCAACstAIAEXPYAgABOUoCAAgJgEA==
Date: Tue, 09 Jul 2013 21:21:05 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE12114A31C6@MCHP04MSX.global-ad.net>
References: <51D43186.2010907@jitsi.org> <F81CEE99482EFE438DAE2A652361EE12114A0200@MCHP04MSX.global-ad.net> <51D6D456.7090900@jitsi.org> <51D6F88E.5000209@alum.mit.edu> <F81CEE99482EFE438DAE2A652361EE12114A1153@MCHP04MSX.global-ad.net> <51DAE33B.3070507@alum.mit.edu>
In-Reply-To: <51DAE33B.3070507@alum.mit.edu>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Trickle ICE for SIP Questions
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 21:21:33 -0000

Paul,

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> Sent: Monday, 08 July, 2013 18:05
> To: Stach, Thomas
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Trickle ICE for SIP Questions
> 
> Just responding to things that haven't already been covered.
> 
> On 7/8/13 5:44 AM, Stach, Thomas wrote:
> 
> >> Yes, why is it such an issue to require PRACK?
> > [TS] I see potential for easier GW/SBC interworking with vanilla-ICE
> UAs, that did not implement PRACK
> 
> I don't get it.
> 
> If you are talking about SBCs that terminate/relay media, then the leg
> doing trickle-ICE is separate from the leg doing vanilla-ICE. So what
> is
> the issue?

> 
> And if you have a signaling-only SBC, and one leg supports trickle-ICE
> while the other side supports only vanilla-ICE, then just use
> vanilla-ICE e2e. You won't gain anything by an intermediary trying to
> map trickle-ICE to vanilla-ICE.
[TS] 
If the trickle-ICE side uses PRACK and the vanilla ICE side does not, the interworking SBC does not only have to collect the trickled candidates and send it on as a bunch once trickling finished. It also has to interwork PRACK.
As you know the PRACK request can contain a new SDP offer or you could also use UPDATE for another SDP O/A before the 200 OK to the INVITE request. This is rather nasty to interwork if not impossible.

> 
> >> It is a good thing to implement for many reasons.
> > [TS] There are also good reasons against PRACK. e.g. the much more
> complicated state machine.
> 
> Yes, but once you have done it then it is there to use for all sorts of
> things. The alternative seems to be to instead introduce a lot of new
> complexity that is *only* applicable to trickle-ICE.
> 
> 	Thanks,
> 	Paul