Brian,
Thank you for opening the can of worms. Watch for a more detail
discussion of several of what emerged (not just this issue) that
I've been working on for a couple of hours soon.
best,
john
--On Saturday, January 8, 2022 08:47 +1300 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 being
> progressed in the Independent Submission Stream")? Will RFC
> 4491 receive an "Obsoleted by" tag?
>
> Regards
> Brian Carpenter
>
> On 08-Jan-22 06:08, The IESG wrote:
>>
>> The IESG has received a request from an individual
>> participant to make the following 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-94 Algorithms with the Internet X.509 Public Key
>> Infrastructure Certificate and CRL Profile)
>>
>> The supporting document for this request can be found here:
>>
>> https://datatracker.ietf.org/doc/status-change-old-gost-pkix-
>> 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@xxxxxxxx mailing lists
>> by 2022-02-04. Exceptionally, comments may be sent to
>> iesg@xxxxxxxx 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/rfc4491/
>>
>> IESG discussion of this request can be tracked via
>> https://datatracker.ietf.org/doc/status-change-old-gost-pkix-
>> to-historic/ballot/
>>
>>
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@xxxxxxxx
>> https://www.ietf.org/mailman/listinfo/ietf-announce
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
