Re: [Ice] ICE Generation clarification questions

Peter Saint-Andre <stpeter@stpeter.im> Mon, 27 February 2017 21:57 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: ice@ietfa.amsl.com
Delivered-To: ice@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D574129405 for <ice@ietfa.amsl.com>; Mon, 27 Feb 2017 13:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=stpeter.im header.b=MV85tMWQ; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=dPfdSW+p
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 WMIQWWUXNNpi for <ice@ietfa.amsl.com>; Mon, 27 Feb 2017 13:57:58 -0800 (PST)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DAC9129401 for <ice@ietf.org>; Mon, 27 Feb 2017 13:57:57 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.nyi.internal (Postfix) with ESMTP id 459B3125D; Mon, 27 Feb 2017 16:57:57 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Mon, 27 Feb 2017 16:57:57 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=stpeter.im; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=3L9/B21vlxdKp7y 9+9jwcau7DTc=; b=MV85tMWQ0yNaS59lZsCm9UDBhlh7PZZEcggipyojIGeflZj qpyjqKgWIfoOPeK43eQ8xO3avXI7S8Jwy4APLplsp+y3p/B7+VmsIyng/lWqgL/y fyHzCmlVuargVhQmDvKUYy8wuGDmbOX5xugDsax0gHYObSySu8/R5pRLdwAs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=3L9/B21vlxdKp7y9+9jwcau7DTc=; b=dPfdSW+p1gmqovQ1kkcv klxU+VPGyBG/2sKerCutNrV1H/KWlBXzBLMrFeMTzezpxBNzeSFf/e4k8LzIrDP+ +irEM1VR61AwX1qP3ErsSYltgOFzOnQfVf7zuFTHsBphyB310Esu6gESLWUIdaAO sC89YiwszoRiJkLmfWrGKpw=
X-ME-Sender: <xms:5KC0WIMzBTYbOXAAgqtp4pZFKefwzn335JrZMGCYP-H_KOY8sM5ZUQ>
X-Sasl-enc: 5JgM9B1ti8arZhkCUHeVWsAlY46ydbzpGp+6jgADQR00 1488232676
Received: from aither.local (c-98-245-40-52.hsd1.co.comcast.net [98.245.40.52]) by mail.messagingengine.com (Postfix) with ESMTPA id 753322428D; Mon, 27 Feb 2017 16:57:56 -0500 (EST)
To: Taylor Brandstetter <deadbeef@google.com>
References: <148779754359.31167.11057689797490201951.idtracker@ietfa.amsl.com> <ca682f16-d926-d11e-ae03-6a84dfa84b68@gmail.com> <a0ca345c-75dd-002d-edc3-e829b5a60869@stpeter.im> <CAK35n0abCrm2WDd8PfQmnDBNrwf4vdCTUL9+TXSZkobATGs-cw@mail.gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <73898e41-dd66-e0be-0415-e5753880f0d1@stpeter.im>
Date: Mon, 27 Feb 2017 14:57:55 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAK35n0abCrm2WDd8PfQmnDBNrwf4vdCTUL9+TXSZkobATGs-cw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/0Mwc2RKoBjlZVmtTmabsjQ-Y-l4>
Cc: Thomas Stach <thomass.stach@gmail.com>, ice@ietf.org
Subject: Re: [Ice] ICE Generation clarification questions
X-BeenThere: ice@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interactive Connectivity Establishment \(ICE\)" <ice.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ice>, <mailto:ice-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ice/>
List-Post: <mailto:ice@ietf.org>
List-Help: <mailto:ice-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ice>, <mailto:ice-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 21:57:59 -0000

Exactly. Would it help to describe it that way or at least note the
connection?

On 2/27/17 2:55 PM, Taylor Brandstetter wrote:
> Another way of looking at it is that a given generation is identified by
> a local/remote ufrag pair, which will change on ICE restart.
> 
> On Mon, Feb 27, 2017 at 1:53 PM, Peter Saint-Andre <stpeter@stpeter.im
> <mailto:stpeter@stpeter.im>> wrote:
> 
>     On 2/27/17 2:13 AM, Thomas Stach wrote:
>     > Hi,
>     >
>     > I'm a bit confused about the definition of an ICE Generation and how it
>     > is used in Section 14
> 
>     To be clear for folks on the list, this is in reference to the trickle
>     draft.
> 
>     >    Generation:  The complete set of candidates sent within an ICE
>     >       negotiation session.
>     >
>     >
>     >
>     > Section 14 and the definition of Half/Full Trickle then uses terms like
>     > "first generation"
>     > "complete generation",
> 
>     For half trickle purposes, I think it would be best to use the phrase
>     "full generation" or even "complete set of candidates". That is: under
>     half trickle, in the initial ICE description the initiator sends all the
>     candidates it might possibly send.
> 
>     > "the responder can respond with an incomplete generation of candidates",
>     >
>     > "full generation"
>     >
>     > This seems to imply that the generation is not necessarily the complete
>     > set of candidates,
> 
>     The generation is as defined above: the complete set of candidates sent
>     within an ICE negotiation session. It would be better here to use the
>     phrase "incomplete set of candidates".
> 
>     > but could grow during aICE Negotiation Session until end-of-candidates
>     > is signalled.
>     > So the generation rather seems to be the extensible set of currently
>     > known/exchanged candidates.
> 
>     No, the generation is everything sent before an ICE restart (if any). In
>     trickle the set can grow over time, whereas in regular ICE it can't.
> 
>     > It is also not clear to me if the candidates sent by the ICE initiator
>     > and the ICE responder
>     > belong to  different generations or if the generation is the union of
>     > both candidate sets.
> 
>     It is the union.
> 
>     Peter
> 
> 
>     _______________________________________________
>     Ice mailing list
>     Ice@ietf.org <mailto:Ice@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ice
>     <https://www.ietf.org/mailman/listinfo/ice>
> 
>