[tao-discuss] Fwd: Re: what to do about missing cites and encouraging better citing

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 26 June 2018 20:36 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tao-discuss@ietfa.amsl.com
Delivered-To: tao-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F329130EDB for <tao-discuss@ietfa.amsl.com>; Tue, 26 Jun 2018 13:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 54Rh20LZanj2 for <tao-discuss@ietfa.amsl.com>; Tue, 26 Jun 2018 13:36:22 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 1465F130E3C for <tao-discuss@ietf.org>; Tue, 26 Jun 2018 13:36:22 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id g3-v6so3865030pfi.1 for <tao-discuss@ietf.org>; Tue, 26 Jun 2018 13:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=0JOzEn/5nmb5POKRWId0lsKx+tX6O7wGR0M/T/BYmzU=; b=hwZu4Sdc1yNSWqzx2CHSWI/Cb/QnO4q12JxjM3v0mBE9tBFnsI5xKWjsZ9JXQc6Hvp dmTkhPl4YmDIbi2ocMOQdI4kqP7Z2IyFv5s+/UuFkIpm7C8peCTxfQ1/JZiaOqEIc+4u OTD2fdghHbt8pTRv9NIlnKsN/La7dA/nR9T1OrHAxCMWGV+1GGuLglIja1U2it7Ka/zN p6lA8kppJK4jECkogiFcFSF/YrwTwN05bB/Bpt90PPR7VzmBAeUzIIYSL1KHwu7lLcru lSCrJoFeNzXj38OdQqb5yuTBmjqS0LHsQ5W3bKdjvhINUFuJH7LHx6xWVjYiBjF6tdK1 o1GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0JOzEn/5nmb5POKRWId0lsKx+tX6O7wGR0M/T/BYmzU=; b=nPIb2yiaSkACKl5AV8hbj35i1pn1TtcWjEBXINcXQgoNjdJOH+zFg8gaxrDkBzKzK2 y0XrgeX768tpFWsVbP7TfBUdQ9elmCggyEZOxz2gfqC9TM1LFwMqEvg93QlkFVVV8jn9 Uj8/mjRc5/TVM3JObeeIpp0yN1Y+vobIccJ8rl3teWx+E9Ax/QUg4I7hKKVOjwZGI77K NGHa+mTOGSlMkmVQp54tVXPaFLhIB3ti4+9M+T/NrU5SCNJj6yYBlbTDFTQbo26UA1q9 YIGJVzGPiY4O5wBEwDtuw0WxPU5LqpUDMlzvxKumBMxBf1lwVhGygrU4Ujqd/1yRDEn1 9q0w==
X-Gm-Message-State: APt69E0Tg8TZH7SNo7TyepVSjGOmJiSnrYTlf+ijeGb2YFERz8rmLpVC zqfDy3jC65xPYwwex8mzL+GlzA==
X-Google-Smtp-Source: ADUXVKIE1DsqvRL1ImLlDVIl2CujjmX7J5+iiJItyuYeBVl5cLHJicrME3hovOTo2l0HE97pMGI75Q==
X-Received: by 2002:a65:5884:: with SMTP id d4-v6mr2586875pgu.292.1530045381625; Tue, 26 Jun 2018 13:36:21 -0700 (PDT)
Received: from [192.168.178.38] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id m5-v6sm4934443pgn.45.2018.06.26.13.36.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Jun 2018 13:36:20 -0700 (PDT)
References: <2b16b471-8d23-1d52-dd5d-275290a1fdf2@rfc-editor.org>
To: tao-discuss@ietf.org
Cc: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Forwarded-Message-Id: <2b16b471-8d23-1d52-dd5d-275290a1fdf2@rfc-editor.org>
Message-ID: <b8114894-6cb4-a226-1151-0b7965045f91@gmail.com>
Date: Wed, 27 Jun 2018 08:36:17 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <2b16b471-8d23-1d52-dd5d-275290a1fdf2@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/VLJWmkrKMXFV7CN81hqK4w0WdG4>
Subject: [tao-discuss] Fwd: Re: what to do about missing cites and encouraging better citing
X-BeenThere: tao-discuss@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Discussion of the Tao of the IETF <tao-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tao-discuss/>
List-Post: <mailto:tao-discuss@ietf.org>
List-Help: <mailto:tao-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2018 20:36:25 -0000

Forwarding this because it includes:

> I think a note on the IETF norms for referencing other RFCs to be a good 
> thing to include in the Tao.

And maybe some of the waffle in https://tools.ietf.org/html/draft-carpenter-whats-an-author would also fit in the Tao?

   Brian

-------- Forwarded Message --------
Subject: Re: what to do about missing cites and encouraging better citing
Date: Tue, 26 Jun 2018 13:24:12 -0700
From: Heather Flanagan (RFC Series Editor) <rse@rfc-editor.org>
To: ietf@ietf.org

On 6/25/18 12:52 AM, John C Klensin wrote:
>
> --On Sunday, June 24, 2018 17:14 -0700 Randy Bush
> <randy@psg.com> wrote:
>
>>> but didn't detect great enthusiasm in the community for
>>> dealing with authorship ethics in general.
>> how embarrassing and shameful
> Randy,
>
> While I agree that this is embarrassing and shameful (and could
> add other words), I question one aspect of your earlier note.
>
> At least until the IAB decides to micromanage that, an erratum
> and its appropriateness is determined by the discretion of the
> RFC Series Editor.  The term is arguably not precisely correct
> for the way we use the things and I've seen many of them whose
> subject matter or content would not be appropriate if the
> classic publisher definition were used.
>
> So I would recommend a conversation with Heather (copied) and
> use of the errata mechanism, at least unless she strongly
> disagrees and wants to propose another mechanism.  That would at
> least get citation on the record.  While I'm not optimistic, if
> author(s) are shamed sufficiently to not omit such citations in
> the future, that would be A Good Thing.  I think all of us
> should be encouraged to watch for obvious omissions on Last Call
> and would encourage document shepherds and responsible ADs (in
> the IETF Stream) and reviewers (in others) to pay attention to
> the issue.

Heather does not disagree - the errata system is the best mechanism we 
have at this time, and it does allow an author to respond as needed.

>
> I would suggest to Heather that a mention of this as the Style
> Guide evolves would probably also be a good thing -- it isn't as
> if adding relevant citations is difficult or costly.

This is going to be a bit trickier. I'm supportive of adding something 
about author ethics, but it would be along the lines of "the RFC Editor 
will not be checking on this; you should do this because it's the right 
thing." We don't have the resources to do a full-on review of the 
literature; if the IETF wants that as a priority, we'll need to talk 
about costs and/or reprioritizing other RFC Editor activities.

I think a note on the IETF norms for referencing other RFCs to be a good 
thing to include in the Tao.

-Heather

>
> We will probably never get everything right, but we can try
> harder.
>
> best,
>     john
>