Re: How to get feedback on published RFCs
Alessandro Vesely <vesely@tana.it> Tue, 19 July 2016 17:16 UTC
Return-Path: <vesely@tana.it>
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 8119E12D7F4 for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 10:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.589
X-Spam-Level:
X-Spam-Status: No, score=-5.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tana.it
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 KB6ief1DRLKu for <ietf@ietfa.amsl.com>; Tue, 19 Jul 2016 10:16:54 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF86112D091 for <ietf@ietf.org>; Tue, 19 Jul 2016 10:16:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1468948610; bh=ZKmlbEJv7MqHIIMCHSzXFWKaAw8yvOpqsEl3dSNeNkM=; l=1007; h=To:References:From:Date:In-Reply-To; b=cBaYfVyFAHdfvGcDWzZ/F/nF4/2DNU+uxHVvaKCp3yTWR1mtRDetscoY1Acb5BXGc jh0azwL8zzZidL0yOTM7VFN5zocfdGwRChLT5nKqG3pOA11TKmJaCSAfLsU46VIh1/ SOT3W93VXywdb1AYbMALqzNrZC8EMabxT6VFq17Y=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Tue, 19 Jul 2016 19:16:50 +0200 id 00000000005DC033.00000000578E6082.00007D47
Subject: Re: How to get feedback on published RFCs
To: S Moonesamy <sm+ietf@elandsys.com>, Yaron Sheffer <yaronf.ietf@gmail.com>, ietf@ietf.org
References: <578DF452.70107@gmail.com> <6.2.5.6.2.20160719051627.0a161790@resistor.net>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <2c9808c0-7b5f-8e32-c5c0-07f5a6f4521a@tana.it>
Date: Tue, 19 Jul 2016 19:16:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20160719051627.0a161790@resistor.net>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yu3tsICz2tKZZZo1awpzFmji174>
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 17:16:56 -0000
On Tue 19/Jul/2016 14:49:36 +0200 S Moonesamy wrote: > At 02:35 19-07-2016, Yaron Sheffer wrote: > >> 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. I recall a 2012 occasion[*] where I asked for a better tool than errata held for document revision. [*] https://www.ietf.org/mail-archive/web/ietf-smtp/current/msg07284.html > As the proposed experiment identifies "tools" RFCs, it shouldn't affect the > archival series. Annotations are stored separately. In principle, notes sticked to a given URL can be displayed anywhere. Ale
- Re: How to get feedback on published RFCs S Moonesamy
- Re: How to get feedback on published RFCs Alessandro Vesely
- Re: How to get feedback on published RFCs Yaron Sheffer
- Re: How to get feedback on published RFCs S Moonesamy
- Re: How to get feedback on published RFCs Kathleen Moriarty
- How to get feedback on published RFCs Yaron Sheffer