[tsvwg] Call for feedback after IETF-113: Should draft-ietf-tsvwg-dtls-over-sctp-bis obsolete RFC 6083?
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sat, 23 April 2022 07:25 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
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 49B023A11C5; Sat, 23 Apr 2022 00:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 HggLiR1MVzTl; Sat, 23 Apr 2022 00:25:39 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC043A11C3; Sat, 23 Apr 2022 00:25:38 -0700 (PDT)
Received: from [192.168.1.64] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 2CFA31B001D2; Sat, 23 Apr 2022 08:25:26 +0100 (BST)
Content-Type: multipart/alternative; boundary="------------O2bzOaUskQVx0Xutuh4Z03ys"
Message-ID: <2df510e2-bde3-893e-bb91-f8534c097261@erg.abdn.ac.uk>
Date: Sat, 23 Apr 2022 08:25:25 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/aeZHpw9DCv3c3Cem4h8eZwgWQkE>
Subject: [tsvwg] Call for feedback after IETF-113: Should draft-ietf-tsvwg-dtls-over-sctp-bis obsolete RFC 6083?
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: Sat, 23 Apr 2022 07:25:48 -0000
The TSVWG meeting session at IETF-113 discussed whether we should make a change to the currently adopted work item on DTLS for SCTP so that it will not update RFC 6083. We now need to confirm what would be acceptable by this WG. The meeting noted that this will result in two alternative DTLS Specs for SCTP. The IETF will need to do security maintenance of any security-related IETF protocol, which implies that if RFC 6093 remains active, it will, itself, need to be updated at some point in the future. This email is to seek an acceptable plan to take this forward, suggestions are: (a) Continue with the current plan that DOES replace RFC 6083 with draft-ietf-tsvwg-dtls-over-sctp-bis. <https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-dtls-over-sctp-bis> Open source has been important in the past, and some thought that the associated IPR would likely not result in an open source replacement. (b) Modify the work item to publish draft-ietf-tsvwg-dtls-over-sctp-bis <https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-dtls-over-sctp-bis> as a PS that does NOT obsolete RFC 6083. This would postpone any decision about whether to obsolete RFC 6083 and allows a different update for RFC6083. This also requires that draft-ietf-tsvwg-dtls-over-sctp-bis <https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-dtls-over-sctp-bis> includes consideration of how the two altenative specs can co-exist. (c) A different proposal - presently the chairs are not aware of other proposals from those who implement and use SCTP. Please send thoughts or isssues in an email to the TSVWG list to help the chairs decide on this topic by 6th May 2022. Best wishes, Gorry TSVWG Co-Chair.
- [tsvwg] Call for feedback after IETF-113: Should … Gorry Fairhurst
- Re: [tsvwg] Call for feedback after IETF-113: Sho… tuexen
- Re: [tsvwg] Call for feedback after IETF-113: Sho… Magnus Westerlund
- Re: [tsvwg] Call for feedback after IETF-113: Sho… tuexen
- [tsvwg] Feedback after IETF-113: Should draft-iet… Gorry Fairhurst