[rfc-i] Fwd: Call for Comment: RFC Format Drafts
ajs at anvilwalrusden.com (Andrew Sullivan) Fri, 12 February 2016 17:00 UTC
From: ajs at anvilwalrusden.com (Andrew Sullivan)
Date: Fri, 12 Feb 2016 12:00:56 -0500
Subject: [rfc-i] Fwd: Call for Comment: RFC Format Drafts
In-Reply-To: <56BE0D00.3030805@gmx.de>
References: <20160211173901.28789.59265.idtracker@ietfa.amsl.com>
<56BDFD7B.4020803@rfc-editor.org> <56BE0834.9030406@gmx.de>
<56BE0C07.7070205@rfc-editor.org> <56BE0D00.3030805@gmx.de>
Message-ID: <20160212170056.GB66257@mx2.yitter.info>
On Fri, Feb 12, 2016 at 05:49:04PM +0100, Julian Reschke wrote: > Right now I want to make sure that I can actually see *all* feedback related > to the rfc-design activity. That doesn't seem to be the case, and that's a > major process failure. We outlined the way we were going to handle these documents many months ago, and I raised the issue IIRC in Prague in the plenary as well. I don't agree that this is a process failure: these are IAB stream documents and we're handling them in the usual way that IAB stream documents work. I wouldn't argue that the process is perfect, but it has not failed at all. Best regards, A -- Andrew Sullivan ajs at anvilwalrusden.com
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Heather Flanagan RFC Series Editor
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Julian Reschke
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Andrew Sullivan
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Heather Flanagan RFC Series Editor
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Julian Reschke
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Andrew Sullivan