Re: [Tools-discuss] [rfc-i] Fwd: New Version Notification for draft-sheffer-ietf-rfc-annotations-00.txt

Leonard Rosenthol <lrosenth@adobe.com> Mon, 27 June 2016 13:17 UTC

Return-Path: <lrosenth@adobe.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33AFD12D1AA for <tools-discuss@ietfa.amsl.com>; Mon, 27 Jun 2016 06:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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=adobe.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 31DOZs35SiwF for <tools-discuss@ietfa.amsl.com>; Mon, 27 Jun 2016 06:17:36 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0099.outbound.protection.outlook.com [207.46.100.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7C1712D1A1 for <tools-discuss@ietf.org>; Mon, 27 Jun 2016 06:17:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adobe.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qWKsRyYLI9voXfg29YpfrntlxPdGfKSPxxshqGKHe7M=; b=uwKEIsJfyZjFOyo/XNjoL80MU4pr8bRkVOZwj+6KdrixTCPYjnqDmaiggy3iQdNvN6vZwoQVyY7AduULFu2fPC3lhfA90KPJ0y5/fYydUH/N2iPbMArJ54R+GdY1sOk6ocrY5a8g9tAIUCH57QuT8nF8zMNvMy9Ziwk+k+eD8J4=
Received: from BLUPR0201MB1505.namprd02.prod.outlook.com (10.163.119.16) by BLUPR0201MB1507.namprd02.prod.outlook.com (10.163.119.18) with Microsoft SMTP Server (TLS) id 15.1.517.8; Mon, 27 Jun 2016 13:17:33 +0000
Received: from BLUPR0201MB1505.namprd02.prod.outlook.com ([10.163.119.16]) by BLUPR0201MB1505.namprd02.prod.outlook.com ([10.163.119.16]) with mapi id 15.01.0517.016; Mon, 27 Jun 2016 13:17:33 +0000
From: Leonard Rosenthol <lrosenth@adobe.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, "tools-discuss@ietf.org" <tools-discuss@ietf.org>
Thread-Topic: [rfc-i] Fwd: New Version Notification for draft-sheffer-ietf-rfc-annotations-00.txt
Thread-Index: AQHRzwwby+qDzdzQH0O4SGZe2r5OYp/7dM4AgAFUYICAAEIxAA==
Date: Mon, 27 Jun 2016 13:17:32 +0000
Message-ID: <756B81DD-D007-454C-9936-5FED0F0E244D@adobe.com>
References: <20160625175547.17196.37166.idtracker@ietfa.amsl.com> <576EC7C4.6010905@gmail.com> <77E7F840-7485-4D1E-A00D-2B5B3D33B763@adobe.com> <5770B7A5.2080400@gmail.com>
In-Reply-To: <5770B7A5.2080400@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.17.0.160611
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lrosenth@adobe.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2601:80:4103:99a0:1610:9fff:fed8:e65f]
x-ms-office365-filtering-correlation-id: 8fc30278-178c-4997-7eb5-08d39e8d6649
x-microsoft-exchange-diagnostics: 1; BLUPR0201MB1507; 6:dGN7QFwEZnkE3TsqV3GO3izqTEdHuwQ1W8dmLiBzcyqlfm09lsb+fEaBGdBQs7S/xB9E6rXD+kw0wWkqewIbS+iULNW+FpbvBP6SKbnQle+kWZibehqDcpVriYQFSu4/+mAen2FfayCXBnzNjuzc3IpYqu2UCD9LlQm9zlk6FUwItjFFJtcDRXwDG1T/NoSMqfbvGrzGy0ySV1P2DBnCHDz47TA5zjUy57Fp6behQZ2fiavskUXVYOueLk7ZjFtJXQpmQYHqpdY2NHhVnT/wJIHoX27Bgf0hyW4Bah1FqJ0dCIwbKB1M19wCvVVM33SfezJZRRwZh2GcdMvtSl4CVeN0PKaRbh9paXLvhk5fNac=; 5:FXufXJNTNzLOTD7iIIDeucaeed6/tT1Y2SOnA++POZr8HvZrMraSzm4csk/60O63gXVcPANQYIgE55IswX3iFiZFOm0Ugp2DILUD6p5uP5BFemvBxiW4e88nkQPYWkWBYUVpaAB9iTnBnrXdT556Qw==; 24:k0WtEhkXEQ5T9iBqXWnA7Z9LuEG+xObT6X942HyNREJwk2gpltITvaxyfPZhVriN+qvqFhpZpdbfGfbmunHE8sG1KytWhNUl5ho24N7CMx4=; 7:BmO7Q0CCx7sbKaaLcb1n1wYMSXBdorezqf5SWHYsHk26ZqrgXEcosAPjemdNZsYhjmbCniGEFcnnDw71OVG/4uRzbthH1a/WZpPDPgA0YMwKmkY267SRl7is+RdKn47qkJk3augzWa8ogArTLFGaj4BMF9TbsPnl2eiXZBrHErMzqj5qYV4tiO8K6NDGY9Sx6DLKEr4ZTtlYJ6rjbqB718FyPc4+exzpQRw0cD40JammMsUcTGnsPSApqpo3TONY
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0201MB1507;
x-microsoft-antispam-prvs: <BLUPR0201MB1507DFD6C83EC96AC2C4127DCD210@BLUPR0201MB1507.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(120809045254105)(176510541525296);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038); SRVR:BLUPR0201MB1507; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0201MB1507;
x-forefront-prvs: 09860C2161
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(2473001)(24454002)(377454003)(199003)(189002)(377424004)(92566002)(8936002)(189998001)(5001770100001)(97736004)(586003)(107886002)(93886004)(68736007)(106356001)(106116001)(105586002)(19580395003)(305945005)(2906002)(19580405001)(4001350100001)(5002640100001)(33656002)(230783001)(2201001)(83506001)(122556002)(87936001)(86362001)(101416001)(83716003)(36756003)(77096005)(15975445007)(50986999)(76176999)(82746002)(54356999)(2900100001)(2950100001)(6116002)(102836003)(15650500001)(99286002)(7736002)(7846002)(3660700001)(3280700002)(2501003)(11100500001)(81166006)(81156014)(10400500002)(8676002)(10090500001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR0201MB1507; H:BLUPR0201MB1505.namprd02.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; CAT:NONE; LANG:en; CAT:NONE;
received-spf: None (protection.outlook.com: adobe.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <AD30E9831B28C84785209926C23366EF@namprd02.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Jun 2016 13:17:33.2031 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fa7b1b5a-7b34-4387-94ae-d2c178decee1
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0201MB1507
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/qUCKYgZY7YsJ601BnnE3FLJVgzI>
Subject: Re: [Tools-discuss] [rfc-i] Fwd: New Version Notification for draft-sheffer-ietf-rfc-annotations-00.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2016 13:17:41 -0000

And that that IETF would run the server and thus “own” the comments, would also seem to be reasonable as well.

We would also need to reconcile the various formats – in case someone commented on the PDF and another person onteh HTML – you’d want to see both.

Leonard

On 6/27/16, 1:20 AM, "Yaron Sheffer" <yaronf.ietf@gmail.com> wrote:

Hi Leonard,

I think an initial "shipping" solution would be mostly around identity: 
allowing users to register with their IETF or some other, federated 
identity instead of having to register with an external service.

Thanks,
	Yaron

On 26/06/16 16:02, Leonard Rosenthol wrote:
> As an experiment, this seems perfectly reasonable.  (not sure what the “shipping” solution would look like – but can’t hurt anything to try out)
>
> Leonard
>
> On 6/25/16, 2:04 PM, "rfc-interest on behalf of Yaron Sheffer" <rfc-interest-bounces@rfc-editor.org on behalf of yaronf.ietf@gmail.com> wrote:
>
> Hi,
>
> I have posted a short draft that proposes to open the "tools" version of
> RFCs up, by allowing readers can annotate them. The goal is to provide
> us with feedback and encourage discussion of these documents outside the
> "walls" of the IETF.
>
> If you will, this is another way to reach out to the broader community,
> as this recent draft [1] suggests.
>
> I would appreciate your comments!
>
> Thanks,
> 	Yaron
>
>
> [1] https://tools.ietf.org/html/draft-arkko-ietf-trends-and-observations-00
>
> -------- Forwarded Message --------
> Subject: New Version Notification for
> draft-sheffer-ietf-rfc-annotations-00.txt
> Date: Sat, 25 Jun 2016 10:55:47 -0700
> From: internet-drafts@ietf.org
> To: Yaron Sheffer <yaronf.ietf@gmail.com>
>
>
> A new version of I-D, draft-sheffer-ietf-rfc-annotations-00.txt
> has been successfully submitted by Yaron Sheffer and posted to the
> IETF repository.
>
> Name:		draft-sheffer-ietf-rfc-annotations
> Revision:	00
> Title:		Requesting Comments: Enabling Readers to Annotate RFCs
> Document date:	2016-06-25
> Group:		Individual Submission
> Pages:		6
> URL:
> https://www.ietf.org/internet-drafts/draft-sheffer-ietf-rfc-annotations-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-sheffer-ietf-rfc-annotations/
> Htmlized:
> https://tools.ietf.org/html/draft-sheffer-ietf-rfc-annotations-00
>
>
> Abstract:
>      RFCs were initially intended as, literally, requests for comments.
>      Since then, they have turned into standards documents, with a
>      peculiar process to report errors and a highly onerous process to
>      actually have the RFC modified/republished.  Non-IETF participants
>      are typically unaware of any way to provide feedback to published
>      RFCs, other than direct email to the listed authors.  This is very
>      different from the way many web specifications are developed today
>      and arguably leads to the value of published RFCs diminishing over
>      time.  This document proposes an experiment to remedy this situation
>      through the deployment of web annotations.
>
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>
>