Tiru did a good job of sorting Normative and Informative.

The only unresolved Normative is
[I-D.ietf-lamps-dilithium-certificates], which is in the same cluster, so let's 
not make something out of nothing?


---
Mike Ounsworth

________________________________
From: Tim Hollebeek <tim.holleb...@digicert.com>
Sent: Friday, September 12, 2025 12:49:01 p.m.
To: Paul Hoffman <paul.hoff...@icann.org>; RFC Editor 
<rfc-edi...@rfc-editor.org>
Cc: K Tirumaleswar Reddy (Nokia) <k.tirumaleswar_re...@nokia.com>; Aritra 
Banerjee (Nokia) <aritra.baner...@nokia.com>; Dimitrios Schoinianakis (Nokia) 
<dimitrios.schoiniana...@nokia-bell-labs.com>; Mike Ounsworth 
<mike.ounswo...@entrust.com>; Sarah Tarrant <starr...@staff.rfc-editor.org>; 
paul.wout...@aiven.io <paul.wout...@aiven.io>; auth48archive@rfc-editor.org 
<auth48archive@rfc-editor.org>
Subject: RE: [Ext] [EXTERNAL] Document intake questions about 
<draft-ietf-pquip-pqc-engineers-14>

We were originally trying to get this RFC out before the NIST announcement
last summer. Let's not hold it up until it is no longer useful.

More than happy to help brainstorm pragmatic solutions to Deb's perfectly
reasonable concern, if it would help.

-Tim

> -----Original Message-----
> From: Paul Hoffman <paul.hoff...@icann.org>
> Sent: Friday, September 12, 2025 11:04 AM
> To: RFC Editor <rfc-edi...@rfc-editor.org>
> Cc: K Tirumaleswar Reddy (Nokia) <k.tirumaleswar_re...@nokia.com>; Aritra
> Banerjee (Nokia) <aritra.baner...@nokia.com>; Dimitrios Schoinianakis
(Nokia)
> <dimitrios.schoiniana...@nokia-bell-labs.com>; Tim Hollebeek
> <tim.holleb...@digicert.com>; Mike Ounsworth
> <mike.ounswo...@entrust.com>; Sarah Tarrant
<starr...@staff.rfc-editor.org>;
> paul.wout...@aiven.io; auth48archive@rfc-editor.org
> Subject: Re: [Ext] [EXTERNAL] Document intake questions about <draft-ietf-
> pquip-pqc-engineers-14>
>
> Deb did indeed insist that all the added references, including to drafts
that might
> take forever to complete, be normative because a reader of the document
would
> not be able to fully understand the document without them.
>
> I disagree with here assessment of the reasoning, and would love the RFC
Editor
> to remind the IESG about the IESG's own statement, in specific "For
example, an
> informative reference might provide background or historical information."
>
> draft-ietf-pquip-pqc-engineers now has a bunch of normative references
that
> could, in my mind as document shepherd, be informative.
>
> --Paul Hoffman


Any email and files/attachments transmitted with it are intended solely for the 
use of the individual or entity to whom they are addressed. If this message has 
been sent to you in error, you must not copy, distribute or disclose of the 
information it contains. Please notify Entrust immediately and delete the 
message from your system.

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to