IETF Logo Mail Archive

Re: [MMUSIC] Do we really need TCP/DTLS/SCTP proto field?

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 16 February 2017 16:56 UTC

Return-Path: <christer.holmberg@ericsson.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 472D11295D9 for <mmusic@ietfa.amsl.com>; Thu, 16 Feb 2017 08:56:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 EqxlkWXO2POg for <mmusic@ietfa.amsl.com>; Thu, 16 Feb 2017 08:55:58 -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 58CDF1294FF for <mmusic@ietf.org>; Thu, 16 Feb 2017 08:55:58 -0800 (PST)
X-AuditID: c1b4fb25-55bff70000001738-b6-58a5d99a4a47
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by (Symantec Mail Security) with SMTP id 6A.62.05944.A99D5A85; Thu, 16 Feb 2017 17:55:56 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Thu, 16 Feb 2017 17:55:54 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [MMUSIC] Do we really need TCP/DTLS/SCTP proto field?
Thread-Index: AQHSiGuZ0ghkIgIFz0iRXtxKyN1pOqFrt7kAgAAhoiA=
Date: Thu, 16 Feb 2017 16:55:53 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4C004589@ESESSMB209.ericsson.se>
References: <CABcZeBOK0T5WbMLi=AS3WOAjDt_D8e8JSTp2czSYdhHv8Xcgtw@mail.gmail.com> <118E7032-775C-46D6-A76A-6DB6EA515528@nostrum.com>
In-Reply-To: <118E7032-775C-46D6-A76A-6DB6EA515528@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4C004589ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDIsWRmVeSWpSXmKPExsUyM2J7oO6cm0sjDM6t1raY33ma3WLF63Ps FlOXP2ZxYPZYsuQnk8esnU9YPCY/bmMOYI7isklJzcksSy3St0vgymj9PYO5YFVCxcsbv1gb GG/EdjFyckgImEgc/refpYuRi0NIYB2jxOad51lBEkICixklZs1w7WLk4GATsJDo/qcNEhYR cJCY9P0CWAmzgLzEhSVrmEBsYQEniTfvr7JC1DhLnLvRxAhhW0k0zbrJAmKzCKhKzFj7BSzO K+ArcWfSGSaIVa2MEj1/OEBsTgF7iXsbf7GD2IwCYhLfT0HMZxYQl7j1ZD4TxM0CEkv2nGeG sEUlXj7+xwphK0k0LnkCdVu+xNyzk9kgdglKnJz5hGUCo8gsJKNmISmbhaRsFtDHzAKaEut3 6UOUKEpM6X7IDmFrSLTOmcuOLL6AkX0Vo2hxanFSbrqRsV5qUWZycXF+nl5easkmRmCcHdzy W3UH4+U3jocYBTgYlXh4C/YtjRBiTSwrrsw9xCjBwawkwrv6KlCINyWxsiq1KD++qDQntfgQ ozQHi5I4r9nK++FCAumJJanZqakFqUUwWSYOTqkGRnGu7UsFb1395f71ls8UHZ16gbf++dWO rM6qc+rcGF/+/HjbRbREe3mL/84v35U66zbMzxfYacIf0+s4neVzYPQX5vcSRwIE9vr/+7Dy 8C3lvUW33Zv2ZV1rT8vfU7Ml4keiy7zT9+/apf2ULsicuVjnom78yr5Yq3jfRXyS4mHnS/jf Ve1vUWIpzkg01GIuKk4EAOzEcU6vAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xiBdNx3zIzRQjGBENY0DIy7t-D0>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Do we really need TCP/DTLS/SCTP proto field?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 16 Feb 2017 16:56:00 -0000

Hi,

My suggestion is to keep the TCP/DTLS/SCTP definition.

We earlier made a choice to restrict the scope of the document (by removing plain SCTP and DTLS-over-SCTP proto values), and I think we should keep the current scope.

Regards,

Christer


From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Ben Campbell
Sent: 16 February 2017 17:52
To: Eric Rescorla <ekr@rtfm.com>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Do we really need TCP/DTLS/SCTP proto field?


Process background: draft-ietf-mmusic-sctp-sdp was on today's IESG telechat. The draft is approved for publication, but with a point raised to ask the WG resolve Ekr's question.

Thanks!

Ben.

On 16 Feb 2017, at 9:43, Eric Rescorla wrote:
I raised this with the authors, but maybe it is worth asking the mailing list.

It seems like we are trending towards a world where we just ignore the transport
component of the proto field and let ICE work things out. In that vein, I wonder
do we really need to register/define TCP/DTLS/SCTP. It's only really useful if
we think people will do SCTP over DTLS with TCP without ICE. Is that actually
likely. I note that per previous discussions, JSEP already requires that you use
UDP/DTLS/SCTP all the time: http://rtcweb-wg.github.io/jsep/#rfc.section.5.1.2

-Ekr

v2.23.0 | Report a Bug | By Email