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

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 03 December 2018 21:01 UTC

Return-Path: <christer.holmberg@ericsson.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 5DC9C12D4E8 for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 13:01:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.748
X-Spam-Level:
X-Spam-Status: No, score=-5.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=eT2Ccvnc; dkim=pass (1024-bit key) header.d=ericsson.com header.b=QGbagpeE
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 y6kbk1ZGGpgo for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 13:01:37 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A64241200B3 for <rtcweb@ietf.org>; Mon, 3 Dec 2018 13:01:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1543870894; x=1546462894; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=EKw/QLGCbgLxmUXvVU3VwlZVGnvla7kVfg8JkuMpAdY=; b=eT2CcvncwLvFNs15pUbi3NK8nza+dsKNH7cqWl2zh1kuF4nzHPRbuV+RwK3KFtqC MoemIVF3B98cw7cgz6DIfRecBsjLsNdib1vCdsPGexko6LoMiPW6g1qEUrdRnKzp 3ePDAk7qPNUJRiAmSQxPTECL/h+tVvpjNYZyOZtoUfg=;
X-AuditID: c1b4fb25-5e9ff7000000191f-62-5c0599ae476a
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 5B.DC.06431.EA9950C5; Mon, 3 Dec 2018 22:01:34 +0100 (CET)
Received: from ESESBMB501.ericsson.se (153.88.183.168) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Mon, 3 Dec 2018 22:01:34 +0100
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB501.ericsson.se (153.88.183.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Mon, 3 Dec 2018 22:01:34 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EKw/QLGCbgLxmUXvVU3VwlZVGnvla7kVfg8JkuMpAdY=; b=QGbagpeEv8bZ9agK4DVHFvS3+cOB/SmlzNC/dQV4zX4MfIY1OCp8qa1vc68TQE3dUfz5W8XLHs4g1vLgZZ6QrijB4cMpEyEbS8vC5ly53RIJYd0HF8y9iBswz9++kAsstKqX3CStv2BcoRI4939s/fGo087qdIIDkle5I961PJE=
Received: from AM6PR07MB5621.eurprd07.prod.outlook.com (20.178.91.14) by AM6PR07MB5415.eurprd07.prod.outlook.com (20.178.88.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1404.7; Mon, 3 Dec 2018 21:01:33 +0000
Received: from AM6PR07MB5621.eurprd07.prod.outlook.com ([fe80::a5dd:4302:feec:e113]) by AM6PR07MB5621.eurprd07.prod.outlook.com ([fe80::a5dd:4302:feec:e113%3]) with mapi id 15.20.1382.020; Mon, 3 Dec 2018 21:01:33 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Adam Roach - SIPCORE Chair <adam@nostrum.com>
CC: RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Thread-Topic: [rtcweb] [MMUSIC] Default proto transport in JSEP
Thread-Index: AQHUhquP7oWmB9W6S0+oK/sz+g4vAaVlZEyAgAAFLoCAABfmgIAABUCAgAf/CNyAAAM1xA==
Date: Mon, 3 Dec 2018 21:01:33 +0000
Message-ID: <AM6PR07MB562184CD3351856DBC45A71B93AE0@AM6PR07MB5621.eurprd07.prod.outlook.com>
References: <CA+9kkMADnZJBaV0hfLuwGU0bGBEP5tCPZ=8Zd_85Dgzi37ghAQ@mail.gmail.com> <CAD5OKxsNFFmER__H0+5Mzts58yn9cWLMEADhSnLR4nreKD9WAQ@mail.gmail.com> <9B9B741B-622F-4565-899B-700636408F6C@iii.ca> <CAD5OKxv9r08RLvMSM4h11A6sXU9E=u_8Qvy-TBfjNcwkhcqf3w@mail.gmail.com> <54ebb208-e7b3-a0f1-6a5c-4745d3a56447@cisco.com> <CAD5OKxut5Lr+Bmyc20y+vV=+_RESw+h72DYLnt3G1_BjS6sTVA@mail.gmail.com> <1346FE48-5D61-48B7-BF37-3D7BAA930DB0@iii.ca> <CAD5OKxv0N+TF3L3bB9KPm4vqQdPZKE=1zkdw1PaV7CpNJ2kYaQ@mail.gmail.com> <110dc822-b3be-7bc2-dcc5-9e6c8277e0d1@nostrum.com>, <CAD5OKxtKOLovNCi0cJiEiHD+M3tCda7ZSecU8EJKxVPuFs7maQ@mail.gmail.com>, <AM6PR07MB5621291E0EA9E72A8065380A93AE0@AM6PR07MB5621.eurprd07.prod.outlook.com>
In-Reply-To: <AM6PR07MB5621291E0EA9E72A8065380A93AE0@AM6PR07MB5621.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [37.136.29.129]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM6PR07MB5415; 6:I/Ng3/6IlQEkTYbjWQdsShBTGXJpopugLvEdUk0z6x2R4o3VDb8twS23sEYSHIbA2yCVaxMLaPAlbPofoOlR/OjwVgANwgAYwUppd8YTAAkMvpi8xn0q60FbWeAicckpS9sg2aWHbzvpyDurKJr8w8CLNi+nhMqQvA3nPDng2lZVaETZTjc6cQKQS0tTNVWzhTkjMHwXN9MGoO9czHH19Ay6Mzjh48vd77TCUkQm2Z8QKcrcx9VH0I4DViB/DAyvkrgOBxTErgb9P7/n575jjdHNsaJ71sIsz4RtpiEE1N47/1sO5dohOklj/cLGHuz2Ov5gutT8OwAyjfAAFklFc6xKs01/CGSDkpAezV/ilqtN/44sdpP6JZg0oBb9gKqqCWez8jDY2h5B/KZmwVqqv6a0YIyO0dgnxZ7GUONeuFY5QWBtVNpPyowwA1vU/AwdzjXViZYFkLib84YrLSmqUQ==; 5:PIO5A5zkJhRa9cqjmxUecyrBhGkM7bbgbWVIOQ4RXNAyuHIPGlxNft8hb8dWIdg9Dwct3pyWwQ97EDyc7fY2PUHvs7Av4czt7I6w29t/GbRbr4uV2K8O3gRTebChifuKe+geCYO2URAd3PshlJLOaz6xOGP+yPtSUhWpstBwxNU=; 7:9xqGznCy/a6zzdis/DKJeXeVzCDvfjtubQiLdrROwvW874dG4ITcFuakta7UGmHreV6MBbJjv2gajiFyAbdFgrFp+qPWl3DUDBhOdBEmLmLTO1zDuUc8gX47Wqu54zL4ufZRXlO1fow6WFOAUOU0BQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 02f1e7b7-c5aa-44fc-11dd-08d6596281ab
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:AM6PR07MB5415;
x-ms-traffictypediagnostic: AM6PR07MB5415:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com;
x-microsoft-antispam-prvs: <AM6PR07MB5415F55B90D9953484EC29EF93AE0@AM6PR07MB5415.eurprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(3231455)(999002)(944501493)(52105112)(10201501046)(148016)(149066)(150057)(6041310)(20161123560045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:AM6PR07MB5415; BCL:0; PCL:0; RULEID:; SRVR:AM6PR07MB5415;
x-forefront-prvs: 08756AC3C8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(39860400002)(136003)(346002)(376002)(199004)(189003)(2940100002)(6606003)(54896002)(93886005)(97736004)(54906003)(9686003)(6246003)(55016002)(66066001)(14454004)(53936002)(6116002)(4326008)(5070765005)(236005)(110136005)(6436002)(6506007)(76176011)(476003)(478600001)(53546011)(486006)(7696005)(93156006)(44832011)(966005)(3846002)(6306002)(5660300001)(186003)(26005)(99286004)(229853002)(68736007)(8676002)(71190400001)(86362001)(106356001)(74316002)(446003)(81166006)(2906002)(7736002)(71200400001)(102836004)(33656002)(316002)(8936002)(14444005)(256004)(11346002)(105586002)(19627405001)(81156014)(606006)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:AM6PR07MB5415; H:AM6PR07MB5621.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: wsnJItF5ogj3GFPA6xmVR85x+WRMP3pnF89m4yR106EX5RmGFr8+LjnD/sMVCAZrO/8JaSW4PUI/uUSLJ+aqkt3oPPZs3ASyenvZ8t1npEXyxelM2wRtUkBYrJZZwCOKVtPqTocw6+5gKyTeRou5CNGtdFsTfKHBqgc9IPmqBLl0nCOHdzyM2QVDH+AgHBe1ruP0NoP/L/xyI1gtu1IKDgIICMukyj4YXho0ALgC5hix1TFxUDBbC5B9tkqVlAgxepr2p+28jfAHMI6m6hn9TzjICV5d1/NXZyF8HhhexXbqNu+WYgElWZW3C8JUHpJSO3TfYLP2vD3akZpWO0UiQAa9YGqc95R8JRQrF+jhROg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM6PR07MB562184CD3351856DBC45A71B93AE0AM6PR07MB5621eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 02f1e7b7-c5aa-44fc-11dd-08d6596281ab
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Dec 2018 21:01:33.6172 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR07MB5415
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTYRTHe97L9moO3paXk1LQyj4oc2pCI0zLL9kHrU8hOsuVLyrqnNs0 TQVRIpuINlzeKs1mXihpJjbNyE2LWrPZ7GJCobjScpWRJuUt3TvBb79zzv/P/5yHh8L5/aQv lSZTMQqZNEPAcSfq4h5eEHbWkZLg50Nicf9KM1esbZ0ixLUjWlx8b/Uy9ygRrdP9xaLre+1E 9Hi1/BQe7x6ezGSk5TIKUUSSe2qX8SNXrm9Dee3frFgxMmqQGrlRQIeB2TGIqZE7xaeHEEyX feewxQKCNdsMwRa3Mei0mJ0ygq7CwdJ3xSWrxODf8hjJFpMIvtQsrE8oikOLoXw1cCPEkz4N 95d+OQNxOgKe1r7HNnjnOt8YLSNYTSQYtSXkpr6p14FvMEHvh0/qCqeGR0ug3nbVtdIwCdaB l06DG50Ib0pbnAGI9oZF812MDfOBcXsjxl5Kg67firPsBV+nVkmW94JZPc9leTfYGsvRRgDQ 7zhQOzhBsAMhzGm1LnMM9NSoCVY0gmDuWoVLFACPFx5h7BZSeNIx4TKkw7PPl1zvvQc6KiZd ZisO5rezqAqJ6rdsy3IW9Br0TubRO+BFnZ1g+8Hw81UjznIg3Lk162IR6OeH0dZ+E+J2IC8l ozyXmRJ6MIhRpJ1XKrNkQTJG1YXW/5Sxe8nfgEYdx0yIppDAgxdVSUr4pDRXmZ9pQkDhAk+e PJuQ8HnJ0vyLjCLrrCIng1GakB9FCHx4k4cexPPpFKmKSWcYOaPYnGKUm28xyhZ+aN/up4gr ij1RKNMUHLb1lFaFnTzTPBSu9xB6dP92E415W48Xh+sb7KM+OZmOluoj6UVtVtKv9cdAzNq+ kriEOv6BysjrJl2StqswJG869OacZckQ1eeZEFu9vBZUb9G8tspLhLH5STPWhgKVv2ZlG2+e gxar6T+JcYZdAkKZKg0JwBVK6X9lnzDkTwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/4H7sdYm6VAFHE3eLpdtsHDkPPxw>
Subject: Re: [rtcweb] [MMUSIC] Default proto transport in JSEP
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: Mon, 03 Dec 2018 21:01:40 -0000

Hi,


In addition, even from a pure WebRTC perspective, there is no guarantee that both endpoints are implementing JSEP, so any WebRTC-specific ICE modification would probably have to be done in a separate document.


Regards,


Christer


________________________________
From: rtcweb <rtcweb-bounces@ietf.org> on behalf of Christer Holmberg <christer.holmberg@ericsson.com>
Sent: Monday, December 3, 2018 10:58 PM
To: Roman Shpount; Adam Roach - SIPCORE Chair
Cc: RTCWeb IETF; mmusic WG
Subject: Re: [rtcweb] [MMUSIC] Default proto transport in JSEP



Hi,

I am jumping late into the circle, but I share Roman's concern regarding the suggested change to 5.2.2. I think the WHOLE m= line (including the protocol) shall match the currently used properties. You may also end up having SDP attributes that are not defined the for the indicated protocol (since you are using another protocol). That is asking for interoperability problems, in my opinion.

I've probably missed it, but what is the "catastrophic flaw" (to use Adam's words) that would require this change, and misalign the JSEP ICE procedures from all the documents Roman listed?

Regards,

Christer

________________________________
From: rtcweb <rtcweb-bounces@ietf.org> on behalf of Roman Shpount <roman@telurix.com>
Sent: Wednesday, November 28, 2018 8:41 PM
To: Adam Roach - SIPCORE Chair
Cc: RTCWeb IETF; mmusic WG
Subject: Re: [rtcweb] [MMUSIC] Default proto transport in JSEP


Hi Adam,

On Wed, Nov 28, 2018 at 1:22 PM Adam Roach <adam@nostrum.com<mailto:adam@nostrum.com>> wrote:

On 11/28/18 10:57 AM, Roman Shpount wrote:
On Wed, Nov 28, 2018 at 11:38 AM Cullen Jennings <fluffy@iii.ca<mailto:fluffy@iii.ca>> wrote:
On Nov 27, 2018, at 4:46 PM, Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> wrote:

 I suggest to update JSEP section 5.1.2 to match the rest of the documents to say that "UDP/TLS/RTP/SAVPF" proto MUST be used during ICE restart. When ICE restart is not in progress, "UDP/TLS/RTP/SAVPF" proto MUST be used if default (only) candidate is a UDP candidate and "TCP/TLS/RTP/SAVPF" proto MUST be used if default (only) candidate is TCP candidate.

I don’t see any real befits to implementations to this change and I don’t think the rtcweb consensus was around the currently solution. Do you see some advantage to implementations to this?

This is what every other document related to ICE, including JSEP section 5.2.2 currently specifies. It was also consensus in MMUSIC. I think RTCWEB need a really good reason why it needs to be different.

It would probably help clarify things if you quoted the parts of the document that you think are in conflict. I can't find any explicit <proto> field handling in 5.2.2.

 I have mentioned this already in the previous message, but I guess this got lost in the traffic.

JSEP-25 in section 5.2.2 says (https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-25#section-5.2.2):

Each "m=" and c=" line MUST be filled in with the port, protocol, and address of the default candidate for the m= section, as described in [I-D.ietf-mmusic-ice-sip-sdp], Section 3.2.1.2.

At the same time section 5.1.2 says (https://tools..ietf.org/html/draft-ietf-rtcweb-jsep-25#section-5.1.2<https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-25#section-5.1.2>)2>):

For media m= sections, JSEP implementations MUST support the "UDP/TLS/RTP/SAVPF" profile specified in [RFC5764], and MUST indicate this profile for each media m= line they produce in an offer. For data m= sections, implementations MUST support the "UDP/DTLS/SCTP" profile and MUST indicate this profile for each data m= line they produce in an offer.

So, section 5.2.2 says m= line should be filled with currently used protocol, which means "TCP/TLS/RTP/SAVPF" or "TCP/DTLS/SCTP" if default candidate is TCP based, but section 5.1.2 says it must be "UDP/TLS/RTP/SAVPF" or "UDP/DTLS/SCTP", even if default candidate is TCP based. I thought that section 5.2.2, since it is more specific, overwrites 5.1.2, which I assumed only applies to ICE restart. Authors disagree and want to update the document.

In terms of changing technical aspects of JSEP: the only reason the document is out of the RFC Editor's queue right now is to address issues arising from rationalizing the reference to RFC 8445 within Cluster 238. This is not an opportunity to re-litigate previously settled consensus decisions. Technical issues such as the one at hand should have been raised during WG development, WG last call, or -- in extremis, since you're a regular RTCWEB participant -- during IETF last call. It's up to the chairs what to allow, but I wouldn't expect anything other than catastrophic flaws to be open for change at this time.

I am not the one who opened this can of worms. I am fine if the current draft version is not changed. This is why I did not comment during the WG last call. Draft authors are introducing the new change in https://github.com/rtcweb-wg/jsep/pull/857, which makes JSEP incompatible with ice-sip-sdp. I oppose this change. If the group considers that a change to clarify things is necessary, I would suggest that section 5.1.2 should be changed instead to that it only applies during ICE restart, so that JSEP is compatible with ice-sip-sdp.

Regards,
______________
Roman Shpount