Re: [DNSOP] Last Call: Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic
I agree new code points should gave new RFCs. I am ok with OBSOLETE or DEPRECATED Sent from my iPhone On Nov 29, 2023, at 17:18, Paul Wouters wrote: On Wed, 29 Nov 2023, Warren Kumari wrote: > So, the IANA has a question: > 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? > If IANA is asked to make changes to these registrations, IANA will add a link > to the status change > document to the registrations." > Seeing as GOST R34.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 RFC5933 is being made historic (replaced by > draft-makarenko-gost2012-dnssec which > describes how to use the GOST 2012 algs), I think that "OBSOLETE, see RFC number>" is best, but I > wanted the WG's input… I don't think a pointer to the new RFC should be used, because we are not re-assigning the code points. Let new code points point to the new RFC. So just "DEPRECATED" I think ? Paul ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Last Call: Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic
On Wed, 29 Nov 2023, Warren Kumari wrote: So, the IANA has a question: 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? If IANA is asked to make changes to these registrations, IANA will add a link to the status change document to the registrations." Seeing as GOST R34.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 RFC5933 is being made historic (replaced by draft-makarenko-gost2012-dnssec which describes how to use the GOST 2012 algs), I think that "OBSOLETE, see " is best, but I wanted the WG's input… I don't think a pointer to the new RFC should be used, because we are not re-assigning the code points. Let new code points point to the new RFC. So just "DEPRECATED" I think ? Paul ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Last Call: Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic
On Mon, Nov 20, 2023 at 6:08 PM, Paul Hoffman wrote: > [[Forwarding this to DNSOP because apparently the IESG forgot to...]] > Thank you. > 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) > > So, the IANA has a question: 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? If IANA is asked to make changes to these registrations, IANA will add a link to the status change document to the registrations." —--- Seeing as GOST R34.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 RFC5933 is being made historic (replaced by draft-makarenko-gost2012-dnssec which describes how to use the GOST 2012 algs), I think that "OBSOLETE, see " is best, but I wanted the WG's input… W [0]: This happened because the AD (me) requests that IETF LC be started, and then the secretariat actually kicks it off. In this case I requested it over the weekend, and was out on Monday. > 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-c...@ietf.org mailing lists by 2023-12-18. Exceptionally, comments > may be sent to i...@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/ > > ___ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > > ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] Last Call: Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic
[[Forwarding this to DNSOP because apparently the IESG forgot to...]] 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-c...@ietf.org mailing lists by 2023-12-18. Exceptionally, comments may be sent to i...@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/ ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
