Skip to main content

Telechat Review of draft-ietf-taps-interface-22
review-ietf-taps-interface-22-secdir-telechat-turner-2023-10-10-00

Request Review of draft-ietf-taps-interface
Requested revision No specific revision (document currently at 26)
Type Telechat Review
Team Security Area Directorate (secdir)
Deadline 2023-09-05
Requested 2023-08-16
Authors Brian Trammell , Michael Welzl , Reese Enghardt , Gorry Fairhurst , Mirja K├╝hlewind , Colin Perkins , Philipp S. Tiesel , Tommy Pauly
I-D last updated 2023-10-10
Completed reviews Secdir Telechat review of -22 by Sean Turner (diff)
Dnsdir Telechat review of -22 by Matt Brown (diff)
Intdir Telechat review of -22 by Tatuya Jinmei (diff)
Secdir Early review of -13 by Sean Turner (diff)
Artart Early review of -13 by Robert Sparks (diff)
Artart Last Call review of -20 by Robert Sparks (diff)
Genart Last Call review of -20 by Thomas Fossati (diff)
Secdir Last Call review of -20 by Sean Turner (diff)
Assignment Reviewer Sean Turner
State Completed
Request Telechat review on draft-ietf-taps-interface by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/gjWAZuQfttVkVWE_zYxoxfvL6ro
Reviewed revision 22 (document currently at 26)
Result Ready
Completed 2023-10-10
review-ietf-taps-interface-22-secdir-telechat-turner-2023-10-10-00
Hi! I've reviewed this I-D a couple of times along the way. This time I just
looked at the diffs between -20 and -22.

tl;dr: It's ready.

The security related changes this time around were pretty minor:

1. Downgrading TLS to informative. Sounds inflammatory doesn't it, but it's not
;) Something has to be implemented under the API, but it doesn't have to be TLS.

2. Dropped zeroRttMsgMaxLen read-only property. Turns out it wasn't used and
didn't offer much utility anyway:
https://github.com/ietf-tapswg/api-drafts/pull/1173