Re: [tsvwg] Call for feedback after IETF-113: Should draft-ietf-tsvwg-dtls-over-sctp-bis obsolete RFC 6083?
tuexen@fh-muenster.de Wed, 04 May 2022 22:31 UTC
Return-Path: <tuexen@fh-muenster.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 D3EEDC14F735; Wed, 4 May 2022 15:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level:
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.069, T_SPF_PERMERROR=0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKRTc0g0qW6M; Wed, 4 May 2022 15:31:08 -0700 (PDT)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A03F8C14F743; Wed, 4 May 2022 15:31:07 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:690e:f705:468b:f524]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 98202721E2825; Thu, 5 May 2022 00:30:52 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_B808AAB8-701F-41E9-A462-41134BBDF07D"; protocol="application/pkcs7-signature"; micalg="sha-256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: tuexen@fh-muenster.de
In-Reply-To: <PA4PR07MB8414BF9B0447020B8585F36D95C39@PA4PR07MB8414.eurprd07.prod.outlook.com>
Date: Thu, 05 May 2022 00:30:50 +0200
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAB9E31C-E16F-4695-8741-2E5696281319@fh-muenster.de>
References: <2df510e2-bde3-893e-bb91-f8534c097261@erg.abdn.ac.uk> <42F31C5B-6144-42BA-9E87-3CFB742F7B71@fh-muenster.de> <PA4PR07MB8414BF9B0447020B8585F36D95C39@PA4PR07MB8414.eurprd07.prod.outlook.com>
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ctdfjVftolUN8rDs00gmoRXmw6w>
Subject: Re: [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.34
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, 04 May 2022 22:31:10 -0000
> On 4. May 2022, at 10:08, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org> wrote: > > > >>> >>> (b) Modify the work item to publish 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 > includes >> consideration of how the two altenative specs can co-exist. > >> If it makes sense or not to spend the resources depends on whether it is >> possible >> to work around the IPRs or not. This can't be decided before the IPRs have >> been >> published. But I guess the authors of draft-ietf-tsvwg-dtls-over-sctp-bis > are >> not >> willing to wait for that to happen before the document progresses. > > No, we don't see waiting is particular productive. The first IPR will be 18 > month by the end of June. However, the second one will not be 18 month until > somewhere in Q1 next year. From my perspective I think it is better to > continue towards publication of draft-ietf-tsvwg-dtls-over-sctp-bis and the > question of obsoleting or not will need to be settled prior to the WG last > call. Hopefully that would be coming up rather soon as we hope to solved all > issues with the next version. Hi Magnus, thanks for the clarification. So I learned is that the new process of doing (at least) SCTP work in TSVWG is: 1. Have an idea how to solve a relevant problem. 2. File an IPR covering the solution. 3. Publish some revisions of an individual IDs describing the solution. 4. Get your individual ID adopted as a WG document without declaring your IPR. 5. Publish some revisions of the ID as a WG document. 6. Declare your IPR. 7. Publish some more revisions of the ID as a WG document. 8. Possibly file more IPRs and declare them. 9. Do a WGLC and expect that to go through without providing information what all of the IPRs are about. Is that correct? Best regards Michael > > Cheers > > Magnus Westerlund
- [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