# HG changeset patch
# User Henry S. Thompson <ht@inf.ed.ac.uk>
# Date 1697809437 -3600
# Node ID 92618ff7095286d6cfd2fd3434e342d78ac498c5
# Parent  0d405ad6709c0d3fc09cfa456cf8a22e983780af
getting started

diff -r 0d405ad6709c -r 92618ff70952 ace-key-groupcomm-review.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ace-key-groupcomm-review.txt	Fri Oct 20 14:43:57 2023 +0100
@@ -0,0 +1,32 @@
+Document: 
+Intended RFC status: Proposed Standard
+Review type: artart - Last Call review
+Reviewer: Henry S. Thompson
+Review Date: 
+IETF Last Call Date: 
+
+Summary: 
+
+Caveat: I'm not familiar with the group comms family of RFCs or the
+applications they support, so this review is from an outsider's
+perspective.
+
+Minor points
+
+Section @. I note that one of the two referenced examples of candidate
+application profiles, "A publish-subscribe architecture for the
+Constrained Application Protocol (CoAP)" [1], has expired.  I'm not
+sure how much it matters to have reasonably mature examples, but
+without _some_ good reasons to suppose that there's a community out
+there waiting to implement this framework, its future does seem a bit
+shaky...  There is of course a chicken-and-egg problem here which may
+explain the lack of progress.
+
+Section 2. This is the first point where the actual connection between
+ACE and this document is made clear, that is, that the KDC is the
+Resource Server _per ACE_.  Simply adding ", per ACE," to "Resource
+Server" in para 2 of Section 1 would do the trick.
+
+Nits
+
+[1] https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-pubsub-12