Re: [MMUSIC] UPDATE mechanism for Trickle ICE - Comment on draft-ivov-mmusic-trickle-ice-sip-01
Emil Ivov <emcho@jitsi.org> Thu, 24 October 2013 16:31 UTC
Return-Path: <emcho@sip-communicator.org>
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 7ED3511E81B2 for <mmusic@ietfa.amsl.com>; Thu, 24 Oct 2013 09:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.735
X-Spam-Level:
X-Spam-Status: No, score=-2.735 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 DCObOiPmZIGo for <mmusic@ietfa.amsl.com>; Thu, 24 Oct 2013 09:31:50 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id 9564B11E835D for <mmusic@ietf.org>; Thu, 24 Oct 2013 09:31:43 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id fa1so884437pad.13 for <mmusic@ietf.org>; Thu, 24 Oct 2013 09:31:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=kcTPnRrxelcBtlW9v/ZYaOZYXSHmrecW0eOAw28+Pmw=; b=mfn2EoryIfwja3ToVX/haQj/U0FcZx5e1S2XPUabY/k8CvIohiKkNkjgIBzXHf9dqt uxIiiSvTYXZdScFSYZ9ukNUNelTtR530haVKsqO4o7owVAIiy0hamM2/Ut+Nu++UivkL s1Zhl/RDD42ece3yb/2C6sDvhxnkXtgq3ICLDToFcTNqvyDkXs7mvZLkWsuRYUUdierS +IKE7s2nJXw4l5aNf0gP9ysz7RTSBdpnBScC4nSNbXXFc5CKU5dNCQn/SWSeZEfHWjuA cjeUWKVDGvphYizB5dIFKUeqakalvXrmMR0VKZm3TskfSxl7U7+oDMNFoGt76ms8A9QC fxSg==
X-Gm-Message-State: ALoCoQlOMEdhnDgrEL9Ugivxxcd1zRbUJVSJrWcNLe/vXK5uUB2f5Nc2f4CbKAETbT6P/SHgBc21
X-Received: by 10.68.253.67 with SMTP id zy3mr3668299pbc.137.1382632303096; Thu, 24 Oct 2013 09:31:43 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [2607:f8b0:400e:c01::235]) by mx.google.com with ESMTPSA id v4sm3646535pbq.31.2013.10.24.09.31.42 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 09:31:42 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up7so2317975pbc.26 for <mmusic@ietf.org>; Thu, 24 Oct 2013 09:31:42 -0700 (PDT)
X-Received: by 10.66.216.129 with SMTP id oq1mr4149375pac.75.1382632302619; Thu, 24 Oct 2013 09:31:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.191.163 with HTTP; Thu, 24 Oct 2013 09:31:21 -0700 (PDT)
In-Reply-To: <369B690E-2456-48AD-923E-93B88A620817@vidyo.com>
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> <7594FB04B1934943A5C02806D1A2204B1C4F0FED@ESESSMB209.ericsson.se> <52692E69.8020109@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C4F223D@ESESSMB209.ericsson.se> <369B690E-2456-48AD-923E-93B88A620817@vidyo.com>
From: Emil Ivov <emcho@jitsi.org>
Date: Thu, 24 Oct 2013 18:31:21 +0200
Message-ID: <CAPvvaaKrFOo-XsPNriNWg9-AWy3sL0gm4p-jY5LM1s52zk_yhA@mail.gmail.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
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 16:31:58 -0000
On Thu, Oct 24, 2013 at 5:36 PM, Jonathan Lennox <jonathan@vidyo.com> wrote: > > On Oct 24, 2013, at 10:34 AM, Christer Holmberg <christer.holmberg@ericsson.com> > wrote: > >> Hi, >> >>>> 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. >>> >>> Yes, that's right. I am not sure why you are saying it though. >> >> Because when you say: >> >> "we treat trickle candidates in the same way as peer-reflexive candidates" >> >> ...it sounds like a trickle candidate is a new type of candidate (similar to peer-reflexive candidate), which is not true. >> >> >> You should say: >> >> "We treat candidates that were provided using the trickle ICE mechanism in the same way as peer-reflexive candidates" > > There's a problem with this. > > RFC 5245 says: > > However, the peer reflexive candidate is not paired with other remote > candidates. This is not necessary; a valid pair will be generated > from it momentarily based on the procedures in Section 7.1.3.2.2. If > an agent wishes to pair the peer reflexive candidate with other > remote candidates besides the one in the valid pair that will be > generated, the agent MAY generate an updated offer which includes the > peer reflexive candidate. > > In other words, peer-reflexive candidates aren't automatically paired with all remote candidates; they're only paired with the remote candidate you were checking when you discovered them, unless you send them in an updated offer. > > Candidates provided over Trickle don't have a remote candidate to be automatically paired with, so "treating them like peer-reflexive candidates" doesn't make much sense. No it doesn't. The idea is that "trickled candidates" being exchanged, checked and selected entirely outside the context of Offer/Answer is not a problem because we already have this with "peer-reflexive candidates". Trickled candidates obviously do need specific handling within the *ice agents*, which is one of the reasons for the existence of the trickle ICE drafts. Cheers, Emil -- https://jitsi.org
- [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