[tsvwg] SSL connections with SCTP
Elmar Stellnberger <estellnb@elstel.org> Wed, 08 May 2019 15:03 UTC
Return-Path: <estellnb@elstel.org>
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 096F8120123 for <tsvwg@ietfa.amsl.com>; Wed, 8 May 2019 08:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level:
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=elstel.org
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 bIC7uL8bHYSi for <tsvwg@ietfa.amsl.com>; Wed, 8 May 2019 08:03:39 -0700 (PDT)
Received: from mailout2.dotplex.com (mailout2.dotplex.com [IPv6:2a0c:5f00:1:114::]) (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 3E2DD12012B for <tsvwg@ietf.org>; Wed, 8 May 2019 08:03:26 -0700 (PDT)
Received: from remote.ip.hidden (remote.ip.hidden [127.0.0.1]) (Authenticated sender: estellnb@elstel.org) by mailout.dotplex.com (Postfix) with ESMTPSA id 88EFA20803 for <tsvwg@ietf.org>; Wed, 8 May 2019 17:03:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elstel.org; s=dotplex190506; t=1557327803; bh=u4wce8jw8aep7AZHTTCjLdHE0IH4rvjmIzr/PlnudqA=; h=To:From:Subject:Date:From; b=axxb9XftsodW3bcR88tcXOj3vYiHMwplX75GWJYV5pDSI6h5XSmxO4iLT8pzM7KCU GYqRtTWe6av1emWJxDv0MP2UBPk0VjtHaMafl/5VjKDiDTjEgDTr3Pk8AtvBbX6Jen U05uOXLxm15uwPHEGQ4QaHgjxvbsFSiZsVxKrhCW8pk7Msh0rdeUZv7mXslrA9Noqy R4zyXNynf6+FuNXI82r819fXJnG1rQt63HtN0Cx6zsgFkfjpVC6X6yqea6eI9jVJVA DRt+hlt9BzpFG/tQjOR+AcqWw76gNoKL3u7PRlVKvqMPF+M1d5qXx5/2oXrAke+3BD vN+2w6+niFjvQ==
To: tsvwg@ietf.org
From: Elmar Stellnberger <estellnb@elstel.org>
Message-ID: <1d70503b-62cd-fe9a-118f-4ea36f148d1e@elstel.org>
Date: Wed, 08 May 2019 17:03:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/rg7PBbvQWHtz4aiyN3ofFS-fz0A>
X-Mailman-Approved-At: Wed, 08 May 2019 12:54:57 -0700
Subject: [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 15:05:17 -0000
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?
- [tsvwg] SSL connections with SCTP Elmar Stellnberger
- Re: [tsvwg] SSL connections with SCTP Michael Tuexen
- Re: [tsvwg] SSL connections with SCTP Caitlin Bestler