Last Call Review of draft-ietf-sipcore-multiple-reasons-01
review-ietf-sipcore-multiple-reasons-01-artart-lc-herr-2022-10-04-00
| Request | Review of | draft-ietf-sipcore-multiple-reasons |
|---|---|---|
| Requested revision | No specific revision (document currently at 01) | |
| Type | Last Call Review | |
| Team | ART Area Review Team (artart) | |
| Deadline | 2022-10-10 | |
| Requested | 2022-09-26 | |
| Authors | Robert Sparks | |
| I-D last updated | 2022-10-04 | |
| Completed reviews |
Opsdir Last Call review of -01
by Tianran Zhou
Secdir Last Call review of -01 by Joseph A. Salowey Artart Last Call review of -01 by Todd Herr |
|
| Assignment | Reviewer | Todd Herr |
| State | Completed | |
| Request | Last Call review on draft-ietf-sipcore-multiple-reasons by ART Area Review Team Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/art/xWxjwYuVtcneeQLPy3UGWTULfyE | |
| Reviewed revision | 01 | |
| Result | Ready w/nits | |
| Completed | 2022-10-04 |
review-ietf-sipcore-multiple-reasons-01-artart-lc-herr-2022-10-04-00
As someone unfamiliar with SIP Reason Header Fields, I'm of the opinion that perhaps an example of a header field with multiple values might be instructive as a contrast to the examples shown in RFC 3326, but I do not feel strongly enough about this to hold up the document.