IETF Logo Mail Archive

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

mrex@sap.com (Martin Rex) Wed, 27 July 2016 17:49 UTC

Return-Path: <mrex@sap.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 D6F2312D768 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2016 10:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level:
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-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 HoXLwkzv_b9E for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2016 10:49:52 -0700 (PDT)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB9CF12D7BF for <ietf@ietf.org>; Wed, 27 Jul 2016 10:49:52 -0700 (PDT)
Received: from mail06.wdf.sap.corp (mail06.sap.corp [194.39.131.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id 3s02Z62K2sz1HkC; Wed, 27 Jul 2016 19:49:50 +0200 (CEST)
X-purgate-ID: 152705::1469641790-00000827-1A50BC74/0/0
X-purgate-size: 1183
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail06.wdf.sap.corp (Postfix) with ESMTP id 3s02Z60t87zl10F; Wed, 27 Jul 2016 19:49:50 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 174E01A508; Wed, 27 Jul 2016 19:49:50 +0200 (CEST)
Subject: Re: How to get feedback on published RFCs [resending as plaintext]
In-Reply-To: <578E14F4.2040000@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Date: Wed, 27 Jul 2016 19:49:50 +0200
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20160727174950.174E01A508@ld9781.wdf.sap.corp>
From: mrex@sap.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a_4VpazEZwYfaM3-bD0ApLGz6_s>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mrex@sap.com
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: Wed, 27 Jul 2016 17:49:55 -0000

Yaron Sheffer wrote:
>
> 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.

For a few years, the front pages of RFCs have been carrying a statement
like this on their front pages:

from RFC7901 (June 2016):

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7901.

from RFC5746 (Feb 2010):

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5746.

and the info on the RFC Editor website says

  Discuss this RFC: Send questions or comments to <....>@ietf.org

giving the IETF WG mailing list address (or rfc-ise@rfc-editor.org)


-Martin

v2.23.0 | Report a Bug | By Email