Re: [Ice] I submitted and plan to present draft-thatcher-ice-remove-candidate in Berlin

Bernard Aboba <bernard.aboba@gmail.com> Tue, 12 July 2016 21:20 UTC

Return-Path: <bernard.aboba@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 5C81C12D960 for <ice@ietfa.amsl.com>; Tue, 12 Jul 2016 14:20:48 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 2eNB3UYMQWBR for <ice@ietfa.amsl.com>; Tue, 12 Jul 2016 14:20:46 -0700 (PDT)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (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 5AC2B12D968 for <ice@ietf.org>; Tue, 12 Jul 2016 14:20:41 -0700 (PDT)
Received: by mail-vk0-x22b.google.com with SMTP id v6so40280053vkb.2 for <ice@ietf.org>; Tue, 12 Jul 2016 14:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hk5Vs5rcIv5sOVAq1YHD4xGyhCsBl0OAsOWlrDOwmSI=; b=uBUL5JuJ1kbBC4of3MmVCm1QHEZEc911pyUVIl+IKv2eSl/9zEVNcqBMf3FWzooD9L Xplt3981wmCt0LZngS6a3peDK7Og7fbiYeQ9rGIyAFSia4mxlsGlOw4Db736oQrcIm9V Z8MqanZg3D8Yw+bv8gl34xjhsWTHL0tybfrr2aWCwbcaZsV7HgIFh/WZNXfsWF00G/U6 8txme7GJarpdSAQNhYfqv8c6z48AH0BBmD6ctVuoOCwzM+4zosaf8m8rvAp8StQ+zqW6 kylbS+VfhT2DmDicYqaUYcSLUJsf3ZxV9qOvFHxeno/DSVyOGdm9veeR1iD4kyh/hVWP NMpg==
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; bh=hk5Vs5rcIv5sOVAq1YHD4xGyhCsBl0OAsOWlrDOwmSI=; b=gfyyjXWUqXrnxvh1NV8juyudK1AdPHt4azsl3jeGBLAwKNkCk8UhvWAMa+oZUizBHt ZL5L5mojWBGgZq84AisaKwQE2h9gJwuAizGX8GR4ex3lkQc6kCKYqj6CXkLzr/yxd4VF b89BUsIsv2avj5qykknHHwbTj+xyxd4MDUSitCPm5iF03Ie7vNz+uvXcQKVoaqaZVk2b I8UqUryIJ+plR8UXCNj3FrGeGhqG5pHy2HZe8vROE0zFJgMzs85+I36JXcuchGnN2tcA HZ9n4aocUzJJbw5ZhYbn3YPpGnGkDdZRystOgTv8TuhvV1jIZ45FlrSbe6buEMBHqPdV fHHQ==
X-Gm-Message-State: ALyK8tLvrsceerC4yseCUFKP8seF0ZcXPWr0Gef8duKIu2xgeQea3f0xJnkvhi+cfNVySvogx3r0iTRmzL4jAQ==
X-Received: by 10.159.40.74 with SMTP id c68mr2275366uac.9.1468358440396; Tue, 12 Jul 2016 14:20:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.41.198 with HTTP; Tue, 12 Jul 2016 14:20:20 -0700 (PDT)
In-Reply-To: <CAJrXDUHTSRzdauAZp0_rrBHavzxu9mYB4F1YTRU_yOw3oj47mA@mail.gmail.com>
References: <CAJrXDUEQoBmjhkwX5AF9Oxny=PwJ0Y1a7UmPNdVRsA8b6AEF7g@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B476A0A52@ESESSMB208.ericsson.se> <CAJrXDUHTSRzdauAZp0_rrBHavzxu9mYB4F1YTRU_yOw3oj47mA@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 12 Jul 2016 14:20:20 -0700
Message-ID: <CAOW+2dtb37QdEZZ6jMtzM2Mfknb8bFCHZUCSvnbvM8sNgvVnEA@mail.gmail.com>
To: Peter Thatcher <pthatcher@google.com>
Content-Type: multipart/alternative; boundary="94eb2c04486a3e2d13053776d723"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/83YsBpYlH-Js5l5bcLWatPG6TRU>
Cc: "ice@ietf.org" <ice@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Ice] I submitted and plan to present draft-thatcher-ice-remove-candidate in Berlin
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: Tue, 12 Jul 2016 21:20:48 -0000

Peter said:

"The real question is whether the removing agent needs to know whether the
receiving agent is going to do anything with the signal.  And since
everything will continue to work even if the receiving ​agent ignores the
signal (simply with some perhaps wasted resources), then it's not necessary
for negotiation at all."

[BA] The removing agent only needs to know if the receiving agent
understands removal if that will make a difference in subsequent behavior.
If a removed candidate will never be re-added, I don't think it matters,
because a receiving agent not understanding removal will eventually figure
out that the removed candidate is inactive, and that pairs involving the
removed candidate are unusable. But if it is desired to be able to re-add a
removed candidate without an ICE restart, then it might make a difference.

On Tue, Jul 12, 2016 at 10:21 AM, Peter Thatcher <pthatcher@google.com>
wrote:

>
>
> On Tue, Jul 12, 2016 at 10:07 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
>> Hi,
>>
>>
>>
>> The text says:
>>
>>
>>
>> “The Receiving Agent MAY keep the existing candidate pairs that use
>>
>>               the Removed Candidates and behave as though the Removed
>> Candidates
>>
>>               had not been removed for those candidate pairs.”
>>
>>
>>
>> What is meant by “behave”? Sending keep-alives? Sending media? That will
>> obviously not work.
>>
>
> ​Both keep-alives and media.  If the removed candidate is a TURN candidate
> that the removing agent wishes to deallocate, it may work for a short
> period of time before the removing agent actually deallocates it.  So the
> Receiving Agent may choose to keep sending media until it finds a different
> candidate pair to use instead.   Or it may not.
>
>
>>
>>
>> I think it would be good to state wether the usage/support of the
>> mechanism must be negotiated before it is used.
>>
> ​
> ​
> ​Signaling the removal of candidate never does any harm, so I don't see a
> need in negotiating that your going to signal removal (modulo a specific
> signaling protocol needing to figure out how to send new messages if it
> chooses to do so).  The real question is whether the removing agent needs
> to know whether the receiving agent is going to do anything with the
> signal.  And since everything will continue to work even if the receiving
> ​agent ignores the signal (simply with some perhaps wasted resources), then
> it's not necessary for negotiation at all.
>
> You are correct that this should be clear in the draft.  I will add it.
>
>
>
>>
>>
>> Regards,
>>
>>
>>
>> Christer
>>
>>
>>
>>
>>
>>
>>
>> *From:* Ice [mailto:ice-bounces@ietf.org] *On Behalf Of *Peter Thatcher
>> *Sent:* 12 July 2016 17:35
>> *To:* ice@ietf.org
>> *Subject:* [Ice] I submitted and plan to present
>> draft-thatcher-ice-remove-candidate in Berlin
>>
>>
>>
>> I submitted draft-thatcher-ice-remove-candidate and would like to speak
>> about in my allotted time on the agenda when I will also be speaking about draft-thatcher-ice-network-cost
>> and draft-thatcher-ice-renomination.
>>
>>
>>
>> It's a very simple draft. Basically it says you can "remove" candidates
>> just like trickle-ice allows you to add candidates. You could probably read
>> it in 3 minutes. Please do so:
>>
>>
>>
>> https://www.ietf.org/id/draft-thatcher-ice-remove-candidate-00.txt
>>
>>
>>
>> Thanks,
>>
>> Peter (Chair hat off)
>>
>
>
> _______________________________________________
> Ice mailing list
> Ice@ietf.org
> https://www.ietf.org/mailman/listinfo/ice
>
>