Thanks, Aaron! I've just done an editorial pass on the document now that we believe it is technically complete.
Some of the nits addressed: - Remove redundancy between intro and abstract - Update language on Security Features to have a consistent tense/voice between definitions of features - Refer to QUIC as a name, not an acronym - Update all TLS 1.3 references to the RFC number - Don't have any empty section headers - Remove incorrect normative "SHOULD" from information doc Commits can be found here: https://github.com/ietf-tapswg/draft-ietf-taps-transport-security/commits/master In my opinion, once we've incorporated the PR from Aaron, we should be good. If anyone has other nits or comments, though, please file an issue or PR! Thanks, Tommy > On Apr 25, 2019, at 9:57 AM, Aaron Falk <[email protected]> wrote: > > Reminder that the working group last call for this draft ends next Monday. > Please send comments and opinions on whether the doc is ready to publish to > this list. > > https://tools.ietf.org/html/draft-ietf-taps-transport-security-06 > <https://tools.ietf.org/html/draft-ietf-taps-transport-security-06> > --aaron > > On 10 Apr 2019, at 10:12, Aaron Falk wrote: > > Dear TAPS working group, > > It’s time to perform a last call review of “A Survey of Transport Security > Protocols.” Please send comments, including “ready to publish”, to > [email protected]. Alternatively, specific issues can be raised via GIT > (https://github.com/ietf-tapswg/draft-ietf-taps-transport-security > <https://github.com/ietf-tapswg/draft-ietf-taps-transport-security>). > > This review period will conclude Monday, April 29. > > --aaron > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
