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)
Julian Reschke <julian.reschke@gmx.de> Tue, 15 May 2018 16:32 UTC
Return-Path: <julian.reschke@gmx.de>
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 79BFA12D77D for <ietf@ietfa.amsl.com>; Tue, 15 May 2018 09:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2RnJDF_76tGI for <ietf@ietfa.amsl.com>; Tue, 15 May 2018 09:32:48 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 522E9126BF7 for <ietf@ietf.org>; Tue, 15 May 2018 09:32:48 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.119.143]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MOjMY-1fEnOX2nI6-0065SO; Tue, 15 May 2018 18:32:35 +0200
Subject: 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)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, John R Levine <johnl@taugh.com>
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <CAKKJt-fcvUhQdDykv8mzS_a+AgAQO0jMBfK+zVk++FD=1+7w5w@mail.gmail.com> <a71ae235-57ca-1350-b4d7-36c78986cb5b@gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <5767225f-bced-60eb-fc2b-dcc375def99f@gmx.de>
Date: Tue, 15 May 2018 18:32:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <a71ae235-57ca-1350-b4d7-36c78986cb5b@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:MRf2oRu2VE41gteTuA4diKb/qYN2+qgv/iQOvcAqD5fs86f7vys yOZJKKbW0wDdtG496OXCk+de/FA0VWhLGjcwRN3NvX1WsGSPsyljM0CiI7GWrp0QNACvuD9 e9ZPsXZjByfx+UQI+vBu57uXUcMAsMLWOyfryicHV7tsNarzv5rxX/ZW8FEcq8Ztgxq7a0Y cMnZAYvEr+7v0rWUnozuQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Dp1StX2QBCQ=:nKCvWV7AD1dbigmZQuuHP8 H5HQyHmRo5MRWbGBcc3Xzn7FhyUNoXbnoxFMSyUtc7btUZbA+dS4i5Yu0OllR58Mz6RoWPX/Q oI2tz2lYGwO1N9jObPjqJ0xD41y7wpGgyG3b62e0LQYPxqzSvOOp+3HJapELIV5b6zCSnoPG+ ZDPm1bkbkzo8qccn1CI698zdxsF63HdtEXvP+FkkW4s8pK/oOU4r4e9d5iBUiGzs+W3fDqg+L FtqlXSn5L1KxnQGVnlNHa02MzRT683NI39B0mjPb/OrpY1lJh7T5+t9b+OQB9iSjsxogOJaXQ myvzDDJhNh8uNlTwXBLwxSCk4ZgLZ4hv09oF6koXgKIXozRJGDNyI4q+bxNt9uM7oMRJzUNSp 9EGu9KVk2oQAJgZAO3R09X9/58V6O8Qxfg8hCb+Kn8uy9+QVrcY2RxReyNLealnelTmW3sZ3R kmHxkyKWZ+OdKtk+PANHMxfY0M86fRfsYbRXNtbJ0YKcZbwNQYwH8JZuCMsOsk3pqjiHWTObA c4nUtxjOPdldCRnCYBgD0zEK9+vOEQ+qZweSKQkCDRRRCfyzGEOY3DbDmjVrjZ621yytqQeug UlG2ZeVixHzJU9I0Iv+HwN3nbQQjLooyJb1umPzwjpk182v9eHQY+cAcaBuXxsxWKXq05CVht cY9VzBEHYbcvkr85XJTwjvk0XsvgYKLbBum6Zr/mbBPARi/0ikTu7IoJyY1bE1CdvW5sfDXRi chQQQN78TBY74RIWG2zV/HR8OWpBbuIt8YGQKi/3WRY0IuetVYnFHBhe6OGraCMm61sD7e/PF 5M9djXt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vfmlyWQavoSY-UIkFmRzxD5Nv3E>
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: Tue, 15 May 2018 16:32:50 -0000
On 2018-05-15 02:17, Brian E Carpenter wrote: > Top posting to note that if you find the RFC via its DOI you > also get the correct status first. I think the RFC Editor has > done the best they can, consistent with the policy that the > bits in the canonical form of an RFC never change. > ... In the hopefully not so distant future, the RFC Editor will also serve HTML. As that is *not* the "canonical" version, it could dynamically insert current metadata (such as demonstrated in various places, for instance <https://tools.ietf.org/html/rfc2616> or <https://greenbytes.de/tech/webdav/rfc2616.html>). To make this work *well*, the RFC Editor should publish the metadata *per* RFC in a machine readable (XML or JSON) and web-friendly (CORS) way. Best regards, Julian
- Visibility of current RFC Maturity Levels (and ho… Spencer Dawkins at IETF
- Re: Visibility of current RFC Maturity Levels (an… Brian E Carpenter
- Re: Visibility of current RFC Maturity Levels (an… Benjamin Kaduk
- Re: Visibility of current RFC Maturity Levels (an… Barry Leiba
- Re: Visibility of current RFC Maturity Levels (an… John R Levine
- Re: Visibility of current RFC Maturity Levels (an… tom p.
- Re: Visibility of current RFC Maturity Levels (an… Julian Reschke
- Re: Visibility of current RFC Maturity Levels (an… Barry Leiba