Last Call Review of draft-ietf-rum-rue-09
review-ietf-rum-rue-09-artart-lc-salz-2021-11-10-00
| Request | Review of | draft-ietf-rum-rue |
|---|---|---|
| Requested revision | No specific revision (document currently at 11) | |
| Type | Last Call Review | |
| Team | ART Area Review Team (artart) | |
| Deadline | 2021-11-12 | |
| Requested | 2021-10-12 | |
| Authors | Brian Rosen | |
| I-D last updated | 2021-11-10 | |
| Completed reviews |
Artart Last Call review of -09
by Rich Salz
(diff)
Genart Last Call review of -09 by Matt Joras (diff) Secdir Last Call review of -09 by Russ Mundy (diff) Tsvart Telechat review of -09 by Dr. Bernard D. Aboba (diff) |
|
| Assignment | Reviewer | Rich Salz |
| State | Completed | |
| Request | Last Call review on draft-ietf-rum-rue by ART Area Review Team Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/art/FAnGx_MrrlJVdU8WxbGG_BOFVe8 | |
| Reviewed revision | 09 (document currently at 11) | |
| Result | Ready | |
| Completed | 2021-11-10 |
review-ietf-rum-rue-09-artart-lc-salz-2021-11-10-00
I am the requested ARTART reviewer for this document. My primary knowledge of SIP comes from hoping and waiting for STIR/SHAKEN to be adopted. It really needs SIP experts to do a close review. I read the document. It is like a conformance document, full of normative language about which RFC's MUST be implemented, and which parameters in them SHOULD have specific values. I cannot comment on whether the sum total of all requirements makes sense or not. The document is well-written. The problem space is well-described. Each individual obligation (MUST MAY SHOULD etc) is in enough detail to make it understandable.