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

yaronf.ietf at gmail.com (Yaron Sheffer) Mon, 27 June 2016 05:20 UTC

From: "yaronf.ietf at gmail.com"
Date: Mon, 27 Jun 2016 08:20:37 +0300
Subject: [rfc-i] Fwd: New Version Notification for draft-sheffer-ietf-rfc-annotations-00.txt
In-Reply-To: <77E7F840-7485-4D1E-A00D-2B5B3D33B763@adobe.com>
References: <20160625175547.17196.37166.idtracker@ietfa.amsl.com> <576EC7C4.6010905@gmail.com> <77E7F840-7485-4D1E-A00D-2B5B3D33B763@adobe.com>
Message-ID: <5770B7A5.2080400@gmail.com>

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 at rfc-editor.org on behalf of yaronf.ietf at 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 at ietf.org
> To: Yaron Sheffer <yaronf.ietf at 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 at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>
>