Re: [Ice] ICE PAC: When to start the timer waiting for possible peer reflexive candidates?

Roman Shpount <roman@telurix.com> Fri, 26 April 2019 20:46 UTC

Return-Path: <roman@telurix.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 EC0E31205FF for <ice@ietfa.amsl.com>; Fri, 26 Apr 2019 13:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.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 wmqf-pRPVGDY for <ice@ietfa.amsl.com>; Fri, 26 Apr 2019 13:46:48 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 DE1AF12025B for <ice@ietf.org>; Fri, 26 Apr 2019 13:46:48 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id d9so2093172pls.8 for <ice@ietf.org>; Fri, 26 Apr 2019 13:46:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IUfGJNmbW9e0p9/1G5T2MqvAFjjkyAV5AEh/J+kvMj8=; b=BVe+cSRW70PQ7HphgqYnLpWvlwL+GMpmeaFdimb48bBL9kO0TLSq/7+2EQRXhHJ2u6 ZZVZ3edbYAJ9Dtc/jtzv1jqTpA1/mKhxVfZ2z1dXjBIm9gkjE3LVx1h3sVFPZuVdNGTV yiOBEB5WbQJDnsQSRJuh4E71BUY59jNgAmkX8L8n3d0kXz+KWz1k/qhvNT802wyAaeGG 04OZgMLmG9NCu6PbWDfH3q61UuTzdnVCOTZ0fhl6O48jUPiOIF7VQdv52idE20Lio398 8QEQHiTJgnk7/599UAzK4VpIc7my245m4ZHUvDed6iizwRMBkil0E0gkgvmTcvfirjeZ 60Xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IUfGJNmbW9e0p9/1G5T2MqvAFjjkyAV5AEh/J+kvMj8=; b=NGbz4lRt0o694PWZPXjCjKcoTTOcwWtrPa/YzHSqYRzEJcpXA26g4TVMQtf3Q33zab 7GuDO/YpRmMqWBcjqbRRTruH8TtycnrT7gtdK6ZBr88N5QnReSv9w7MPGdLmSLKia8pa /6It8hvb1bH4OhlL1O8kfD170M4Q9QxWiJZVwcIQjx3v0993clZdKggPfH/4AZAyAmrc 6EF7j4BUqu9aEKCW2ks8+Cdq1C1TSHYgTIy8VVc+hca1I4IvasiwLQqE1ts6lZfMwLkX 58YZagxNYIUwAGwORMAssJfp3PY80GXnPwT6sVkOF5LzoP/PyXF2SOxNYpeknzJyR9kh zPPQ==
X-Gm-Message-State: APjAAAWPXTgqO52DVAFR2jN2gS935qKduJ1JNIooa2qsII/0HmhZT469 mLog4ealXoZywCoc/Rvq2+e4bDtxua0=
X-Google-Smtp-Source: APXvYqw52zCzGEQEPHa3RKVjfHVZn+ziG0xfux+LTPSCSWaFueH1/wgtMUyJEOU4FTNwvcrgq56rAw==
X-Received: by 2002:a17:902:70c6:: with SMTP id l6mr46892684plt.95.1556311608209; Fri, 26 Apr 2019 13:46:48 -0700 (PDT)
Received: from mail-pf1-f176.google.com (mail-pf1-f176.google.com. [209.85.210.176]) by smtp.gmail.com with ESMTPSA id p20sm31621768pgh.83.2019.04.26.13.46.47 for <ice@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Apr 2019 13:46:47 -0700 (PDT)
Received: by mail-pf1-f176.google.com with SMTP id y13so2249887pfm.11 for <ice@ietf.org>; Fri, 26 Apr 2019 13:46:47 -0700 (PDT)
X-Received: by 2002:a65:6110:: with SMTP id z16mr37257929pgu.131.1556311607397; Fri, 26 Apr 2019 13:46:47 -0700 (PDT)
MIME-Version: 1.0
References: <3A66B735-03C9-41FF-95AD-500B0D469C80@ericsson.com> <CAD5OKxsMgNTQPNP4Ni72H+yD4iUeyNK+x6CSvdBApGnPTpr_vg@mail.gmail.com> <A4EC3C01-4D7D-45DF-876D-E58706F74866@ericsson.com> <CAD5OKxt8tDemkK=v4X1gjwJGLYrxcd95S7uV53_fsga6grZ_rA@mail.gmail.com> <30518269-CA9D-4F50-8CE3-062A01DBCD7F@mozilla.com> <CAD5OKxvmRK8Xzu4FSRv3Lgdg-VrrufzGhjAdSmfcLLkrm-jtjw@mail.gmail.com> <0AD3077C-74FA-4585-942A-375B83B3A7A0@ericsson.com> <CAD5OKxsgpf7Hv_nxFOZFwfNk7-_xNRzmoPTA2bZCqZo3wzudKQ@mail.gmail.com> <HE1PR07MB316172053751D307F83DE0EB933E0@HE1PR07MB3161.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB316172053751D307F83DE0EB933E0@HE1PR07MB3161.eurprd07.prod.outlook.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 26 Apr 2019 16:46:39 -0400
X-Gmail-Original-Message-ID: <CAD5OKxu332E8vzdc4dt09NxXGf9Cr2izwECDAQjc7V_YDx3r5w@mail.gmail.com>
Message-ID: <CAD5OKxu332E8vzdc4dt09NxXGf9Cr2izwECDAQjc7V_YDx3r5w@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Nils Ohlmeier <nohlmeier@mozilla.com>, "ice@ietf.org" <ice@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000084d65b05877508bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/8d8HOi1ptVFa9F4_zIyB3O2UGDM>
Subject: Re: [Ice] ICE PAC: When to start the timer waiting for possible peer reflexive candidates?
X-BeenThere: ice@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 26 Apr 2019 20:46:51 -0000

Hi Christer,

On Fri, Apr 26, 2019 at 4:28 PM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> In a non-trickle case, I think it would be very strange if the agent
> didn’t get any candidates front the peer agent.
>
>
I have just sent a message to the mmusic list regarding ice-sip-sdp and
offers with no candidates. There is nothing that technically prohibits it
in RFC 5245, so I thought it makes sense to add a note which explicitly
allows it in ice-sip-sdp.

There is a valid use case for this, when client is behind NAT and it would
only communicate with a server on public address. In such cases, client
does not need to collect any candidates and simply send the offer. Once it
gets the answer from the server with the public address, client can send a
STUN bind request to server address using a local socket not bound to any
address, which will use default route. There are multiple benefits for
implementing it this way, one of which would be client privacy.

Regards,
_____________
Roman Shpount