[core] Mail regarding draft-ietf-ace-key-groupcomm

Jim Schaad <ietf@augustcellars.com> Thu, 04 April 2019 01:42 UTC

From: Jim Schaad <ietf@augustcellars.com>
To: draft-ietf-ace-key-groupcomm@ietf.org
CC: core@ietf.org
Date: Wed, 03 Apr 2019 18:42:31 -0700
Message-ID: <003201d4ea87$acb73780$0625a680$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Language: en-us
Thread-Index: AdTqhNNyNWeMmgN+Rsq71GPkqAXXZA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/QRQ5uwdi4BVCyQiviE_cmmdseJk>
Subject: [core] Mail regarding draft-ietf-ace-key-groupcomm
Precedence: list

Some additional things that need to be thought about.

1.  Someplace as part of the re-key discussions there ought to be some
commentary on the wisdom of rate limiting the frequency of doing re-keying
operations.

2. I think that there should be an optional parameter that says "If this
much time has elapsed since the last time you checked, see if the group id
has changed."  This would be combined with a polling client to ensure that
they check for an updated key context before doing some operation.

3.  What happens in the following situations:
a) The key context is changed between a request being sent and the server
receiving the request.  This could just be because the sender did not get
the notification of the key context changing.

b) The response takes "a while" to generate and the key context is changed
after the request is received, but before the response is sent.

c)  The key context is changed in the middle of a block-wise transfer.

Jim

[core] Mail regarding draft-ietf-ace-key-groupcomm Jim Schaad