Re: [MMUSIC] DTLS-over-SCTP, anyone?

Christian Groves <Christian.Groves@nteczone.com> Tue, 09 February 2016 01:57 UTC

Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4401B3F3E for <mmusic@ietfa.amsl.com>; Mon, 8 Feb 2016 17:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=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 Olh0bIdtlu1T for <mmusic@ietfa.amsl.com>; Mon, 8 Feb 2016 17:57:18 -0800 (PST)
Received: from msh03.myshophosting.com (msh03.myshophosting.com [101.0.109.158]) (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 E6F7A1B3F3D for <mmusic@ietf.org>; Mon, 8 Feb 2016 17:57:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nteczone.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=EHvFt/0eU2oaQiAZbKVxwFw2Oa2eR5wwEtalKrXDsgM=; b=car+owhy3eBtj4F+QEvFpJn07p IQXhi2UnItCtGMuqnyxirMCRnUjcvxRBBIhRM8qawf+iJMrr2cwx6P8psUHpvZ7Gt70brfdkz4qoG 8dRgJ/ysBYCQDZTg6k00lRJNl6tYbio7BArTeeqsPPv4mA5s6qJw5tiZlSQ+wXjy8V5RV8f6DLtsJ oyu/CfnCtMPI2uS7tR+UzVfYWeFGcBrKfo2+nzGtHTQMXvELjb0TlX2gY4K2nZitAT4n9TL5JBOkR Tw75KHDuYFlvgF9SC3riSi2gd80p+bv0YA3R5q0VckQbsg0OUXDMiMutuDGKe1BgAhd3ZMwJoiZmc UvllRBIQ==;
Received: from ppp118-209-127-77.lns20.mel4.internode.on.net ([118.209.127.77]:50315 helo=[192.168.1.22]) by msh03.myshophosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from <Christian.Groves@nteczone.com>) id 1aSxYG-001y6Y-Tg for mmusic@ietf.org; Tue, 09 Feb 2016 12:57:13 +1100
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B37DBF1AD@ESESSMB209.ericsson.se> <786615F3A85DF44AA2A76164A71FE1ACE19A359C@FR711WXCHMBA03.zeu.alcatel-lucent.com> <CAD5OKxtLn+g5fZtkbKoMqTCb-g25PSpcw5PLjOvWnNUayOn=sw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37DC39DB@ESESSMB209.ericsson.se>
From: Christian Groves <Christian.Groves@nteczone.com>
Message-ID: <56B94776.3090606@nteczone.com>
Date: Tue, 09 Feb 2016 12:57:10 +1100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37DC39DB@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - msh03.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: msh03.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Authenticated-Sender: msh03.myshophosting.com: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/KFfSCG7ueUS0HfdgvPxUOq06ELw>
Subject: Re: [MMUSIC] DTLS-over-SCTP, anyone?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 09 Feb 2016 01:57:20 -0000

Hello

I think the fact that the draft doesn't support DTLS-over-SCTP has been 
known for some time. No one has been pushing for its inclusion. I'd be 
happy if it was left out to be able to progress the draft.

Alternatively we can do what I think Albrecht is suggesting. Reserve 
proto values for DTLS/SCTP/IP and SCTP/UDP/IP in the draft and indicate 
their use by SDP should be defined in a future specification. I don't 
think its worth solving that problem now.

Regards, Christian

On 9/02/2016 7:45 AM, Christer Holmberg wrote:
>
> Hi,
>
> > The problem with DTLS-over-SCTP (RFC 6083) is that it is not fully 
> compatible with draft-ietf-mmusic-dtls-sdp.
>
> > In particular, RFC 6083 does not allow DTLS association span across 
> multiple SCTP associations, but
>
> > draft-ietf-mmusic-dtls-sdp allows to preserve DTLS association 
> through a transport change. The most likely
>
> > solution to this is updating RFC 6083, but, if no one is using 
> DTLS-over-SCTP, it would be easier just to say
>
> > that DTLS-over-SCTP is not supported.
>
> **If** we decide to keep DTLS-over-SCTP in the draft, my suggestion 
> would be to say that “DTLS preservation over transport change” does 
> not apply to DTLS-over-SCTP, with a reference to RFC 6083.
>
> Then, if someone at some point updates RFC 6083, the SCTP-SDP spec 
> also has to be updated.
>
> I do NOT want to delay draft-sctp-sdp until a possible RFC 6083 update 
> has been done (assuming people would agree to do it in the first place).
>
> Regards,
>
> Christer
>
> _____________
> Roman Shpount
>
> On Mon, Feb 8, 2016 at 10:12 AM, Schwarz, Albrecht (Nokia - DE) 
> <albrecht.schwarz@nokia.com <mailto:albrecht.schwarz@nokia.com>> wrote:
>
>     Hello Christer,
>
>     the titel of the (future) RFC will not exclude any SCTP transport
>     modes.
>
>     And a comprehensive and future safe protocol specification should
>     cover all existing ones, which is “DTLS/SCTP/IP” as well as
>     “SCTP/UDP/IP” (RFC 6951).
>
>     These two SCTP transport modes should be indicated as well,
>     independent of potential intentions to be used soon.
>
>     Codepoint space could be reserved, placeholder sections tagged as
>     “not yet supported” of “for further studies”, etc, but the worst
>     case would be any kind of interaction issues in future.
>
>     My view,
>
>     Albrecht
>
>     *From:*mmusic [mailto:mmusic-bounces@ietf.org
>     <mailto:mmusic-bounces@ietf.org>] *On Behalf Of *EXT Christer Holmberg
>     *Sent:* Montag, 8. Februar 2016 15:33
>     *To:* mmusic <mmusic@ietf.org <mailto:mmusic@ietf.org>>
>     *Subject:* [MMUSIC] DTLS-over-SCTP, anyone?
>
>     Hi,
>
>     draft-ietf-mmusic-sctp-sdp currently defines the SDP O/A
>     procedures for SCTP, SCTP-over-DTLS, and DTLS-over-SCTP.
>
>     As we know, SCTP-over-DTLS is used for the WebRTC data channel.
>
>     My question is: does anyone intend to use DTLS-over-SCTP?
>
>     Regards,
>
>     Christer
>
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic