Re: Visibility of current RFC Maturity Levels (and how they got there (was: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic)

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

 



For me as an AD, I am either looking at the tools.ietf.org HTML
version or the datatracker page, or I am lamenting Google's
algorithm that placed me somewhere else.  But I don't know what
"people in general" are "reasonably expecting" to do; perhaps the
RFC Editor's plain-text repository remains canonical in usage as
well as in archival status, even if it is not for me.  (It's also
unclear how useful http/rsync/etc access logs would be for trying to
answer this question.)

I use rsync and find stuff using rfc-index.txt and rfc-index.xml. Those have the obsoletes and updates links but no URLs. Dunno how typical it is, but it's very convenient. The full archive including all the bulky postscript is about .5GB, not much these days.

Regards,
John Levine, johnl@xxxxxxxxx, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly




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

  Powered by Linux