Yeah, like instead of redirecting to the next stop, present a page with a list
of the obsoleting RFCs (name + title) and a link to each, like:
RFC 2616 is obsoleted by the following RFCs:
o RFC 7230 <https://tools.ietf.org/html/rfc7230/latest> - Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing
o RFC 7231 <https://tools.ietf.org/html/rfc7231/latest> - Hypertext Transfer
Protocol (HTTP/1.1): Semantics and Content
and so on….
On 29 Mar 2017, at 16:44, Dave Crocker <dhc(_at_)dcrocker(_dot_)net> wrote:
On 3/29/2017 4:40 PM, Yoav Nir wrote:
But there are examples that are properly tagged.
https://tools.ietf.org/html/rfc2616 is obsoleted by a series of six RFCs.
So to attempt a more serious suggestion -- remembering that the whole idea
here was KISS: If the Obsoleted-By field contains multiple pointers, then
present this fact to the user and request that the select one.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
signature.asc
Description: Message signed with OpenPGP