How to get feedback on published RFCs

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 19 July 2016 09:42 UTC

Return-Path: <yaronf.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 B61E012DE61 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 02:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 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, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 lTVFUzZaOI6U for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 02:42:04 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 B265312DE74 for <ietf@ietf.org>; Tue, 19 Jul 2016 02:35:18 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id g62so8687568lfe.3 for <ietf@ietf.org>; Tue, 19 Jul 2016 02:35:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=bUZPOVGQvgOiBNviYlJd8Jxw3aZIULUB2gOweuyLtjI=; b=fOo0itTrHYkSxSMdB9g+BoHXEmXuW67S+D73i5YKtDQgaVstbjTlYxniYJUCStNhBq qpbGOVeOtV6obzBc4ABPAoyHoFsUWgO8YWtgM9D8dA2L6pyKBCVWBKKdAbo7bj7aHG3r 3o/WmIBd3RcuCvnmBTa4OHEyAmu7nPlmq59ynsF6KQAiB7GL2OZsOlpwrHLn/eNrFJF7 DbaXVtb1YXQSWdVJ5ZU+vOYA4yvm7qhh1N2K4A+3ZrY9AXg9dPS2sk18kIDMc9sryjc4 PP7iVljacwbZxtARWoiytUohzRrd5/crw1OYljVUWQXL2ZlFD9WSXyenxguVGZVQ8Ebk v1yQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=bUZPOVGQvgOiBNviYlJd8Jxw3aZIULUB2gOweuyLtjI=; b=BiMR4jUpMSl6DMGYptNd8E4rfAeV1YyrTGHSlCjUgak5qUKbGPnHsac5mPFPFfxM5h oFCPAIGCup6W5JvY8bCztirxGzwN53ID5MNmxa6r/6M6eoJv8YV+H8MUUM2eR55NNO8b +JPjlhPBHUiOsCiO11sL4bnvkTR/qBenL65vWqP8RKxqpnT2QDmrfgoMKgPTZ1OaVuYD kuPZu8OhRoBjCcUI+kDyOTYDhp8dP7yW21AVETfO5XuKOcoRx9KSzHeE95tBi5gmHDMz Nbj+Vnv00Nat9eyYplmp3eB8wVKdQjeA4bi/Vz9iW+WA+/1rup1kNwtK1G8BqwOVTymn vSyg==
X-Gm-Message-State: ALyK8tJJVWqNdMOqtpWRa13lT9C+xco3VU8Zl8gC+2KoyRkRwaFlT0fn/4qDA5fc8Tvq+A==
X-Received: by 10.25.19.169 with SMTP id 41mr14619105lft.24.1468920916583; Tue, 19 Jul 2016 02:35:16 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:160:48cf:6beb:a726:d082? ([2001:67c:370:160:48cf:6beb:a726:d082]) by smtp.gmail.com with ESMTPSA id j64sm157168lfb.31.2016.07.19.02.35.14 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jul 2016 02:35:15 -0700 (PDT)
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: How to get feedback on published RFCs
To: IETF <ietf@ietf.org>
Message-ID: <578DF452.70107@gmail.com>
Date: Tue, 19 Jul 2016 11:35:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mF1UXyjFjA1kY1TAWPleH1W7uNg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 19 Jul 2016 09:42:05 -0000

Once an RFC is published, there is essentially no way for readers to provide feedback: what works, what are the implementation pitfalls, how does the document relate to other technologies or even to other RFCs.

We IETF insiders usually know what is the relevant working group, and can take our feedback there. Non-insiders though don't have any contact point, and so will most likely keep their feedback to themselves. These non-IETFers are the target audience of our documents! Unfortunately, our so-called "Requests for Comments" are anything but an invitation to submit comments.

There is a number of tools now that allow "web annotations" (i.e., comments) on various published documents. I submitted a draft [1] recently that proposes to enable annotations on the "tools" version of our RFCs. Technically, this is a trivial change. From a process point of view it is more complicated and merits discussion on this list. Sec. 6 of the draft allows you to see for yourself what such annotations would look like.

I am here in Berlin if people prefer to talk it over in person. Otherwise, please reply on this list.

Thanks,
    Yaron 

[1] https://tools.ietf.org/html/draft-sheffer-ietf-rfc-annotations-00" rel="nofollow">https://tools.ietf.org/html/draft-sheffer-ietf-rfc-annotations-00