Re: [MMUSIC] UPDATE mechanism for Trickle ICE - Comment on draft-ivov-mmusic-trickle-ice-sip-01

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 24 October 2013 13:01 UTC

Return-Path: <christer.holmberg@ericsson.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 E171211E8183 for <mmusic@ietfa.amsl.com>; Thu, 24 Oct 2013 06:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.795
X-Spam-Level:
X-Spam-Status: No, score=-3.795 tagged_above=-999 required=5 tests=[AWL=-1.196, 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 XTESXS0d4Fet for <mmusic@ietfa.amsl.com>; Thu, 24 Oct 2013 06:01:35 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 966E711E8153 for <mmusic@ietf.org>; Thu, 24 Oct 2013 06:01:34 -0700 (PDT)
X-AuditID: c1b4fb38-b7f178e00000233b-25-52691a2df688
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 0A.F8.09019.D2A19625; Thu, 24 Oct 2013 15:01:33 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0328.009; Thu, 24 Oct 2013 15:01:33 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Emil Ivov <emcho@jitsi.org>
Thread-Topic: UPDATE mechanism for Trickle ICE - Comment on draft-ivov-mmusic-trickle-ice-sip-01
Thread-Index: Ac7Oi3Z+e3UP57hvROCS8x6y31/feAAJw8IAACFHcIAAAcFGAAAEeh/hAAAm54r//+FhgIAAIpUB///8bUCAAAAHAP/+8S7AgAIsaoD//9DwgAAJK5MA//6RbBA=
Date: Thu, 24 Oct 2013 13:01:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4F0FED@ESESSMB209.ericsson.se>
References: <00a401cece8b$7b00f780$7102e680$@co.in> <CAPvvaaK3YOOB-Ta8+eoRcfQ8NrNRDdDf5a3VvOaN0vK=0unf7A@mail.gmail.com> <00ce01cecf48$6c0b5500$4421ff00$@co.in>, <5266BB46.4070305@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C4EBB51@ESESSMB209.ericsson.se>, <5266C0A7.5040305@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C4EBBEA@ESESSMB209.ericsson.se> <5266DAB0.7020001@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C4EC9F2@ESESSMB209.ericsson.se> <5267CA43.8020304@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C4EDE3A@ESESSMB209.ericsson.se> <5267E052.6020401@jitsi.org>
In-Reply-To: <5267E052.6020401@jitsi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+Jvja6uVGaQwZz54hZrdk5gsWi542Ux dfljFovJn/pYHVg8liz5yeTx/02gx4f5X9g9Ws71sgewRHHZpKTmZJalFunbJXBl7Djbzlpw RqBi3ZLlzA2MS3m7GDk5JARMJJb1XWaBsMUkLtxbz9bFyMUhJHCUUeLH7afMEM4SRol3xy4C ZTg42AQsJLr/aYM0iAjIS3S3LWICqWEW6GGUWPyjgRkkISyQKPHk519WiKIkifeLv7ODFIkI dDFK7Fl4lh0kwSKgKvFyzTdmkKG8Ar4SnbM0IZadZpFontsCVsMpoClx4OxcMJsR6Lzvp9Yw gdjMAuISt57MZ4I4W0BiyZ7zzBC2qMTLx/9YIWxFiavTl0PV60gs2P2JDcLWlli28DVYPa+A oMTJmU9YJjCKzUIydhaSlllIWmYhaVnAyLKKkaM4tTgpN93IYBMjMJoObvltsYPx8l+bQ4zS HCxK4rwf3zoHCQmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamDsV/WZWZ6joHuyRVXcY/uyP6yx qn+PPbtlH/j59MTrrIYlhVIuEq5Rd9h7ph/P2Gc3Y92s7w83lLvfsAplXLhqu9MugU/+/+fl 9koY/rG3PlN+6yfz3Kj3t/0+9Wq5KH7+GH6a5/zEkEN59ko3Nz56vi1X/mhL1uXLcw9VKjyL y+IQa2y8MWWPEktxRqKhFnNRcSIAqKKK1XQCAAA=
Cc: 'mmusic' <mmusic@ietf.org>
Subject: Re: [MMUSIC] UPDATE mechanism for Trickle ICE - Comment on draft-ivov-mmusic-trickle-ice-sip-01
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: Thu, 24 Oct 2013 13:01:42 -0000

Hi,

>>>> First, I completely messed up with the candidate types. Sorry for 
>>>> the confusion :)
>>>>
>>>> Anyway, it doesn't really matter what type of candidates are 
>>>> trickled
>>>> - it's about whether trickled candidates can be affected by 
>>>> Offers/Answers.
>>>
>>> And by affected you really mean invalidated. OK, I think I understand now.
>>>
>>> I don't think there's anything in 5245 that defines semantics which would invalidate existing candidates.
>>
>> Generally, in SDP Offer/Answer, when an SDP attribute is not present, it means that it's invalidated, or the default value (if such has been specified) is assumed.
>
> What I meant was that 5245 explicitly states that all previously signalled candidates MUST be signalled in updated Offers, so candidate removal in the middle of ICE processing is not something that is defined for ICE.
>
> Also, non-signalled candidates, like peer reflexive, are not required to be signalled in update Offers, so their absence in an offer cannot in any way be construed as a request for their removal.

So, IF we can define the same for trickled candidates, then there might not be an issue.

We have to remember, though, that a trickled candidate is not a new candidate "type". The candidate types you trickle are the same types you send in Offer/Answer - tickle is simply an alternative candidate transport mechanism.

>> But, that really depends on whether the candidates are considered part 
>> of the SDP state or not. IF so, trickled candidates would update that 
>> state, in the same way SDP Offers/Answers do.
>
> Right, and I've already mentioned that I don't see any reason to consider them as part of the SDP state, just as you wouldn't consider peer-reflexive candidates to be part of it.

If a trickled candidate is eventually selected, doesn't a "clean up" SDP Offer have to be sent (as for any other non-default candidate), where the c- line is aligned with the candidate? In that case the candidate becomes part of the SDP state :)

Regards,

Christer