IETF Logo Mail Archive

Re: [MMUSIC] [rtcweb] Default proto transport in JSEP

Roman Shpount <roman@telurix.com> Mon, 19 November 2018 21:21 UTC

Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5D0B130DE5 for <mmusic@ietfa.amsl.com>; Mon, 19 Nov 2018 13:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] 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 H-fjEYTFl_0z for <mmusic@ietfa.amsl.com>; Mon, 19 Nov 2018 13:21:01 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 DE21D130934 for <mmusic@ietf.org>; Mon, 19 Nov 2018 13:21:01 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id v1-v6so8039835plo.2 for <mmusic@ietf.org>; Mon, 19 Nov 2018 13:21:01 -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=1kFedqBjw1q87B3nWocG0ELPLDbQf0PWVcdtAsnUfIk=; b=SD00JNHNrK4dAeWS2vTrxEGPgnmMd3qwbQmDy0/yxTzr/X30GoUIfadEhoNsoYqUV3 YKSj11GhLVBFEBKRfzN25Ls4z1myw4A1tlueEnk4qinwlPABtyMuZLB6qV8ljOjf6TRi iW2SMTeCHmICSNCDOeJerGCA6wDnrVyy8xAe1THDhCQizuFYG8VXYb+SolYVx8mn94QG OlLiAs4NwBFZwgytzU9N4eB2rrA38pzPQ3sKny4VXK1fNTrU9Lxe8J96VcBUZ3MZB5G2 AI5djXkQSr21NILV5BXcPROPXvHo76tUDnY+DSN+es3qm/eagMdgYXalaKrX1x9vpWL8 2LEA==
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=1kFedqBjw1q87B3nWocG0ELPLDbQf0PWVcdtAsnUfIk=; b=oipT1+2YCHYx3UexNoqwCYrtBzniYSStZtoiyBlGM3jyptPQd1J8QIK/BSF+fGqJ2t XFRCT/mECJLAcJAxEt6qdbhwQwNjAYp0XNB0ufN/CbMRiIegQ/UquwF65igXe4lStCJz PmklnbrKrVGinFtlgm0+4KYqgVKm0Fv46ZjajQSnc1ClBhZrHyVqsY9aZ41WS/w72NFR +inrh1Lvh9NlTiQYwpGb2e8ldaZhGGNLDRfKByqULNjakatexgcoSsOLpT3iYnuviKwW 3r91JnxgV8RwAfFaJQfzzLX1ACmE/G0xB/iMTxhiISwunnOEJvaCVRAcWtAHELkSD5CC 3x5Q==
X-Gm-Message-State: AGRZ1gI1pTqJze6eQJ/XBk1JFN3dzhMdyb5y2BgCj7nGATYGNQrjk1D9 mn265lVt9a0LdGvGcjSt1z7NO//lXL4=
X-Google-Smtp-Source: AJdET5dGnHEsQIfR9fWHQNx2RSqNB9ACxqhxkxfHRlCTK3ceGAsw14V/RZEyeRMyBSU2PF8L4wl/ag==
X-Received: by 2002:a17:902:1e3:: with SMTP id b90-v6mr23794062plb.117.1542662461348; Mon, 19 Nov 2018 13:21:01 -0800 (PST)
Received: from mail-pf1-f177.google.com (mail-pf1-f177.google.com. [209.85.210.177]) by smtp.gmail.com with ESMTPSA id t21sm33610492pgg.24.2018.11.19.13.21.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Nov 2018 13:21:00 -0800 (PST)
Received: by mail-pf1-f177.google.com with SMTP id v68-v6so15461129pfk.0; Mon, 19 Nov 2018 13:21:00 -0800 (PST)
X-Received: by 2002:a63:b4c:: with SMTP id a12mr21895065pgl.131.1542662460459; Mon, 19 Nov 2018 13:21:00 -0800 (PST)
MIME-Version: 1.0
References: <CA+9kkMADnZJBaV0hfLuwGU0bGBEP5tCPZ=8Zd_85Dgzi37ghAQ@mail.gmail.com> <CAD5OKxsNFFmER__H0+5Mzts58yn9cWLMEADhSnLR4nreKD9WAQ@mail.gmail.com> <CALiegfkHXv6f8P3C-C=2RKCyxWfzCAzkzOqxBXmmsNCPrZzFfg@mail.gmail.com> <CAD5OKxswZdGm1CYvy=NoyEtN-eFFp7Sc8mmGT7jAJ-q3msJYXA@mail.gmail.com> <CALiegfmFV=988+WuViUQRGJRgR=mcqS9Y+eDnL4pH6VrbJRvCQ@mail.gmail.com> <CAD5OKxtwuQu0du+ptmJpX0ALQnUtjLG==NanP8OB51D4M9fYhg@mail.gmail.com> <CALiegfnMbwTruVKU-VnsZvddqRhnuCm1k8zLcLSuWSs9zT1JUA@mail.gmail.com> <CAD5OKxtxAiBbVY4HQjfjwqfsGoUxAZzmmrTWVfe7pG6MTsHGRA@mail.gmail.com> <CALiegfnVOFvUKYMRp7z0Q3aVyzbi=+JuyXmH+PL6_pNW9j9PVA@mail.gmail.com> <CAD5OKxtpepraJWVbJy2+x_4pFbeqF57=yh1GVF-WoYGBX1OV-Q@mail.gmail.com> <CALiegf=ffb1UL0FPrk770Q-ACQL-ySAqxBzB1M0yJXZUM6y9sg@mail.gmail.com>
In-Reply-To: <CALiegf=ffb1UL0FPrk770Q-ACQL-ySAqxBzB1M0yJXZUM6y9sg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 19 Nov 2018 16:20:49 -0500
X-Gmail-Original-Message-ID: <CAD5OKxtj=nEWjOWztcAVMDsFOFRGO7hQaKUsn-Pqbk7Ma64Trg@mail.gmail.com>
Message-ID: <CAD5OKxtj=nEWjOWztcAVMDsFOFRGO7hQaKUsn-Pqbk7Ma64Trg@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Cc: RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f6d65d057b0b1715"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jnHNzlNn1nQdPwAp1lFWakWGzEU>
Subject: Re: [MMUSIC] [rtcweb] Default proto transport in JSEP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 21:21:05 -0000

On Mon, Nov 19, 2018 at 4:17 PM Iñaki Baz Castillo <ibc@aliax.net> wrote:

> On Mon, 19 Nov 2018 at 22:08, Roman Shpount <roman@telurix.com> wrote:
>
> > If anybody ever implements data channels over QUICK vs SCTP, proto is
> the place to specify this. ICE candidates will only tell the end point that
> UDP vs TCP,. Kind only tells the type of stream. If there is more then one
> way to transport this data (SCTP vs QUICK), proto is required.
>
> I understand your points, and you are right in all of them. I just
> don't believe that this is gonna happen in SIP world within next 25
> years. I mean: in order to explain this you have moved to
> DataChannels, which will never exist in SIP-land (BFCP already exists
> which is implemented by 2-3 devices).
>
>
In SIP land it is the the difference between RTP/AVP, RTP/SAVP, and
UDP/TLS/RTP/SAVP which is the problem. In first case no encryption is
allowed, in second case SDES-SRTP is required, and in third case DTLS-SRTP
is required. Then there are AVP vs AVPF differences.

Regards,
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email