IETF Logo Mail Archive

Re: Getting the latest version of an RFC specification

Yoav Nir <ynir.ietf@gmail.com> Wed, 29 March 2017 22:04 UTC

Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E146126C2F for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 15:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6I1NykbamPTM for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 15:04:10 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6641126DDF for <ietf@ietf.org>; Wed, 29 Mar 2017 15:04:08 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id f84so8026882ioj.0 for <ietf@ietf.org>; Wed, 29 Mar 2017 15:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=4kN+sfeyUEb//g06D5wyTdHfGNSySOQkziCbOzN1hbY=; b=FJXwfPUKyuMCjMM8pZFtduxhpLcy3f2Ycs6bW1kjUTdouEDdg5pw+W1n2Ct79CeXTZ 38C24hVz1YavNyuOG8JL8PP89uaACmKzgmC8Wz1OngTtvtzMgoV8kir9oM2823n6fEcE +SApx8BdkSiqUfoa3MCj2CQwkM3Ko6qy+itF4YjqgpPnti/sRWFlRBqiW3xCKf7pYVgK R/OlEluXRsBbggOi+0FhOdpwftpahpQ+/EFCVup9+pEWzEecGb+9t+/Joma81lbBjwFS /KYDkloANwnW2DsEIVGxeQUg3ZyKfeprWBEB5+HHxER5+x/QdPg51cxZu4hzolPvWJmL oW6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=4kN+sfeyUEb//g06D5wyTdHfGNSySOQkziCbOzN1hbY=; b=Zk1bhKMwJBL6kTt89GBbCcSDNa/wEvhWicu4ZR62EMcADiPiduci8NQ4nwfKyqc/Fc fNkl2MoIOMuAW5YCL75dozin2x/GntvCtsx3leX4LG5/jtW55/Vc+WaSXLcgzHwKiTSr +h4cYKyatmtQmWrBK1GkHJL7N6FuG8gsm9ZGKebL4NvJhMHAvdSYJ3dIL9GOxbmKw6CM yDIlcKmKQkG2GtX9imU6M+MWzeZHW09Yh0HLvmanWtZ9LNsMxO9eY0CRTNKJKtnxsEVL 6fpOAFM3J/7W4+FH2Ja/97x+Ncns60eZe+hRsNOLXhXksE9iBFTP6KNna/nzzpuQnv/J hdtg==
X-Gm-Message-State: AFeK/H2kQAhKquC/fzUuWBhX31cg1ziG4TDgl152H5J7+zwvzjXWBHf5GwUSxptE2eFnPg==
X-Received: by 10.107.132.155 with SMTP id o27mr3141315ioi.138.1490825048048; Wed, 29 Mar 2017 15:04:08 -0700 (PDT)
Received: from t2001067c03700128f5d7507edd3635c6.v6.meeting.ietf.org (t2001067c03700128f5d7507edd3635c6.v6.meeting.ietf.org. [2001:67c:370:128:f5d7:507e:dd36:35c6]) by smtp.gmail.com with ESMTPSA id 33sm317545ios.54.2017.03.29.15.04.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 15:04:07 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <2FF66A0A-EC38-4915-A987-3F81424D29AF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E62268DD-ED66-4538-A518-1B0A1F75F6C7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Getting the latest version of an RFC specification
Date: Wed, 29 Mar 2017 17:04:06 -0500
In-Reply-To: <9437d845-ff46-3c02-f842-1ed1fae7f54b@dcrocker.net>
Cc: Matthew Kerwin <matthew@kerwin.net.au>, IETF general list <ietf@ietf.org>
To: dcrocker@bbiw.net
References: <94f81f6a-6a34-6587-a4f7-683586c2f436@dcrocker.net> <CACweHND9_9x7ZBc0_95keKbkQt8bz6YLJBP06qE=y=-S=GNDRg@mail.gmail.com> <C48761FC-E4C1-4951-ABF0-162B298135DA@gmail.com> <9437d845-ff46-3c02-f842-1ed1fae7f54b@dcrocker.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y_dJn4yo-ufA-2RLK5vCxsU5hlc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2017 22:04:12 -0000

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@dcrocker.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

v2.23.0 | Report a Bug | By Email