[Lake] Genart last call review of draft-ietf-lake-traces-06

Joel Halpern via Datatracker <noreply@ietf.org> Mon, 04 September 2023 01:20 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern via Datatracker <noreply@ietf.org>
To: gen-art@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: <169379043411.64704.12901040769411900252@ietfa.amsl.com>
Reply-To: Joel Halpern <jmh@joelhalpern.com>
Date: Sun, 03 Sep 2023 18:20:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/dLrLI6lXSvJVIJFmB1fv5Yq9Q_A>
Subject: [Lake] Genart last call review of draft-ietf-lake-traces-06

Reviewer: Joel Halpern
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-lake-traces-??
Reviewer: Joel Halpern
Review Date: 2023-09-03
IETF LC End Date: 2023-09-11
IESG Telechat date: Not scheduled for a telechat

Summary: This document is technically ready, but has what appears to me to be a
significant procedural error that should be fixed before resolving publication.

Major issues:
    The draft lists [I-D.ietf-lake-edhoc] as an informative reference.  As that
    is the definition of the protocol for which this is providing traces, this
    appears to be meaningless without that, and thus [I-D.ietf-lake-edhoc]
    should be a normative reference.

Minor issues: N/A

Nits/editorial comments: N/A

[Lake] Genart last call review of draft-ietf-lake… Joel Halpern via Datatracker