Re: [MMUSIC] UPDATE mechanism for Trickle ICE - Comment on draft-ivov-mmusic-trickle-ice-sip-01
Christer Holmberg <christer.holmberg@ericsson.com> Wed, 23 October 2013 14:06 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 619EF21E808F for <mmusic@ietfa.amsl.com>; Wed, 23 Oct 2013 07:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.806
X-Spam-Level:
X-Spam-Status: No, score=-3.806 tagged_above=-999 required=5 tests=[AWL=-1.207, 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 hK5gnEkLvs-M for <mmusic@ietfa.amsl.com>; Wed, 23 Oct 2013 07:06:17 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9828211E83F4 for <mmusic@ietf.org>; Wed, 23 Oct 2013 07:06:11 -0700 (PDT)
X-AuditID: c1b4fb38-b7f178e00000233b-4f-5267d7cfec1a
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 56.AC.09019.FC7D7625; Wed, 23 Oct 2013 16:06:07 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0328.009; Wed, 23 Oct 2013 16:06:07 +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//9DwgA==
Date: Wed, 23 Oct 2013 14:06:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4EDE3A@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>
In-Reply-To: <5267CA43.8020304@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+NgFrrPLMWRmVeSWpSXmKPExsUyM+Jvje756+lBBjM2iFus2TmBxaLljpfF 1OWPWSwmf+pjdWDxWLLkJ5PH/zeBHh/mf2H3aDnXyx7AEsVlk5Kak1mWWqRvl8CV8WyRe0Gj YMXEDVeYGhiP83YxcnJICJhIbNr+nhnCFpO4cG89WxcjF4eQwFFGiWmPfzNCOEsYJXa/aACq 4uBgE7CQ6P6nDdIgIiAv0d22iAmkhlmgh1Fi8Y8GsEnCAokST37+ZYUoSpJ4v/g7O4RdJ/Fp 21+wGhYBVYneyXuZQGxeAV+Jcye62EBsIYEXzBKfd+mD2JwCmhLbFzeA9TICXff91BqwemYB cYlbT+YzQVwtILFkz3moD0QlXj7+xwphK0pcnb4cql5HYsHuT2wQtrbEsoWvmSH2CkqcnPmE ZQKj2CwkY2chaZmFpGUWkpYFjCyrGDmKU4uTctONDDYxAiPp4JbfFjsYL/+1OcQozcGiJM77 8a1zkJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQZGg09PduetDvqxofgRY+UcRyGZc6+l2b9y KEgcMn9Qt1n2h1un3x2bCe/uKsVkTz53vPK5y5Jwt1tqi87lTHblFe7c9+BOzNZg+8Xln1/u 9+conPvkmcWjB+yxWbOOile+8aqL9HthtGKywV6paP9nUVeX7/0TnPG0xSHSt4v5+0xlK6nL UxcdVGIpzkg01GIuKk4EALk6i45yAgAA
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: Wed, 23 Oct 2013 14:06:23 -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. You could of course argue that, if a candidate has never been carried in an SDP Offer/Answer to begin with, SDP Offer/Answers should have no impact on it. 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. My point is that these things need to be clearly clarified. >>>> So, that would mean that if an Offer is received without the peer >>>> refexive candidates, the answerer would remove them. >>> >>> You lost me. How would an answerer remove candidates from an offer if >>> they weren't there in the first place? Did you mean to say something >>> else? >> >> I referred to the example below, where an Offer does not contain a >> candidate that was previously trickled, and whether the answerer will >> then assume that the candidate is no longer valid. > > Right. I don't think there's such a risk. 5245 explicitly forbids update Offers and Answers to remove candidates that have been announced previously and it allows (as in MAY, not SHOULD) that new candidates be added. > > The former should address your concern and I believe we could simply remove the latter as it is of little use, if any. Well, then there is of course a risk that the receiver of the Answer will trigger an error, as the trickled candidate is not included in the Answer (as the Answer was sent before the candidate was trickled :) Regards, Christer
- [MMUSIC] UPDATE mechanism for Trickle ICE - Comme… Parthasarathi R
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Parthasarathi R
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Jonathan Lennox
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Paul Kyzivat
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Parthasarathi R