[rfc-i] RFC search tool capabilities to the RFC index ?
pekkas at netcore.fi
Thu Nov 18 12:10:07 PST 2004
Speaking of which..
The RFC search has a useful functionality to:
- show historic/obsoleted documents grayed-out
- provide a link to the errata.
Unfortanately, I haven't been able to see the same input for the
*index* of all RFCs, or RFCs selected based on some criteria (based on
the category, based on RFC number, or even all of them), with the same
kind of user interface.
The best I've found is at:
Would it make sense to provide this in the same format as the RFC
search tool, or at least by "graying-out" obsoleted/historic
documents in the RFC-indexes such as:
.. to make it easier to spot still-assumed-relevant information
---------- Forwarded message ----------
Date: Thu, 18 Nov 2004 11:45:28 -0800
From: Aaron Falk <falk at ISI.EDU>
To: newtrk at lists.uoregon.edu
Cc: rfc-editor at rfc-editor.org
Subject: [newtrk] cruft & UPDATES, UPDATED-BY
I'm a bit behind on the mail list but this came up recently in some
RFC Editor discussions and since there appears to be forward momentum
in the cruft activity, I thought I'd bring it up now.
The RFC repository contains meta-data stating that RFCs update and are
updated by other RFCs. You can trace these relationships pretty
easily through the search engine on the RFC Editor site. The
semantics of these updates are a little fuzzy, sometimes meaning the
text is updated, sometimes the protocol, sometimes the standard. So,
I suggest that it is important for the cruft team to examine these
linkages and make recommendations that, when a document is made
HISTORIC, each RFC related by OBSOLETES, OBSOLETED-BY, UPDATES, or
UPDATED-BY attributes be evaluated as to whether it should be made
HISTORIC, too. If there is no change, that should be explicitly
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html
More information about the rfc-interest