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

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 06 July 2019 21:51 UTC

Return-Path: <christer.holmberg@ericsson.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 03BB91200EB for <ice@ietfa.amsl.com>; Sat, 6 Jul 2019 14:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 07i3YYd9D6gZ for <ice@ietfa.amsl.com>; Sat, 6 Jul 2019 14:51:06 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00086.outbound.protection.outlook.com [40.107.0.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E627A1200D6 for <ice@ietf.org>; Sat, 6 Jul 2019 14:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WPBxQBLjb2ygrSu0NELh7lNvAnQxJHWTyJJ+5rCA/yI=; b=mUQrVGlumrvx6+A+Llxyw3iADGpK10Y1A6I3s1k8mTXbtMWFzFoh6M7b/Ce+UYB4lAIXbV7C/o+djQipwCFMw3sIryAgvOgWWuEfiApVW/S/PmudYRMis0QtaVjABz6P8DkXJzNBVSpNw6f76WwaVlp2AlA8hxhoZgO80wjJIGA=
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3243.eurprd07.prod.outlook.com (10.170.246.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.14; Sat, 6 Jul 2019 21:51:00 +0000
Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::5050:a3a9:be80:cf43]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::5050:a3a9:be80:cf43%5]) with mapi id 15.20.2073.004; Sat, 6 Jul 2019 21:51:00 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
CC: Harald Alvestrand <harald@alvestrand.no>, "ice@ietf.org" <ice@ietf.org>
Thread-Topic: [Ice] ICE PAC: When to start the timer waiting for possible peer reflexive candidates? - discussion restart
Thread-Index: AQHVFUwc5tNKLJLjCke9cDBba/EsEKao6YiAgAIHR4CAAAOSAIALwuyAgALR9zCAA+TQgIAAT7gggABkiACAADqWAA==
Date: Sat, 06 Jul 2019 21:50:59 +0000
Message-ID: <HE1PR07MB3161B5D8D93E3335AB4A81C093F40@HE1PR07MB3161.eurprd07.prod.outlook.com>
References: <AFCE8799-8865-454F-8478-81CE11E9B454@ericsson.com> <1aa5aac7-af59-4e3b-8651-18f6e6431a2d@alvestrand.no> <66678ADA-7C02-4D9D-B9D2-308873BC0125@ericsson.com> <7a829bc0-d066-a3be-b7be-9b39ce799821@alvestrand.no> <CAJrXDUHZJURLvzBYX2MGcMsrFgyOagW5=s1OSXwDmTZpsruD0A@mail.gmail.com> <VI1PR07MB3167F21EF7A1009B8EB9948B93FB0@VI1PR07MB3167.eurprd07.prod.outlook.com> <ae88593c-633f-8c18-eac6-82ba3673dce7@alvestrand.no> <HE1PR07MB31614FEC9997294294BB63A393F40@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxt_nvwYEDNEFtRSrdDK2BOoTWOL52_5mz99o7M3=5q6kA@mail.gmail.com>
In-Reply-To: <CAD5OKxt_nvwYEDNEFtRSrdDK2BOoTWOL52_5mz99o7M3=5q6kA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com;
x-originating-ip: [62.113.190.248]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ed01fb0e-756e-4e74-6fb0-08d7025c0895
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:HE1PR07MB3243;
x-ms-traffictypediagnostic: HE1PR07MB3243:
x-microsoft-antispam-prvs: <HE1PR07MB32436D7C411C39707DC3DF3D93F40@HE1PR07MB3243.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00909363D5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(136003)(366004)(376002)(346002)(39860400002)(189003)(199004)(186003)(86362001)(14444005)(102836004)(99286004)(256004)(68736007)(4326008)(26005)(305945005)(52536014)(6916009)(2906002)(14454004)(66946007)(73956011)(478600001)(66446008)(66476007)(76176011)(7696005)(25786009)(66556008)(6246003)(76116006)(64756008)(6116002)(54906003)(229853002)(486006)(8676002)(81156014)(5660300002)(33656002)(44832011)(8936002)(476003)(71200400001)(3846002)(71190400001)(6506007)(316002)(11346002)(7736002)(6436002)(53936002)(9686003)(66066001)(81166006)(446003)(55016002)(74316002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3243; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Q19KFoosUMkqdJXKMQSv52qapDGi9Xz5RWNBPmAwacuLAaxX2fC4+Deb+Rex6hzho6WqjqXg0IThzLYEJ/ix00trpt82wsl6mSkRFfP9BNoXLEtFkEb9VwDS3uf+w2WL8Jbia7RtjJk3NSCH3UYF8Pab0h0IbMH0peZY4oKDE9oW8iEXp+8xTX2N5lO82rFRfvXaU7wbDdPneyhCScojHPTKB7RujoQFHiMPb90FVMe+AF7JewXs44sPrR59XkBzhwzzA3K17CPB8xr8qgxqsf9jEWKSK5gUh85b3HzXpKPfiXWrUPxY+ss//EsGD9VV19sge87bVu423AxkNCbtxy2nbHbchjBVZfRw9ksXvkdzsuuPJon5yM7vPdPT1GtxBe9HFoFgFrAuya934OEldQ3GFXwOhlQjzN4f1mrqS/A=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ed01fb0e-756e-4e74-6fb0-08d7025c0895
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jul 2019 21:50:59.8713 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: christer.holmberg@ericsson.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3243
Archived-At: <https://mailarchive.ietf.org/arch/msg/ice/sl--RPuSxbKKvhOME5_XQi3WCyw>
Subject: Re: [Ice] ICE PAC: When to start the timer waiting for possible peer reflexive candidates? - discussion restart
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: Sat, 06 Jul 2019 21:51:11 -0000

Hi,

...

>If there are remote candidates to check, then ICE should continue checking them. Part of the problem is that when ICE is starting, it is unclear 
>if remote candidate have not been received yet, no usable remote candidates where received, or remote candidates are not going to be sent 
>at all.  Also, checking remote candidates can end very quickly if remote candidates are unreachable (fail immediately with ICMP remote address unreachable message). 

Ok, let's assume we DO have remote candidates, and the timer expires. We discard the fact that the timer expires, and go on checking the remote candidates, as you suggested.

Then, at some point we have checked all remote candidates, but we have NOT found successful pairs for all streams. So, since the timer already expired, we declare ICE failure.

I thought the whole idea was to still wait for some time after we have tried all remote candidates, in case we will receive peer reflexive candidates, before we declare ICE failure.

But, as I said earlier, I am fine doing as you and others suggest. All I am saying is that the draft needs to describe what to do if the timer expires while there are still untested remote candidates. If the solution is to discard the timer expiration, then it needs to be documented.

Regards,

Christer