Re: [tsvwg] SSL connections with SCTP

Michael Tuexen <michael.tuexen@lurchi.franken.de> Wed, 08 May 2019 20:19 UTC

Return-Path: <michael.tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 891C01200CE for <tsvwg@ietfa.amsl.com>; Wed, 8 May 2019 13:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=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 Ky8HdTUrr4c3 for <tsvwg@ietfa.amsl.com>; Wed, 8 May 2019 13:19:22 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8226012004B for <tsvwg@ietf.org>; Wed, 8 May 2019 13:19:21 -0700 (PDT)
Received: from [IPv6:2003:cd:6f38:4a00:c9a9:efbf:2cfd:8c0a] (p200300CD6F384A00C9A9EFBF2CFD8C0A.dip0.t-ipconnect.de [IPv6:2003:cd:6f38:4a00:c9a9:efbf:2cfd:8c0a]) (Authenticated sender: lurchi) by drew.franken.de (Postfix) with ESMTPSA id EAD2B721E280D; Wed, 8 May 2019 22:19:17 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <1d70503b-62cd-fe9a-118f-4ea36f148d1e@elstel.org>
Date: Wed, 08 May 2019 22:19:15 +0200
Cc: tsvwg <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA242CAC-05C7-4317-A15A-F95983F96192@lurchi.franken.de>
References: <1d70503b-62cd-fe9a-118f-4ea36f148d1e@elstel.org>
To: Elmar Stellnberger <estellnb@elstel.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ZYVXFSSnBhYEkATXuo0X7XQ7a2I>
Subject: Re: [tsvwg] SSL connections with SCTP
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 20:19:26 -0000

> On 8. May 2019, at 17:03, Elmar Stellnberger <estellnb@elstel.org> wrote:
> 
> I am planning to write a proxy for localhost which relays incoming tcp connections via an SCTP connection to a remote host. That way it should be possible to overcome lacking SCTP support for browsers. Now my question is how to best use SSL with SCTP. If I have established an open  SSL SCTP connection and want to fork a new flow for the same connection do I have to repeat the SSL cipher negotiation or may I simply fork an existing SSL SCTP flow?
> 
I would suggest to use DTLS/SCTP. This is supported by OpenSSL and you can
find some examples at https://github.com/nplab/DTLS-Examples.

Best regards
Michael