On 18 Dec 2024, at 15:36, Brian E Carpenter wrote:
On 19-Dec-24 07:27, Pete Resnick wrote:
On 18 Dec 2024, at 11:46, S Moonesamy wrote:
The supporting document does not have any information about when the
request was made and who sent it. Would it be possible to disclose
who the individual participant is?Just in case others are curious: It was me, last week. Does it matter?
It doesn't matter at all, but thanks for the discussion anyway.
I'm curious, why only 4 candidates? I tweaked my code to separate out
the cases that are obsoleted Internet Standards, and there are eight of
them:Internet Standards (8 RFCs)
RFC0793 (STD?): Transmission Control Protocol
RFC0821 (STD10): Simple Mail Transfer Protocol
RFC0822 (STD11): STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
RFC1065 (STD?): Structure and identification of management information for TCP/IP-based internets
RFC1119 (STD?): Network Time Protocol (version 2) specification and implementation
RFC1723 (STD?): RIP Version 2 - Carrying Additional Information
RFC1725 (STD?): Post Office Protocol - Version 3
RFC1869 (STD10): SMTP Service Extensions(The STD? cases are where rfc-index.xml doesn't include the STD number.)
The 4 I chose already have Internet Standards replacing them, so nothing controversial about marking them Historic.
The STD10 (RFC821/RFC1869) and STD11 (RFC822) cases are going to be dealt with when 5321bis (post-Last Call) and 5322bis (Approved, waiting for refs) get published as Internet Standard, so no need for a complicated discussion there.
That leaves NTP. NTP is currently a bit of a mess: RFC 1119 (NTP v2) appears in the list without an STD number. RFC 1119 is obsoleted by RFC 1305 (NTP v3), which is currently at Draft Standard (!). RFC 1305 is obsoleted by RFC 5905 (NTP v4), which is currently at Proposed Standard. Erik asked the NTP list to sort this and they requested the status change for 1119 and 1305; that's currently in Last Call too. But that's the case where we don't have an Internet Standard that already replaces the existing one and that one does seem more controversial.
pr
I've put my code at https://github.com/becarpenter/misc/blob/main/RFCstatus.py
Brian
--
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
