Hi, just chiming in to say draft-deremin-rfc4491-bis does not obsolete RFC 4491 (that would involve crossing the streams) or in any way mention RFC 4491 (except in the slightly confusing file name that is a legacy of an early version of the draft).
draft-deremin describes how to use the latest versions of the GOST algorithms in conjunction with IETF specifications and practices. It makes no comment on previous versions of GOST algorithms.
RFC 4491 is the product of the IETF stream. In discussion with one of the SEC ADs it was determined that it would also be useful to make the RFC Historic as it refers to a set of algorithms that have been withdrawn by their original publisher and that are strongly deprecated on security grounds. In order to help facilitate that, the ISE and the draft author invented some text for last call announcement and gave it to the AD, however the choice of words and the decision to call to mark 4491 Historic is an IESG action that requires IETF consensus.
If there is any need to order the publication of draft-deremin ad an RFC and the status change of RFC 4491, I am unaware of it.
Best,
Adrian (as ISE but from my personal email account)
On 07/01/2022 21:20 Russ Housley <housley@xxxxxxxxxxxx> wrote:
It looks like draft-deremin-rfc4491-bis is in the works to replace RFC 4491. Why is this action needed before the bis is approved to replace it?
Russ
On Jan 7, 2022, at 2:47 PM, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote:
Naive question:
RFC 4491 (currently a PS) formally updates RFC 3279 (also a PS). How will a reader of RFC 3279 in future know that they need to look at RFCxxxx ("a new document beingprogressed in the Independent Submission Stream")? Will RFC 4491 receive an "Obsoleted by" tag?
RegardsBrian Carpenter
On 08-Jan-22 06:08, The IESG wrote:The IESG has received a request from an individual participant to make thefollowing status changes:- RFC4491 from Proposed Standard to Historic(Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94Algorithms with the Internet X.509 Public Key Infrastructure Certificateand CRL Profile)The supporting document for this request can be found here:The IESG plans to make a decision in the next few weeks, and solicits finalcomments on this action. Please send substantive comments to thelast-call@xxxxxxxx mailing lists by 2022-02-04. Exceptionally, comments maybe sent to iesg@xxxxxxxx instead. In either case, please retain the beginningof the Subject line to allow automated sorting.The affected document can be obtained viaIESG discussion of this request can be tracked via_______________________________________________IETF-Announce mailing list--last-call mailing list--last-call mailing list
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
