Mercurial > hg > ietf
comparison ace-key-groupcomm-review.txt @ 1:92618ff70952
getting started
| author | Henry S. Thompson <ht@inf.ed.ac.uk> |
|---|---|
| date | Fri, 20 Oct 2023 14:43:57 +0100 |
| parents | |
| children | 11c0afd7bad2 |
comparison
equal
deleted
inserted
replaced
| 0:0d405ad6709c | 1:92618ff70952 |
|---|---|
| 1 Document: | |
| 2 Intended RFC status: Proposed Standard | |
| 3 Review type: artart - Last Call review | |
| 4 Reviewer: Henry S. Thompson | |
| 5 Review Date: | |
| 6 IETF Last Call Date: | |
| 7 | |
| 8 Summary: | |
| 9 | |
| 10 Caveat: I'm not familiar with the group comms family of RFCs or the | |
| 11 applications they support, so this review is from an outsider's | |
| 12 perspective. | |
| 13 | |
| 14 Minor points | |
| 15 | |
| 16 Section @. I note that one of the two referenced examples of candidate | |
| 17 application profiles, "A publish-subscribe architecture for the | |
| 18 Constrained Application Protocol (CoAP)" [1], has expired. I'm not | |
| 19 sure how much it matters to have reasonably mature examples, but | |
| 20 without _some_ good reasons to suppose that there's a community out | |
| 21 there waiting to implement this framework, its future does seem a bit | |
| 22 shaky... There is of course a chicken-and-egg problem here which may | |
| 23 explain the lack of progress. | |
| 24 | |
| 25 Section 2. This is the first point where the actual connection between | |
| 26 ACE and this document is made clear, that is, that the KDC is the | |
| 27 Resource Server _per ACE_. Simply adding ", per ACE," to "Resource | |
| 28 Server" in para 2 of Section 1 would do the trick. | |
| 29 | |
| 30 Nits | |
| 31 | |
| 32 [1] https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-pubsub-12 |