[Lake] Secdir last call review of draft-ietf-lake-traces-07

Ivaylo Petrov via Datatracker <noreply@ietf.org> Sat, 16 September 2023 17:54 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ivaylo Petrov via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-lake-traces.all@ietf.org, lake@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <169488689598.20310.2907983251532754551@ietfa.amsl.com>
Reply-To: Ivaylo Petrov <ivaylopetrov@google.com>
Date: Sat, 16 Sep 2023 10:54:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/bFU6wNo2ZYf0x85ly51_607o-Z0>
Subject: [Lake] Secdir last call review of draft-ietf-lake-traces-07

Reviewer: Ivaylo Petrov
Review result: Ready

Reviewer: Ivaylo Petrov
Review result: Ready

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG. These comments were written primarily for the benefit of the
security area directors. Document editors and WG chairs should treat
these comments just like any other last call comments.

I haven't verified the examples myself, but the rest looked good to
me. Thank you for writing this document! 

I agree with Roman that the provided examples need to be consistent
with I-D.ietf-lake-edhoc when that is published and this document 
should point to the resulting RFC.

[Lake] Secdir last call review of draft-ietf-lake… Ivaylo Petrov via Datatracker