[Congress] CoAP congestion control method "favor" on next CoRE interim

Carsten Bormann <cabo@tzi.org> Mon, 05 June 2023 09:33 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: congress@ietfa.amsl.com
Delivered-To: congress@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D095FC14F736; Mon, 5 Jun 2023 02:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 yka2jaeVq0Ch; Mon, 5 Jun 2023 02:33:12 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 263CCC14E515; Mon, 5 Jun 2023 02:33:06 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4QZT1C6KZZzDCf0; Mon, 5 Jun 2023 11:33:03 +0200 (CEST)
Content-Type: multipart/mixed; boundary="Apple-Mail=_820BE791-3092-4CE6-8325-4B97A3E2EDD3"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 05 Jun 2023 11:33:03 +0200
Cc: congress@ietf.org
X-Mao-Original-Outgoing-Id: 707650383.446312-2e8c76bd302be35ee78996321c98cbf8
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFD574D7-4A7E-4CF5-978E-B09A60084762@tzi.org>
To: ccwg@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/congress/LBfIT0cyAkUGc5vYnyCl5lfGmq4>
Subject: [Congress] CoAP congestion control method "favor" on next CoRE interim
X-BeenThere: congress@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussions about the CONGestion RESponse and Signaling \(CONGRESS\) Working Group" <congress.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/congress>, <mailto:congress-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/congress/>
List-Post: <mailto:congress@ietf.org>
List-Help: <mailto:congress-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/congress>, <mailto:congress-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2023 09:33:15 -0000

I would like to point out that the CoRE WG is likely to resume work on the congestion control (and RTO determination) mechanism for the CoAP protocol called “FASOR” (Fast-Slow Retransmission Timeout and Congestion Control).

This will be discussed in this Wednesday’s CoRE interim.
I’m not requesting any specific help at this point, but if this interests you, the coordinates are below.
We are planning to do the FASOR update at the start of the meeting (~ 14:05Z).

Grüße, Carsten

https://datatracker.ietf.org/doc/draft-ietf-core-fasor/
https://datatracker.ietf.org/doc/html/draft-ietf-core-fasor-02

core - Constrained RESTful Environments
Scheduled: 2023-06-07 at 16:00 to 17:30 CEST (Wednesday 2023-06-07 14:00Z)
Remote instructions: https://meetings.conf.meetecho.com/interim/?short=83412f0c-9648-4311-bec9-12d11cd4d860

https://datatracker.ietf.org/meeting/interim-2023-core-09/session/core
https://www.timeanddate.com/worldclock/fixedtime.html?msg=CoRE+interim&iso=20230607T14&ah=1&am=30