Return-Path: X-Original-To: rtcweb@ietfa.amsl.com Delivered-To: rtcweb@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D142129284 for ; Thu, 7 Feb 2019 08:44:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.011 X-Spam-Level: X-Spam-Status: No, score=0.011 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, 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=unavailable 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 7T7MInE40Qar for ; Thu, 7 Feb 2019 08:44:02 -0800 (PST) Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 05720124BF6 for ; Thu, 7 Feb 2019 08:44:02 -0800 (PST) Received: by mail-pf1-x434.google.com with SMTP id d22so141408pfo.3 for ; Thu, 07 Feb 2019 08:44:02 -0800 (PST) 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=IoYBOqruYN5tr2PW3ihlq0WKcoh43/9BXT5d+67ueXM=; b=qwe7oUR8zO71XB5JmMCLF2MxQ9dhWs68xzHRLeycslVwxPff2dvRZdqtSxsLey2bAA s+knFGn8uDTO71avCkHWzTusDWRNtZLBCgGpSnmU2jBc1v7JpO9m2Xc5DFQsi96gWw6R ETxkxsBwY+Bro5B3EPOcVXk1bZj0ItXAztiRG5DEYkckAhJHPx6LjK8ux9hf1sa4HkCv FsshdmNfoQzA9YqLjBhTfw6cxs7YrDftqCz5QEmAcMoCvCgCrj6bdApBir5AwK/e4Np2 huIdy/zCQ42AAKcvncGfmAYgarUvROlNTivF6IXN5xPtuLIT9fp6t9mPIhBkULVjNHGz ia2A== 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=IoYBOqruYN5tr2PW3ihlq0WKcoh43/9BXT5d+67ueXM=; b=ZzGN6FMUPAnlFg86Ej/drMHU1QvOyI0VYV6URAjzpcqFgGmavG54JKDH7LRIFQtu6w S1W/6JiVTKA7MmX3WQt7fCqSzm+k9ijXhEu5KR+rFN+Ogc/12ldYEtlPyGy1xJXIgkBk 8Hz8akhNe3JNdy0fNiMfs8ivY5DNDVjauCIajTuy9z2awWOlVIpfrSINLZaPscG53QB9 4W71UCqUmQ/Zs2pCvcqPnk+1vS65EDQdRY9RwZCKz+VmHP0fHgbbKC5haoj0bpK4Mk+K WCQApgWlMbziREDHNHnxGnP4/c5eaV4rQ9Kazf81OdyhQhvzfW/rFWduSpEVYKKhZ16T u4dA== X-Gm-Message-State: AHQUAuZEKVm1rJsbS0+bzuDFcYHw9XXepQzihi47z7pqgjl23Y/sVa3R hM+92iZTQPSGAy00RELHks611wXZSVw= X-Google-Smtp-Source: AHgI3IZbpPNwGH6uWenUm/emfpdsG//rx30XLcQOkIpHfXdd+tIR9uQEIbb0fBARXQbJ+5DU2z5Xlg== X-Received: by 2002:a62:29c3:: with SMTP id p186mr17246400pfp.117.1549557841179; Thu, 07 Feb 2019 08:44:01 -0800 (PST) Received: from mail-pg1-f173.google.com (mail-pg1-f173.google.com. [209.85.215.173]) by smtp.gmail.com with ESMTPSA id b26sm20189630pfe.91.2019.02.07.08.44.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Feb 2019 08:44:00 -0800 (PST) Received: by mail-pg1-f173.google.com with SMTP id w7so148121pgp.13 for ; Thu, 07 Feb 2019 08:44:00 -0800 (PST) X-Received: by 2002:a62:4bcf:: with SMTP id d76mr17709642pfj.170.1549557840020; Thu, 07 Feb 2019 08:44:00 -0800 (PST) MIME-Version: 1.0 References: <24551658-0943-431C-B319-D74B5DC169B9@gmail.com> <0fd991e5-73c9-edd2-67e4-2c527ccc6e95@alvestrand.no> In-Reply-To: From: Roman Shpount Date: Thu, 7 Feb 2019 11:43:47 -0500 X-Gmail-Original-Message-ID: Message-ID: To: Justin Uberti Cc: Harald Alvestrand , RTCWeb IETF Content-Type: multipart/alternative; boundary="0000000000009d0c3d0581508c0c" Archived-At: Subject: Re: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate? X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2019 16:44:04 -0000 --0000000000009d0c3d0581508c0c Content-Type: text/plain; charset="UTF-8" On Thu, Feb 7, 2019 at 11:28 AM Justin Uberti wrote: > Note also that only host candidates will be mDNS; srflx and relay > candidates will continue to work as before. > > If client is running without STUN or TURN servers and communicates with a server on the public IP with UDP and TCP candidates, all the candidates in the client session description will be mDNS. This use case was working without mDNS, but it is broken now, since server ends up with session description with no usable candidates, which means ICE nomination stops before it even begins or any peer reflexive candidates are received. Amusingly, this still works with ICE-lite, since server there will simply wait for connectivity checks while ignoring all the client candidate information. Regards, _____________ Roman Shpount --0000000000009d0c3d0581508c0c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Feb= 7, 2019 at 11:28 AM Justin Uberti <juberti=3D40google.com@dmarc.ietf.org> = wrote:
Note also that only host can= didates will be mDNS; srflx and relay candidates will continue to work as b= efore.=C2=A0


If client= is running without STUN or TURN servers and communicates with a server on = the public IP with UDP and TCP candidates, all the candidates in the client= session description will be mDNS. This use case was working without mDNS, = but it is broken now, since server ends up with session description with no= usable candidates, which means ICE nomination stops before it even begins = or any peer reflexive candidates are received.

Amu= singly, this still works with ICE-lite, since server there will simply wait= for connectivity checks while ignoring all the client candidate informatio= n.

Regards,
_____________
Roman Shpount
=C2= =A0
--0000000000009d0c3d0581508c0c--