Re: [rtcweb] Proposal to break the ICE impasse

Roman Shpount <roman@telurix.com> Tue, 29 January 2019 22:08 UTC

Return-Path: <roman@telurix.com>
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 77A7F130EDB for <rtcweb@ietfa.amsl.com>; Tue, 29 Jan 2019 14:08:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.031
X-Spam-Level:
X-Spam-Status: No, score=-2.031 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01] 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 1vaFFSp8u6BE for <rtcweb@ietfa.amsl.com>; Tue, 29 Jan 2019 14:08:36 -0800 (PST)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 8067D12E7C1 for <rtcweb@ietf.org>; Tue, 29 Jan 2019 14:08:36 -0800 (PST)
Received: by mail-pg1-x536.google.com with SMTP id m1so9359476pgq.8 for <rtcweb@ietf.org>; Tue, 29 Jan 2019 14:08:36 -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=gY7x9kLNYLhoDVz8msp1B4b8ovpgweC56jkVdpMeWfk=; b=nmuoTXnnqv1DqVQrhV7lzkeMecb+9EETtvRj4XOlc9pBCNeZHTvq21X1UrWyZaAggh 76lz76upydHtCf4ZOjL25dWoSIEP+rvi726qMDoxAzMm0oBpDK+dbIeOLoq/qZQI2vWT Pzh/JEmcLRSJXOcGuEUk7wENeYKQKkrC9K1Z5AhHY6yMhtbCLmtXLJSwWjeCZtLWaNib KPVmCOlL+BzI+xBZ1Qsuz9NAoPCg+o8h0KMJV+pxMaat04mEqReXUv8PbhVyGj1odglj rxNQSiAlQ1az9Rb8GSuU8rTVWlRfe/HzErLZh3+N+3oCq6YZlLp7W3Y+1F6IjS0zVTrQ Wd/g==
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=gY7x9kLNYLhoDVz8msp1B4b8ovpgweC56jkVdpMeWfk=; b=dYh8ztos+ah1vHVkku6W8BO5Ds9IHSLVIZLWuL1R4aw0UfzLKS78fVnS8N46abv+uj g9/AWR+k8G5ooixaterOD9xBCQOVGWo/6MSUOuwqJZpkJ/er8lURaZ0YOyntZq5mYp7S ZSzpJK3Dz9rNX+qH/1GfFBzkTeZJ1UWKWKdtnw7LdhGgpedkwFFTHE++4yiVM0Kaqu+z 2T8UUW/WC1WPSbqgtfGyuVgwTTmpVerrpwYG9/KKkDbnF9+/13tBLpoo8zZBuLiAcNT0 +Apu5aNAot2MmAi0InUzNtoxDR8hwE6LBNE+NFkdrbIs6wlcwvNTDBd9c2lCxJB4pe6i 3g+Q==
X-Gm-Message-State: AJcUukfDYcsXKMYnYnHj36dSbyEqsSJg/nCx94uhr/RRsq66sOhszYkR Nqf1FPLkOY1+g8/srCxW1T1lNFSMGzs=
X-Google-Smtp-Source: ALg8bN4s7a8JzLtA0bNJ+Gudijj/VYSwkaC2KJdsHfGJyszYnLXSnC6+j3KQMZudeRwbKMajl9QYmw==
X-Received: by 2002:a63:c42:: with SMTP id 2mr25327253pgm.372.1548799715298; Tue, 29 Jan 2019 14:08:35 -0800 (PST)
Received: from mail-pl1-f169.google.com (mail-pl1-f169.google.com. [209.85.214.169]) by smtp.gmail.com with ESMTPSA id 5sm67250480pfz.149.2019.01.29.14.08.34 for <rtcweb@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jan 2019 14:08:34 -0800 (PST)
Received: by mail-pl1-f169.google.com with SMTP id u18so10001934plq.7 for <rtcweb@ietf.org>; Tue, 29 Jan 2019 14:08:34 -0800 (PST)
X-Received: by 2002:a17:902:8b88:: with SMTP id ay8mr28219532plb.55.1548799714253; Tue, 29 Jan 2019 14:08:34 -0800 (PST)
MIME-Version: 1.0
References: <97ed2641-8a7e-19a9-be38-a3458ca9212e@nostrum.com> <CABcZeBP9t0SgsHAuENo99D6ffKd7Mw0Xs1vzUCOzSS=WJN5z8A@mail.gmail.com> <HE1PR07MB3161B0F1D2B5AC9DA72DDFAD93950@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAOJ7v-3KHi0TUDsQvG6qq-qeNGBsqLxg+NC1c+Nxvgy0ks0d0g@mail.gmail.com> <CABcZeBNL=sWFfh=zwiuib80HPsno=GzF18gU+z3DrCZTK_PquA@mail.gmail.com> <CA+9kkMDh56CeXRGNSk_r-HrLkDNT5DnYc_FguXOdeccfq=LEMA@mail.gmail.com> <CABcZeBPboLf0bLUDTyJArxsPYSnUrULArmsZ9YshQCX+rEvexA@mail.gmail.com> <CA+9kkMCwCBHWEEADxVHT2ZbvWEi=bUBJ22icKHpA2p8Kg1fF9A@mail.gmail.com> <CALiegfnpj+Pu0Hg05iqHXCwhTefxn_Em7gTnzOXK897fzcyuwg@mail.gmail.com> <CAD5OKxvmQHT3TAt_=xCd_JKnPzXfnc=Mej-mr6KMsaKVoBkuSg@mail.gmail.com> <CALiegfm_jtv1bV3Ok6j20hkim8e6QxMYPrbbHejqoHnCHjMXpA@mail.gmail.com> <CAD5OKxsMWEE39O6hSc+UFjwTAa=z1A+XD5X2BY=Q7PEUdYE4UA@mail.gmail.com> <961E55AE-2072-4145-8BCF-62D67C6D150F@mozilla.com> <CAD5OKxuwhmAPvonV1rX1rN6yi08-4NPH1BOzVuJPUMEntnpRkw@mail.gmail.com> <CALiegfmZ_DSe7EFw48C6HoQ+bUReom4r0TTMf4wRG6UyAbgX2w@mail.gmail.com> <CAD5OKxvm_U=Tgvmxfi8hqiR=8tB_ueQtUSJJV5NLcVL8dBdHtw@mail.gmail.com> <CALiegfm1y_p3wDoXeckSw2BQ61gGYh4c9A7a=p0vi=BnWGoU4A@mail.gmail.com> <CAD5OKxvyDNm68_A1WVEyvsU52Jua+vHbrMpZJ0v0s7reP00OLQ@mail.gmail.com> <CABcZeBMi9nmue+Sw0+2Cf+Bs1NQE6cV-Ld+_9gMTDvbrWH_nfQ@mail.gmail.com>
In-Reply-To: <CABcZeBMi9nmue+Sw0+2Cf+Bs1NQE6cV-Ld+_9gMTDvbrWH_nfQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 29 Jan 2019 17:08:23 -0500
X-Gmail-Original-Message-ID: <CAD5OKxv_sTZzLc5J3CG=kdH4d_5GTwwv0Tuh2nXWixpQVHe_pA@mail.gmail.com>
Message-ID: <CAD5OKxv_sTZzLc5J3CG=kdH4d_5GTwwv0Tuh2nXWixpQVHe_pA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cbe2fa0580a00820"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/uUOztjJqH4n4V-IS-zVY0EJVpm0>
Subject: Re: [rtcweb] Proposal to break the ICE impasse
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2019 22:08:38 -0000

On Tue, Jan 29, 2019 at 4:53 PM Eric Rescorla <ekr@rtfm.com> wrote:

>
> On Tue, Jan 29, 2019 at 11:28 AM Roman Shpount <roman@telurix.com> wrote:
>
>> On Tue, Jan 29, 2019 at 2:05 PM Iñaki Baz Castillo <ibc@aliax.net> wrote:
>>
>>> I understand your point. But still I don't understand the purpose of the
>>> new draft (set TCP/DTLS/etc in proto line if there are just TCP candidates
>>> in the offer).
>>>
>>
>> The purpose is standard compliance. If nominated candidate is UDP, proto
>> line should be UDP. If nominated candidate is TCP, proto line should be
>> TCP. If you do not care about the c= and m= line, put the dummy values and
>> UDP there, but this breaks legacy interop by causing ICE mismatch.
>>
>
> This is two separate statements that don't necessarily follow form each
> other
>
> 1. This is a matter of standards compliance.
> 2. It breaks legacy interop
>
> I agree on point (1). I'm still waiting for someone to demonstrate point
> (2)
>
>>
>>
Unfortunately 2 is impossible to demonstrate to your satisfaction since:

a. Browsers currently do something different from the spec (once again is
being debated) and include additional candidates even after ICE nomination
was completed

b. Using UDP based proto when TCP based candidate is nominated only affects
server provider SBC or media servers. These components are typically easier
to patch when dealing with non-compliant implementations similar to current
JSEP clients. What you are arguing is to keep the "special" profile for
SBC/Media Servers indefinitely instead of making browsers and VoIP end
points do the same thing. This is simply moving the complexity from one
place to another.

As an observation, since JSEP currently mandates that c= and m= lines are
already updated (address and port) based on the ICE candidate which is
nominated, I am not sure if additional complexity of updating the proto
line at the same time is all that great.

Regards,
_____________
Roman Shpount