Reviewer: Victor Kuarsingh Review result: Ready Reviewer: Victor Kuarsingh 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. As part of this ops review, I did not find anything that would restrict this document's readiness, but have operationally oriented questions/comments for consideration. (1) The document did not share how much (% of overhead, cycle time, etc) impact calculating the checksum has which means that, in production networks, the true impact is unknown. The overhead is likely to change, so how do participating nodes know if they should even care about the overhead? Changing code implementation that affects functionality should be considered in relation to such benefit. In short, exposing stable implementations to changes to save what could be a trivial amount of overhead may or may not be worth it. Again, this is a general question and does not impact publishing IMO. (2) What is the assumption about how the higher layer integrity checks occur? What about a use case where the upper layer checks can be turned off mid-session? would that consideration need to be considered? I don't know if such implementations actually occur in practical terms, but it's a potential failure case. this is theoretical in nature. outside of those question, no specific changes are noted to be made as part of this review. -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
