Re: How to get feedback on published RFCs

S Moonesamy <sm+ietf@elandsys.com> Tue, 19 July 2016 12:58 UTC

Return-Path: <sm@elandsys.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 4156512D81B for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 05:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.077
X-Spam-Level:
X-Spam-Status: No, score=-3.077 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=3lMV1HNs; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=VYfbFkoc
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 HgLvG-OW0qAj for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 05:58:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3590512D7E3 for <ietf@ietf.org>; Tue, 19 Jul 2016 05:56:00 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.147.114]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u6JCtiIJ013045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jul 2016 05:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1468932958; x=1469019358; bh=R166h/aK0ZvrFswflp/qjtxPhvfiiuAmuyIXTXGzma4=; h=Date:To:From:Subject:In-Reply-To:References; b=3lMV1HNsvttXFGFJKi4FBYjZ/tptNvRrDx2wcyw+Dfoes+s3S8Q4jUf4dTU10dsrk HafHzub6vEmLJkL38FX2OnSpLJht88pQCn3KCcFnQiu87TDHp0BRTRcXV/5HeSDYqe 1FRUdWhk1TQScpKW3JxcqUh2RyqlEjr8pHVcGw+A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1468932958; x=1469019358; i=@elandsys.com; bh=R166h/aK0ZvrFswflp/qjtxPhvfiiuAmuyIXTXGzma4=; h=Date:To:From:Subject:In-Reply-To:References; b=VYfbFkocqrTWzt5HSSkIf5lvfJyOK/C00g6+79JUeuz+Z3Cm7hROsfEFWCuWdI+LL VjTm5y9iBJ3JheZiaSbgkhVlkknk1L/r1x5Y9KoEizU4kgPIWAHnKAF++ryPXFmmrC 9H6RQ98tBncr4SuQ6JFfYcMyX7L083RUqghF2f0o=
Message-Id: <6.2.5.6.2.20160719051627.0a161790@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 19 Jul 2016 05:49:36 -0700
To: Yaron Sheffer <yaronf.ietf@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: How to get feedback on published RFCs
In-Reply-To: <578DF452.70107@gmail.com>
References: <578DF452.70107@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jUj69ItypYC6TRJE8a4aR2I0poI>
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 12:58:50 -0000

Hi Yaron,
At 02:35 19-07-2016, 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.

[snip]

>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 recall that this has been discussed 
before.  draft-sheffer-ietf-rfc-annotations-00 is proposing an IETF 
process experiment to enable web annotations on published 
RFCs.  Would that cover RFCs published in the IAB Stream?

As the proposed experiment identifies "tools" RFCs, it shouldn't 
affect the archival series.  Section 4.1 mentions that there is room 
for abuse.  I read some negative comments on the web about a RFC 
which I edited.  In my opinion it is fair criticism.

Regards,
S. Moonesamy