Re: How to get feedback on published RFCs

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 19 July 2016 13:33 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 4F7AB12B071 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 06:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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] 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 vHzJARrgmFyh for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 06:33:15 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 69ADC12DED7 for <ietf@ietf.org>; Tue, 19 Jul 2016 06:12:31 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id f65so138478673wmi.0 for <ietf@ietf.org>; Tue, 19 Jul 2016 06:12:31 -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=YQeIFgTePTSQ50bk8en2u0YC7a5WZQ8JW1Qc9Vvu/fw=; b=O7FLlwuJkJL0YxWfW+0k6ndbPd36Wj2GNWYmlJrett0T5AXXX3CJDqpmGTZuQUIOUy NQ8h5lTdfF3cB/WfsZ7VPp7wCp1EM5EppnEIqhvaD7TUhLh4X6pIQytOcJAUW2U8sGLN JPTzuRORJeb2tnCq8Td+FBTJzaFa5Stj1lcTArNraJU6Vl21XiaIiySj36XtTKI0AZus Tj3bjxzqVPMs1w78Q7tLJTX6RDQgynaG8oQnrJ6juFEwRqSflkJpG8Y96vBR8rT0Rq4N eaKg1HuiMSucVj5kdAb7kfxidBAvRFeOg1w48qUTihErkMuQQZXbwkIHH6+Hm9iyRsu0 IhBQ==
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=YQeIFgTePTSQ50bk8en2u0YC7a5WZQ8JW1Qc9Vvu/fw=; b=VBcMApkUAD/JHga4Pxi4tXvIkL6lvBKSu7jk39ivTqQ77xXMD0/bJHRkYr/iG7rE1L CEMObOMIY35Kkr1eeXv5HCxVm74wPMiq2itYnK6U6x9gd29MCNlHOFuvNQO0abMgperF Nhry7u5wbye1Ri5Dg2hyU/QVIS6glcpLnAq3hbG5neQwLfl7g9NJhnkEUBGMNAsxXCE6 qetM5QLjvJT+FiyMP2JJiuNmJgp4XmVx9LibAoKe7Up5rJBjhLk4OE2srsb22eV2w2P3 kHQMFSHhxl00wIpQ9a1e1PFYFbmEq3aIaqUz3pWGWmR5b+sAo7hEQD/qhgni0sKGC+zW 5hqQ==
X-Gm-Message-State: ALyK8tL9DvMt10UZsPlT6DNZ7mvAOea91l0RHv1AepzS+0HbE3Urmu0//jKxxgEhKXkRSg==
X-Received: by 10.28.14.75 with SMTP id 72mr4118693wmo.85.1468933949614; Tue, 19 Jul 2016 06:12:29 -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 i8sm5400621wmg.21.2016.07.19.06.12.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jul 2016 06:12:28 -0700 (PDT)
Subject: Re: How to get feedback on published RFCs
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
References: <578DF452.70107@gmail.com> <6.2.5.6.2.20160719051627.0a161790@resistor.net>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <578E273C.1000202@gmail.com>
Date: Tue, 19 Jul 2016 15:12:28 +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: <6.2.5.6.2.20160719051627.0a161790@resistor.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/htiawsJyjWO2UGBaBV47qyRqR9k>
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 13:33:20 -0000

On 19/07/16 14:49, S Moonesamy wrote:
> 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?

Yes, the current proposal would cover all published RFCs.

>
> As the proposed experiment identifies "tools" RFCs, it shouldn't affect
> the archival series.

This is correct.

   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