Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic
status-change-gost-dnssec-to-historic-05

The following approval message was sent
From: The IESG
To: IETF-Announce 
Cc: The IESG ,
    dnsext-chairs@ietf.org,
    iana@iana.org,
    rfc-editor@rfc-editor.org,
    rfc5933@ietf.org,
    warren@kumari.net
Subject: Protocol Action: Use of GOST Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC to Historic

The IESG has approved changing the status of the following document:
- Use of GOST Signature Algorithms in DNSKEY and RRSIG Resource Records for
DNSSEC
  (rfc5933) to Historic

This protocol action is documented at:
https://datatracker.ietf.org/doc/status-change-gost-dnssec-to-historic/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc5933/

Status Change Details:

RFC5933 - "Use of GOST Signature Algorithms in DNSKEY and RRSIG Resource
Records for DNSSEC" was published in the IETF Stream and refers only to GOST
R 34.10-2001 and GOST R 34.11-94. GOST 34.10-2001 and GOST 34.11-94 were
deprecated by the Orders of the Federal Agency for Technical Regulation and
Metrology of Russia (Rosstandart) in August 2012, and superseded by GOST
34.10-2012 and GOST 34.11-2012 respectively from January 1, 2013.

draft-makarenko-gost2012-dnssec describes "how to produce digital signatures
and hash functions using the GOST R 34.10-2012 and GOST R 34.11-2012
algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain
Name System Security Extensions (DNSSEC)" will be published on the ISE stream.

This status change document marks RFC5933 as historic.

Personnel

  Warren Kumari is the responsible Area Director.

[Ballot discuss]
==[ original text ]==
The update to RFC5933, draft-makarenko-gost2012-dnssec, describing "how to
produce digital signatures and hash functions using the GOST R 34.10-2012 and
GOST R 34.11-2012 algorithms for DNSKEY, RRSIG, and DS resource records, for
use in the Domain Name System Security Extensions (DNSSEC)" will be published
on the ISE stream.
==[ original text ]==

Since this text is discussing documents crossing stream, I recommend we be be pedantically precise.  draft-makarenko-gost2012-dnssec is not "updating" RFC5933 in the formal sense.  That document doesn't use the update tag and and ISE document updating an PS in IETF stream would be an anomaly.  draft-makarenko-gost2012-dnssec is providing another code point.

IMO, the text should read: s/The update to RFC5933, draft-makarenko-gost2012-dnssec, describing/draft-makarenko-gost2012-dnssec describes/

[Ballot discuss]
Really a simple request for discussion with other IESG members about timing and procedure.

How can the last paragraph (repeated below) be implemented? Would it be easier to defer this status change until draft-makarenko-gost2012-dnssec is published ?

`This status change document marks RFC5933 as historic, and will take affect
once draft-makarenko-gost2012-dnssec is published as an RFC.`

Beside this timing/process issue, I have no objection to this status change.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of status-change-gost-dnssec-to-historic-03. If any part of this review is inaccurate, please let us know.

IANA has a question about this document.

IANA understands that the intent of status-change-gost-dnssec-to-historic is to, along with the work in draft-makarenko-gost2012-dnssec, mark RFC5933 as historic. IANA also understands that this will go into effect once the other draft is approved by the IESG.

IANA Question --> What about the registrations that currently reference RFC5933?

Should the registrations currently referencing RFC5933 be marked "OBSOLETE," "DEPRECATED," changed in some other way, or left alone?

Please see:

https://www.iana.org/assignments/dns-sec-alg-numbers/
https://www.iana.org/assignments/ds-rr-types/

If IANA is asked to make changes to these registrations, IANA will add a link to the status change document to the registrations.

For definitions of IANA review states, please see:

https://datatracker.ietf.org/help/state/draft/iana-review

Thank you,

David Dong
IANA Services Sr. Specialist

The following Last Call announcement was sent out (ends 2023-12-18):

From: The IESG
To: IETF-Announce
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call: Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic


The IESG has received a request from an individual participant to make the
following status changes:

- RFC5933 from Proposed Standard to Historic
    (Use of GOST Signature Algorithms in DNSKEY and RRSIG Resource Records
    for DNSSEC)

The supporting document for this request can be found here:

https://datatracker.ietf.org/doc/status-change-gost-dnssec-to-historic/

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-12-18. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

The affected document can be obtained via
https://datatracker.ietf.org/doc/rfc5933/

IESG discussion of this request can be tracked via
https://datatracker.ietf.org/doc/status-change-gost-dnssec-to-historic/ballot/