IETF Logo Mail Archive

[Ice] ICE Generation clarification questions

Thomas Stach <thomass.stach@gmail.com> Mon, 27 February 2017 09:13 UTC

Return-Path: <thomass.stach@gmail.com>
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 92D5F128E19 for <ice@ietfa.amsl.com>; Mon, 27 Feb 2017 01:13:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.com
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 qY0PD99gzLgZ for <ice@ietfa.amsl.com>; Mon, 27 Feb 2017 01:13:12 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B634128824 for <ice@ietf.org>; Mon, 27 Feb 2017 01:13:12 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id v186so56191701wmd.0 for <ice@ietf.org>; Mon, 27 Feb 2017 01:13:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=keCQZLomd7uDVIzUBIUcVZY+w87qQhO5jFlifYY6s0g=; b=tENuO6s3m6GnZfduc4A2TJXKlP+HiainoBVOlWVDlanc5Rd18sSZcQpmJdWKzZUSQM a5GwiKNy5vTxOBPQGk0fv9ZJAoQDXiAxW/p2KdLOSVCzh7jVF7v1+xPZ2YNVgSawHX5X pbxT+9c5nCswRdf8oFSVj4NgTgD68LediZYbmlaBKNFQcqTcQiblikeVmKA/Is6W+lfJ 95P9a66WYNH48/cvV2Ij/vfbR8KuAHvAp+Z+uvAoxSXd867mQz8jeM5ZHioUs9LNmCkB Jgc5H5J+E4OIZR8QZ7xnIWFPd7EekfzP/6XvLT8LyQnp14Q6yWcDcje6uj0us8n5zUR+ lfzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=keCQZLomd7uDVIzUBIUcVZY+w87qQhO5jFlifYY6s0g=; b=MhnglrUa9YBEsJA4YLh8fgMOoaIqkZDUsDJTqAsM74oA5dlnoFAkI5akdkDmTIu6kw x7IAC/PBtCq5fhHw2B2KiGYWJlVbf3ANrMb2Bui/WdQzEFzxlVq/tkZ7EmJyEL7AgPLQ yUwfqIxOhikaEuVTs0VQl+W5T9RNGVt4YaXUnejz89StRzUHWsysTp1d/rZ+2Y7szwl5 ZUKHpli9UuJAOH8zW0f5/9gUFMefqnNNgSA3i1YUUVCyPMy7WvirVzUPk4y7DK2Tkw1F Q0BpOCorbToDQBbHQ6QhThn3mgRY07FF7HjJwteOBAaxwoYHC06AuhlwJvm2xeQCIlYZ QLFw==
X-Gm-Message-State: AMke39lc4tzHX2Nbtvh5OSsmW4mLKcA1iE21WGcJ6UrxtJyyon0mToXb3o8Uu9gJ0Iw4QA==
X-Received: by 10.28.63.15 with SMTP id m15mr13146758wma.119.1488186790804; Mon, 27 Feb 2017 01:13:10 -0800 (PST)
Received: from [192.168.2.114] (dsl-linz7-19-68.utaonline.at. [81.189.19.68]) by smtp.googlemail.com with ESMTPSA id i189sm13465684wmg.7.2017.02.27.01.13.09 for <ice@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Feb 2017 01:13:10 -0800 (PST)
To: ice@ietf.org
References: <148779754359.31167.11057689797490201951.idtracker@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <ca682f16-d926-d11e-ae03-6a84dfa84b68@gmail.com>
Date: Mon, 27 Feb 2017 10:13:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148779754359.31167.11057689797490201951.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/uuXMunNYoxEZzSzXf0WvOTbmwGg>
Subject: [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 09:13:14 -0000

Hi,

I'm a bit confused about the definition of an ICE Generation and how it 
is used in Section 14

    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",
"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,
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.

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.

Could you please clarify?

Regards
Thomas

On 2017-02-22 22:05, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Interactive Connectivity Establishment of the IETF.
>
>          Title           : Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol
>          Authors         : Emil Ivov
>                            Eric Rescorla
>                            Justin Uberti
>                            Peter Saint-Andre
> 	Filename        : draft-ietf-ice-trickle-06.txt
> 	Pages           : 28
> 	Date            : 2017-02-22
>
> Abstract:
>     This document describes "Trickle ICE", an extension to the
>     Interactive Connectivity Establishment (ICE) protocol that enables
>     ICE agents to send and receive candidates incrementally rather than
>     exchanging complete lists.  With such incremental provisioning, ICE
>     agents can begin connectivity checks while they are still gathering
>     candidates and considerably shorten the time necessary for ICE
>     processing to complete.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ice-trickle/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-ice-trickle-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ice-trickle-06
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Ice mailing list
> Ice@ietf.org
> https://www.ietf.org/mailman/listinfo/ice
>

v2.23.0 | Report a Bug | By Email