[Ace] Congestion control needs to be included

Jim Schaad <ietf@augustcellars.com> Mon, 23 March 2020 17:36 UTC

From: Jim Schaad <ietf@augustcellars.com>
To: draft-ietf-ace-key-groupcomm@ietf.org
CC: ace@ietf.org
Date: Mon, 23 Mar 2020 10:36:33 -0700
Message-ID: <042301d60139$9a0f0e90$ce2d2bb0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Language: en-us
Thread-Index: AdYBODic7LV0QZU9TTW5mgUvtZ9eWA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/0YwfcQ6DEjtwdblMKPeMzCsJzZk>
Subject: [Ace] Congestion control needs to be included
Precedence: list

I had a weird weekend trying to get coverage testing up for my Observe
implementation and in the process found out that it had not implemented the
required congestion control.  As part of this I had to go back and do a
careful read of RFC 7641 to get things right in my code and following that I
thought that this document really needs to have a discussion of congestion
control as well.  Part of this can be a reference to section 4.5.1 of RFC
7641 where we are using observe but we need to go through the document and
potentially look at some other places where we need to discuss congestion as
well.

I will also note that observe does not guarantee that all messages will be
sent to a client, just that after a while it will have the most current
version of the content.  This means that there is a high probability that
clients will not get every update of key material if turn over is being done
at all quickly.

Jim

[Ace] Congestion control needs to be included Jim Schaad