Re: [MMUSIC] STUN Transactions, still needed in ICE?

Emil Ivov <emcho@jitsi.org> Fri, 14 November 2014 05:51 UTC

Return-Path: <emcho@sip-communicator.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592591A6FDA for <mmusic@ietfa.amsl.com>; Thu, 13 Nov 2014 21:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8RFCsy8rE3Y for <mmusic@ietfa.amsl.com>; Thu, 13 Nov 2014 21:51:30 -0800 (PST)
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EA431A6FFA for <mmusic@ietf.org>; Thu, 13 Nov 2014 21:51:29 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id n3so1618570wiv.6 for <mmusic@ietf.org>; Thu, 13 Nov 2014 21:51:28 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=kQD4+WCgw+vT9sYTtK29sdrj6R/qf9EK4xwY8hTxK9E=; b=Z41jC/nGnhlnmcdDRpygAq6BcQU0JSfOeYmcknKnENctYJ8jnGLho3gI3YxEy4AP8i LvVI3Z0D9cbYBl5hS4CUc0zru/LXjn3QccmtnJPGQWx1RpfgFhBxKeCw5gj2SkC+U0dE Ja8cqM13lp0vD8TtdGQm1tRRz5u6oFol6QndHRVDjgxYtrOoLUsZ3tS0l4fbmoEESQz/ cLhAsOCtZYXNJi0Mz05nql1Mo9KL8dUK+z1TLipDAZbvmjezbOsm2GaQm1q6mEPej6m4 WFIho6X3HBdqGUXBwmt5UHyvRONAQOMBNIuIEAwjGKCJjp0RhOhvURE7vNmr8cnsZi3X uSOw==
X-Gm-Message-State: ALoCoQnLJn8j9ybS/AMxefH5b4hPiFhEO67p90wUYuwUMpkFD0Hkn1Ol3TVYCTgqzz0LqZzifZYe
X-Received: by 10.194.89.129 with SMTP id bo1mr10568368wjb.29.1415944288463; Thu, 13 Nov 2014 21:51:28 -0800 (PST)
Received: from [192.168.1.21] (9.6.69.91.rev.sfr.net. [91.69.6.9]) by mx.google.com with ESMTPSA id mu4sm2017755wib.2.2014.11.13.21.51.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Nov 2014 21:51:26 -0800 (PST)
Message-ID: <5465985D.2090806@jitsi.org>
Date: Fri, 14 Nov 2014 06:51:25 +0100
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>, mmusic <mmusic@ietf.org>
References: <2E9E03AE-DEF0-4C17-AB8A-BB59A87D9126@cisco.com> <5465956A.8090001@jitsi.org>
In-Reply-To: <5465956A.8090001@jitsi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/1JqsIJHQNIQrjvpvQea3hP_KbkI
Subject: Re: [MMUSIC] STUN Transactions, still needed in ICE?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 14 Nov 2014 05:51:34 -0000


On 14.11.14, 6:38, Emil Ivov wrote:
> On 13.11.14, 23:34, Pal Martinsen (palmarti) wrote:
>> Hi,
>>
>> During the TRAM meeting it was briefly discussed if we could changing
>> the STUN transaction ID when retransmitting a STUN request. Main
>> reason is to get more accurate/easier RTT measurements.
>>
>> Can we remove the STUN transaction concept from ICEbis without
>> breaking anything? Would there be simplification there as well as we
>> no longer would need two timers (One transaction timer and one
>> retransmit timer).
>>
>> From a code (At least mine..) perspective it would simplify the STUN
>> part (client/server) and put some more logic into the ICE part.
>
> I guess that for anyone who did implement transactions as per the spec,
> this would be a considerable effort. For us it certainly would be. Much
> more so than the perceived gain of improving RTT measurements.
>
> Wouldn't it be easier to just repurose three or four bits from the
> transaction ID and use them as a counter? This way the receiving side
> can also learn about loss and use it as a factor in constructing pair
> preferences.

And obviously there's also the option of just doing that in an extra 
attribute.

And just to be clear, I do think improving the RTT measurement would be 
a good thing. I just don't believe that repurposing the entire 
transaction ID as a counter is the best way to do it.

Emil


-- 
https://jitsi.org