[Last-Call] Re: Last Call: Moving RFCs 793, 1065, 1723 and 1725 to Historic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2024-12-18, at 16:51, touch@xxxxxxxxxxxxxx wrote:
> 
> A *protocol* has its RFC designated as historic when the protocol is, not when the document is. 

What is a *protocol*?

I know what a document is.
One of the main reasons that RFC 9293 was created was that nobody knew any more what documents describe the protocol that we loosely call “TCP”, roadmap document notwithstanding.

On the subject of Internet Standards:

I wanted to know whether bib.ietf.org is as confused as the datatracker seems to be in its indications of status.

So I wrote a document that references STD 7 (TCP).

Please see for yourself:

https://www.ietf.org/archive/id/draft-bormann-what-is-tcp-00.html#name-normative-references

So *something* in our automation knows what documents are part of STD 7.
(As it does for BCP 14, which is also referenced in this little demo draft.)

Grüße, Carsten

-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux