IETF Logo Mail Archive

Re: How to get feedback on published RFCs [resending as plaintext]

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 19 July 2016 14:57 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 15F6B12E04A for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 07:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level:
X-Spam-Status: No, score=-2.69 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_LOW=-0.7, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] 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 payYnrBO9C_p for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 07:57:10 -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 E49F412E28D for <ietf@ietf.org>; Tue, 19 Jul 2016 07:34:19 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id l69so16135460lfg.1 for <ietf@ietf.org>; Tue, 19 Jul 2016 07:34:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=8LXdCzNgjaX886w/gd6ypqLL1Q1Yl/lstoskCvEF+Dk=; b=0H2g0gizuMlXkupCp1lv4nqSm8pEvA8J5ZRAAlsFaJjgn15KvR6Sj5+U2TDwT8l89t CgBxqgk9Q+h8rYE0PSEp/xat6w8UEkbNfz1qu2wTl+qMZSQXHsAZaAO0wv2Hj7mO5t15 Jr5Gv4iAMZ1xokr/HxgYcZQFrfmgXvGmsmP7LwOEXwW/vDG/D7H4Hs0uJQYtX5dFX6WD 4DNVSzHUUFwM9+IsIUur4r5QncoYSA8LwZcZc8svcZOXOdWM4NQr02Dg4B0ws4ZROz2O 0zf46JS3ruqb02DvVGbuMfea2gVCH3Aj9YgcU/kKGZPlNO9craxAzspinXg7e+tP0DwA ZxJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8LXdCzNgjaX886w/gd6ypqLL1Q1Yl/lstoskCvEF+Dk=; b=TEb0qEMHnGyTuI3/StygoZfJoOMKaOI1IXoSjfmEb7egUB1T26ppSwsKCyLOSWUEwY U0FG65KGQ5mYtkoq6o+W9p/JruEnf9A5CHpP7DuAebIrzPR1w6XdGNccrlvjZIDOKeNb kfYV1HhtIyKSZPVyY5ruqlLewrSp4qCP9wadMEXn6LCuUNvcMStT+3fmxtUgbKcJ1mfQ bW1Fy3x/qvfoLA7JVHMx/lEoI5XcZXThOVaVuJKTEkudOR8gOHhRzigNV2oL/CDqmyvo NP+zd2ipx2ep/sRfohvYZFqstMAMQ3RFi94N0AOxto6KHOF5Ajo3mpd+jSjHhMcTAz2z a5bw==
X-Gm-Message-State: ALyK8tJpyqPWqmK2A5ftLDfQFRpILu92LE1DDTWbVIcyfFf7bgFMpYIfAwWFlCMCJ5D4KQ==
X-Received: by 10.25.152.135 with SMTP id a129mr15671756lfe.226.1468938857871; Tue, 19 Jul 2016 07:34:17 -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 u70sm5706794lja.15.2016.07.19.07.34.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jul 2016 07:34:16 -0700 (PDT)
Subject: Re: How to get feedback on published RFCs [resending as plaintext]
To: "MH Michael Hammer (5304)" <MHammer@ag.com>, IETF <ietf@ietf.org>
References: <578E14F4.2040000@gmail.com> <CE39F90A45FF0C49A1EA229FC9899B05266CE983@USCLES544.agna.amgreetings.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <578E3A66.8040500@gmail.com>
Date: Tue, 19 Jul 2016 16:34:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B05266CE983@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5uYE1KHZAQYzxEelzhZXj6e4Kys>
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 14:57:12 -0000

On 19/07/16 15:16, MH Michael Hammer (5304) wrote:
>
>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Yaron Sheffer
>> Sent: Tuesday, July 19, 2016 7:54 AM
>> To: IETF
>> Subject: How to get feedback on published RFCs [resending as plaintext]
>>
>> 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.
>>
>
> A simple solution would be to include a pointer to the relevant working group as a header or note to the RFC. There could be a standard "How to comment" section. No need for additional tools or process.
>
> Mke
>

Working groups are not forever, so giving a working group name or email 
address is not very useful. Besides, not all comments (e.g. 
implementation experience) are even appropriate to send to the WG list.

Thanks,
	Yaron

v2.23.0 | Report a Bug | By Email