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

Yaron Sheffer <yaronf.ietf@gmail.com> Mon, 27 June 2016 05:20 UTC

Return-Path: <yaronf.ietf@gmail.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 34A1412B029 for <tools-discuss@ietfa.amsl.com>; Sun, 26 Jun 2016 22:20:45 -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 fF_CLuSEFHSx for <tools-discuss@ietfa.amsl.com>; Sun, 26 Jun 2016 22:20:43 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 CC0F112B027 for <tools-discuss@ietf.org>; Sun, 26 Jun 2016 22:20:42 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id r201so97832215wme.1 for <tools-discuss@ietf.org>; Sun, 26 Jun 2016 22:20:42 -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=IrxDo2pc08j1dL/db4FNacHbXlzhqLB63pWyg1+jbtk=; b=Cx64fdwGtd5qyK5ud3QXUvIN4YybgRKU4/Plfreky+vwBpG6bZ8VJ7HVGYKSYYR/6n qqT+/F2l3LQBBcF3eGsV0/rJpNB2nnl1PwZQOg2ZwnQN11AOtE2S+DaDvZ2jKVu7Wnr0 3iD+5t2lVw4EOAzOqkhzFWBZwIEQxajdgmUi6TrviI6GIvcRTyzx2krYaWsgQq7fRLE/ pn2oI8y4g8/Pt8PhCXs+kfgmfydOw8dHJDgCmTF7oPbSnfy70SBIocSDoS8Y3tSck/Cq Ft0MWzKm2rsqJ74VsjVCsaa9Bc8y9NJBXivHBIamYC4YwzFg2R35H6wQtieeyjjcMDv4 G44A==
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=IrxDo2pc08j1dL/db4FNacHbXlzhqLB63pWyg1+jbtk=; b=TzgkXtyDG6uiI9Jyj/yeTrA/Ni1Cz+SJ9APfV7crUwVKb7hauz/y1Fma3CC/6JPfCk eINwXFZfS3hePKjjRg8X7i2i4Eb/5x9Oqs8/uCBH2HgETaOhUP+Uowz8MluQ5C6ZI/eT UcdpVoUiP4urgJnO3QzG3WUYOxzEzLHdmTJF6qyLQ/9eDzofGG8b1/0zoT3Qh4LuX3St f11JHewXQ4DD7SWKg7eq6YTcRbPRUIG4E29HFAKtHEWwOOz0jUjgN1sZj2ov783fQRMn pSgPIj6He/uq6vsPTYBJ5y8TcKQye4qRQNXDqfLIRCTtU6nZcUlyoywEorZpifKlLU+r NVRg==
X-Gm-Message-State: ALyK8tJqHPSKYG6yMIVIkvRI6ZdaQcADpYcwQK/t0NNq2YXBkBh/wgk6x347IbnWcg8Wmw==
X-Received: by 10.194.134.230 with SMTP id pn6mr13744197wjb.165.1467004841271; Sun, 26 Jun 2016 22:20:41 -0700 (PDT)
Received: from [10.0.0.9] (bzq-109-67-2-59.red.bezeqint.net. [109.67.2.59]) by smtp.gmail.com with ESMTPSA id e16sm6206357wma.12.2016.06.26.22.20.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Jun 2016 22:20:40 -0700 (PDT)
To: Leonard Rosenthol <lrosenth@adobe.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, "tools-discuss@ietf.org" <tools-discuss@ietf.org>
References: <20160625175547.17196.37166.idtracker@ietfa.amsl.com> <576EC7C4.6010905@gmail.com> <77E7F840-7485-4D1E-A00D-2B5B3D33B763@adobe.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <5770B7A5.2080400@gmail.com>
Date: Mon, 27 Jun 2016 08:20:37 +0300
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: <77E7F840-7485-4D1E-A00D-2B5B3D33B763@adobe.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/kB7kLi2zDSGrvqXtuFV-F7LI0Z0>
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 05:20:45 -0000

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
>
>