Re: [Ice] Trickle ICE review

Peter Saint-Andre <stpeter@stpeter.im> Tue, 28 March 2017 17:05 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 3A262129454 for <ice@ietfa.amsl.com>; Tue, 28 Mar 2017 10:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=Z5eNsURs; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Yo6oyuAb
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 eeIxL-3AXqa5 for <ice@ietfa.amsl.com>; Tue, 28 Mar 2017 10:05:25 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59146128C84 for <ice@ietf.org>; Tue, 28 Mar 2017 10:05:25 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id C448E20C31; Tue, 28 Mar 2017 13:05:24 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 28 Mar 2017 13:05:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; 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=fm1; bh=3DRqqXl07QiCrqW/fo K8fQYCdH1z/H8EbeOLVULQWbY=; b=Z5eNsURsoPrpAtzHQVs1FVcyWbH69jDHLr 1DRLqYX4jk/Rpplp8CKMoP5Rk0qRSEWYAwKUzMjsDka5cKSWvTnX6k3bAuGu7MLC eTj9rz8tGIsiaIVHTZXwsWo2ULcgNlneuvKaxY3oec4kczOxNQtHpXR7XO8+VVs1 fxbQsiZJVx67DDe8I6VDK3ovCrTdssFxcaQQmEcJHpXFL875VZtg0NcGweIjwMWr J/BVAK409pmYkIhbt8AxnLSf8TZ69+QZHvajA+2T66D4OQmAOYr7KkOqEx7tJUZ5 LOGXWgt98EaHUjzzlIbGqLgArDPveIv5t/jxmHhuUA6/30pzMEKA==
DKIM-Signature: v=1; a=rsa-sha256; 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= fm1; bh=3DRqqXl07QiCrqW/foK8fQYCdH1z/H8EbeOLVULQWbY=; b=Yo6oyuAb s/hRss57aJI0nwuw9wiLfAwIoOInaLPdCc9Uvp1iyTI9YuvbjXtv7FD/gfnO/q0J gY/mUI7OSuXJ5HUdzWOiHH3RqDYMpah3+vwW3BbYgjYgdYtSVGs8e0TQVnb4vVqF Ah26qG3x1F9CylCdstzRCx/cqmiDVkHBb7tAX34jBdZSuv1GgNyqPVtzFCbOKZ/X xv24f4S/Rh9ppWpobNB7EoWp/WX/I/mFLw5x3WLhl7eXFgc2CiiF4oiR6UMRCVMo b4dBEeuKJKb0dDRcceIX6L0AxHgwlrxER6c0mWEW4XMTg45g6a63pfQf+BiGDvO6 5zCQtaftgXE7oA==
X-ME-Sender: <xms:1JfaWEEsPLJn3kbFGdMW_9Cr-QRgPc-pasiKe9nJOLGZdpaO_TBIgg>
X-Sasl-enc: 94SfEs/LuOHTAd4sE6EklKzMGtDp3cYUoGrUmLIG7XzG 1490720724
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 443017E5D9; Tue, 28 Mar 2017 13:05:24 -0400 (EDT)
To: Ari Keränen <ari.keranen@ericsson.com>, Peter Thatcher <pthatcher@google.com>
References: <CAJrXDUHzNT3v5oMPBQu5_OsXwonY7cogDQgTt5QPxN0=6DWQkQ@mail.gmail.com> <7ebb3254-a882-6e05-3159-0ec56614831b@stpeter.im> <CAJrXDUEi0n7P5mDuuLGj285AmQqr9HDFUPGLtLnU+BuJpws6Tw@mail.gmail.com> <7e9e8188-2add-0497-e94f-14ee41afe02d@stpeter.im> <BFB0CDEF-4572-41D5-A5D2-A5D210A1E175@ericsson.com>
Cc: "ice@ietf.org" <ice@ietf.org>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <0c989dea-9318-b87c-3a90-0f6083efa16a@stpeter.im>
Date: Tue, 28 Mar 2017 11:05:23 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <BFB0CDEF-4572-41D5-A5D2-A5D210A1E175@ericsson.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/4VZ2v7LnfSdw-Fv8nzr4G_zKf9w>
Subject: Re: [Ice] Trickle ICE review
X-BeenThere: ice@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 28 Mar 2017 17:05:27 -0000

On 3/28/17 10:43 AM, Ari Keränen wrote:
> 
>> On 28 Mar 2017, at 11:27, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>>
>>>> - The name "ICE negotiation session" with definition of "A virtual
>>>> session ..." is confusing.   I understand that we need a word for
>>>> "period between restarts" and "period across restarts".  But what does
>>>> "virtual" mean in this context?  And what does "negotiation" mean in
>>>> "ICE negotiation session"?  Here's a possible suggestion: call it
>>>> "single-exchange session".   A single-exchange session is the period
>>>> from a single exchange of ICE description until the next exchange.  A
>>>> "normal" ICE session is basically a multi-exchange session.
>>>
>>>    This might be clearer:
>>>
>>>       ICE Session:  All of the ICE-related interactions between ICE agents
>>>          up until an ICE restart (if any).
>>>
>>>    However, that definition probably belongs in 5245bis. The term as used
>>>    in the Trickle specification is not limited to interactions between
>>>    Trickle ICE agents.
>>>
>>>
>>> I like that idea of using "ICE session" to mean the thing between
>>> restarts as long as it's compatible with 5245 and 5245bis and it doesn't
>>> cause confusion such that people think an "ICE session" is the time
>>> period across all ICE restarts.
>>>
>>> I originally thought it should go in 5245bis also, but Ari thought it
>>> didn't make sense there since it would never use the term after defining
>>> it.  
>>
>> It's already used in 5245bis, isn't it? But we can continue to define it
>> in Trickle.
> 
> It's used but not defined actually. We'll add this to the terminology of 5245bis.

Right, I think that's the best place for it. Thanks!

Peter