Reviewer: Shwetha Bhandari Review result: Ready 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. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
