Re: [Errata-design] An example of an erratum that takes time for little value

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 13 January 2015 22:42 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: errata-design@rfc-editor.org
Delivered-To: errata-design@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id B8106181CD8; Tue, 13 Jan 2015 14:42:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ia_hNUt8HuPr; Tue, 13 Jan 2015 14:42:49 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by rfc-editor.org (Postfix) with ESMTP id 13772181CD3; Tue, 13 Jan 2015 14:42:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 92F17BECA; Tue, 13 Jan 2015 22:43:33 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eVuGDSeZRCL; Tue, 13 Jan 2015 22:43:32 +0000 (GMT)
Received: from [10.87.48.73] (unknown [86.41.54.55]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 08B34BEBB; Tue, 13 Jan 2015 22:43:32 +0000 (GMT)
Message-ID: <54B59F93.2010909@cs.tcd.ie>
Date: Tue, 13 Jan 2015 22:43:31 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, errata-design@rfc-editor.org
References: <54B59B0A.6040809@rfc-editor.org>
In-Reply-To: <54B59B0A.6040809@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [Errata-design] An example of an erratum that takes time for little value
X-BeenThere: errata-design@rfc-editor.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <errata-design.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/errata-design>, <mailto:errata-design-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/errata-design/>
List-Post: <mailto:errata-design@rfc-editor.org>
List-Help: <mailto:errata-design-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/errata-design>, <mailto:errata-design-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2015 22:42:50 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 13/01/15 22:24, Heather Flanagan (RFC Series Editor) wrote:
> 
> Hello all,
> 
> While we're waiting for everyone to respond to the Doodle poll
> (*hint* https://doodle.com/925i53egnm5957i2 *hint*), an example
> recently came up for discussion of an errata that is not helping
> the world be a better place.
> 
> http://www.rfc-editor.org/errata_search.php?eid=4230
> 

That's one kind of useless-time-sink. I've found the worst ones
are like [1] where there's a technical change that's not obviously
an erratum (or not) for a protocol nobody cares about and where
there's no WG or accessible source of an authoritative answer
as to whether the change suggested is good or not. And of course
nobody except possibly (only possibly!) the busy-body who posted
the thing cares anyway.

   [1] http://www.rfc-editor.org/errata_search.php?eid=3811

> I suggest that a measure of a successful errata system will be one 
> visually and through metadata differentiate between levels of
> usefulness for an implementer/reader.

Yep.

> The vote system could be of use here (though the irony of even
> thinking "vote" and "IETF" in the same context tweaks my brain).

Think of it as modding up/down and not voting, or as like/dislike.
But yeah, let's not call it voting. (On the sound technical basis
that there is no register of electors. I'm sure Pete will have a
principle that we can use here:-)

> Any alternative opinions to whether that measure is reasonable?

Yes. If it's done so that almost anyone can do the modding up/down.
I'd be fine with a requirement for an IETF tracker or tools a/c
to be allowed hit that button. We don't have to create new RFC
editor accounts IMO as we don't really care who is modding up/down,
we just want some not-quite-trivial anti-spam and multiple-voting.

And I'm also fine that we leave all that vulnerable to Sybil
attacks.

S.


> 
> -Heather
> 
> 
> 
> _______________________________________________ Errata-design
> mailing list Errata-design@rfc-editor.org 
> https://www.rfc-editor.org/mailman/listinfo/errata-design
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUtZ+NAAoJEC88hzaAX42ila4H/Rn+sVlle4TOZyQ7JSHoeIDr
gFFSt08rac7pp3fdNbkBDQaszHZe8vIAqBk+NoCR96S9P5KNWnUezJ+JBoYOvPLG
kMjbchJU0T1WS59hrGALEjNa9oWqs2sDxUx3u7gPMdNGcllKqgYvQAF+FySKLNur
x1axZxG4lTibmWvUb3rQVqUrlBiYYegxb8w7VmeW1snPEAvayZCR1RONDzbvyE2/
mh+Ml164+lDSIbVL5HH8kc6RMckdKVLhf0n/51QKQTB434XN4LJihXPiOxDpD3n0
SVdQBWTxHmVcy9Ub818wWbL5jnlQTabzsLaa/ecxKfCqBMgBah4gZ7XS6A6vvZY=
=XPPf
-----END PGP SIGNATURE-----