Mercurial > hg > ietf
annotate ace-key-groupcomm-review.txt @ 4:a88cd2ff0a89
done through section 9
author | Henry S. Thompson <ht@inf.ed.ac.uk> |
---|---|
date | Fri, 27 Oct 2023 15:31:55 +0100 |
parents | 11c0afd7bad2 |
children | b281db304428 |
rev | line source |
---|---|
1 | 1 Document: |
2 Intended RFC status: Proposed Standard | |
3 Review type: artart - Last Call review | |
4 Reviewer: Henry S. Thompson | |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
5 Review Date: 2023-10-@@ |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
6 Result: Ready with Issues |
1 | 7 |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
8 *Summary* |
1 | 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 | |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
14 *Substantive points* |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
15 |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
16 Section 2. I'm seeing an inconsistency in the way the Dispatcher is |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
17 discussed. When introduced in the bullet points the last bullet says |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
18 |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
19 "If it consists of an explicit entity such as a pub-sub Broker or a |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
20 message relayer, the Dispatcher is comparable to an _untrusted_ |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
21 on-path intermediary, and as such it is _able to read_ the messages |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
22 sent by Clients in the group." [emphasis added] |
1 | 23 |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
24 But at the end of section 2 we find |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
25 |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
26 "5. The joining node can communicate _securely_ with the other group |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
27 members, using the keying material provided in step 3." |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
28 [emphasis added] |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
29 |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
30 If the Dispatcher is untrusted, how can communication be secure? |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
31 There is no discussion of the Dispatcher in the Security section. |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
32 |
4 | 33 Section 5: I don't see how authority to institute forced deletion is |
34 established. Indeed the means for forced deletion don't appear to be | |
35 defined at all. Section 4.8 (and 4.8.3) explicitly requires that only | |
36 the Client can send a Delete request, and only for themselves. | |
37 | |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
38 *Minor points* |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
39 |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
40 Section 1. I note that one of the two referenced examples of candidate |
1 | 41 application profiles, "A publish-subscribe architecture for the |
42 Constrained Application Protocol (CoAP)" [1], has expired. I'm not | |
43 sure how much it matters to have reasonably mature examples, but | |
44 without _some_ good reasons to suppose that there's a community out | |
45 there waiting to implement this framework, its future does seem a bit | |
46 shaky... There is of course a chicken-and-egg problem here which may | |
47 explain the lack of progress. | |
48 | |
49 Section 2. This is the first point where the actual connection between | |
50 ACE and this document is made clear, that is, that the KDC is the | |
51 Resource Server _per ACE_. Simply adding ", per ACE," to "Resource | |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
52 Server" in para 2 of Section 1 would fix this for me. |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
53 |
4 | 54 Section 6: It might be helpful to include ASCII-art diagrams of the |
55 different communication pathways described for accomplishing rekeying. | |
56 | |
57 Sections 3.1 & 7: The example scopes include Verifier and Monitor | |
58 roles. Although there is a parenthetical reference to the [Vv]erifier | |
59 role in Section 3.3.1, no other mention of Monitor is given, and in | |
60 general the role of roles is not explained anywhere. There is a | |
61 "Request inconsistent with the current roles" error code defined in | |
62 section 9, but no tabulation of roles allowed/required for particular | |
63 requests, which one might expect. | |
64 | |
65 If all this is something defined in one of the many referenced specs, | |
66 and so familiar to likely readers, that's OK, otherwise perhaps | |
67 something should be added. | |
68 | |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
69 *Nits* |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
70 |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
71 Section 1 / Appendix A: The use of REQ[n] and OPT[n] in conjunction |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
72 with REQUIRED and MAY is not explained, nor are they linked to the |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
73 relevant text in Appendix A. There is an oblique reference to this |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
74 practice in para. 4 of Section 1, which could stand to be expanded to |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
75 explain your conventions. |
1 | 76 |
3
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
77 Passim: Please do a thorough spell-check. The following were found in the |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
78 first 4 sections: |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
79 recommeded -> recommended |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
80 memebrs -> members |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
81 specificaton -> specification |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
82 acces -> access |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
83 trasferring -> transferring |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
84 |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
85 ht |
11c0afd7bad2
trying to get into Section 3
Henry S. Thompson <ht@inf.ed.ac.uk>
parents:
1
diff
changeset
|
86 -- |
1 | 87 |
88 [1] https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-pubsub-12 |