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 <[email protected]> > Sent: Friday, September 12, 2025 11:04 AM > To: RFC Editor <[email protected]> > Cc: K Tirumaleswar Reddy (Nokia) <[email protected]>; Aritra > Banerjee (Nokia) <[email protected]>; Dimitrios Schoinianakis (Nokia) > <[email protected]>; Tim Hollebeek > <[email protected]>; Mike Ounsworth > <[email protected]>; Sarah Tarrant <[email protected]>; > [email protected]; [email protected] > 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
smime.p7s
Description: S/MIME cryptographic signature
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
