Last Call Review of draft-ietf-privacypass-architecture-13
review-ietf-privacypass-architecture-13-genart-lc-shirazipour-2023-06-26-00
| Request | Review of | draft-ietf-privacypass-architecture |
|---|---|---|
| Requested revision | No specific revision (document currently at 16) | |
| Type | IETF Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2023-07-03 | |
| Requested | 2023-06-19 | |
| Authors | Alex Davidson , Jana Iyengar , Christopher A. Wood | |
| I-D last updated | 2024-06-13 (Latest revision 2023-09-25) | |
| Completed reviews |
Artart Telechat review of -15
by Russ Housley
(diff)
Secdir IETF Last Call review of -13 by Ned Smith (diff) Artart IETF Last Call review of -13 by Russ Housley (diff) Genart IETF Last Call review of -13 by Meral Shirazipour (diff) |
|
| Assignment | Reviewer | Meral Shirazipour |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-privacypass-architecture by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/CqgR-suCZMWF5qvJsUFdPu89cak | |
| Reviewed revision | 13 (document currently at 16) | |
| Result | Ready w/nits | |
| Completed | 2023-06-26 |
review-ietf-privacypass-architecture-13-genart-lc-shirazipour-2023-06-26-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-privacypass-architecture-?? Reviewer: Meral Shirazipour Review Date: 2023-06-26 IETF LC End Date: 2023-07-03 IESG Telechat date: Not scheduled for a telechat Summary:This draft is almost ready to be published as informational RFC, no other comments than those on the list. Major issues: Minor issues: Nits/editorial comments: Concept of Issuer, Origin, Client, and Attester. Any requirement which should be from the same/different organization? 4.2 to 4.4 cover examples but an explanation at the the beginning of the document with example organization would really help with readability. -[Page 4] "etc;"-->"etc.," -[Page 6] section 3.2 "the vailidity"-->"the validity" -[Page 6] "the vailidity"-->"the validity " -[Page 25] "Appliations should "-->"Applications should "? "discused in Section 4 "-->"discussed in Section 4 "