Last Call Review of draft-ietf-tsvwg-transport-encrypt-19
review-ietf-tsvwg-transport-encrypt-19-opsdir-lc-bhandari-2021-02-19-00

Request Review of draft-ietf-tsvwg-transport-encrypt
Requested rev. no specific revision (document currently at 20)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2021-02-19
Requested 2021-02-05
Authors Gorry Fairhurst, Colin Perkins
Draft last updated 2021-02-19
Completed reviews Secdir Early review of -01 by Christopher Wood (diff)
Opsdir Last Call review of -19 by Shwetha Bhandari (diff)
Genart Last Call review of -19 by Joel Halpern (diff)
Secdir Last Call review of -19 by Derek Atkins (diff)
Genart Telechat review of -20 by Joel Halpern
Assignment Reviewer Shwetha Bhandari 
State Completed
Review review-ietf-tsvwg-transport-encrypt-19-opsdir-lc-bhandari-2021-02-19
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/i6sa8Y_j9en85IElj2y8cSvg3OA
Reviewed rev. 19 (document currently at 20)
Review result Ready
Review completed: 2021-02-19

Review
review-ietf-tsvwg-transport-encrypt-19-opsdir-lc-bhandari-2021-02-19

I have reviewed this document as part of the Operational directorate's 
ongoing effort to review all IETF documents being processed by the IESG.  These 
comments were written with the intent of improving the operational aspects of the 
IETF drafts. Comments that are not addressed in last call may be included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat these comments 
just like any other last call comments. 

Summary: 
This is an informational document discussing possible impact when network traffic uses
 a protocol with an encrypted transport header. 

This document lists some current practises, and the implications for some stakeholders that depend on visibility of transport header fields for building tools for network operations and management, when transport layer header encryption is used. The document covers operational practises that assume unencrypted transport header fields and also suggests possible alternatives for network operators and operational tools designer  to utilize protocol features for e.g. embedding OAM information by end-points in the network layer, and fields that are available at network layer.  It also suggests issues to consider when designing new transport protocols or features to explicitly share observable fields with the network layer. 

Hence with regards to operational considerations listed in RFC 5706 I dont see any issues in this document.