[rfc-i] Fwd: Call for Comment: RFC Format Drafts
rse at rfc-editor.org (Heather Flanagan (RFC Series Editor)) Fri, 12 February 2016 16:44 UTC
From: "rse at rfc-editor.org"
Date: Fri, 12 Feb 2016 08:44:55 -0800
Subject: [rfc-i] Fwd: Call for Comment: RFC Format Drafts
In-Reply-To: <56BE0834.9030406@gmx.de>
References: <20160211173901.28789.59265.idtracker@ietfa.amsl.com> <56BDFD7B.4020803@rfc-editor.org> <56BE0834.9030406@gmx.de>
Message-ID: <56BE0C07.7070205@rfc-editor.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2/12/16 8:28 AM, Julian Reschke wrote: > On 2016-02-12 16:42, Heather Flanagan (RFC Series Editor) wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> >> Hello all, >> >> In case you missed yesterday's post to regarding the status of the >> format documents, they are now out for community comment. Please >> send comments of support, concern, or other feedback to the IAB >> (iab at iab.org). If you have never posted to that list, it will be >> temporarily held in moderation until your address can be put on >> the white list. >> >> Discussion on specific drafts or requests for clarification can >> always be sent here to rfc-interest or to the draft authors. >> >> Thank you for your time and interest, Heather > > Sending feedback to the IAB list apparently means that it will only > be visible to IAB members. That seems like a very bad idea for public > review. > But it seems to be how IAB stream documents are reviewed. See the announcements, for example, for draft-iab-irtf-chair-descriptions and draft-iab-rfc5741bis. If yo think the IAB process should change, that's something to take up with the IAB. Maybe an open mic question at IETF 95? - -Heather -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWvgwHAAoJEJlIWQlAXuk2eb8P/1aVy8OIJIe0qa1wh8ztpl8i VAbxVcqpBsZmy+AXVLu7h9YaHoO1Bv+OCYSA++C/KMVNxukii66ERcHVu/8kU1Yb rU56sk1ciVWQkJZZv5dXpLKRArPZoxlh8RVP1RQttvuswoLzdYPKbntL6EnjzMOm p/evkMX76pa6CuL+3vP7YCAM4+TSbj7OcFZnoei+lLon2WumfLaFGzJckXlsbSK9 vPomVYIh2ddv4pkQbo0t/kXOD+IdMfBOwR48557oMI161k4SqzH0h2ndGLht5/ka PgursmLSDIyiC1TVZaMzFaWYsKB1u1eAbBSmnJCw1zzyCQkwv7G89MfFtViMHhkL e0TUss2uxaTEGvgjsW/odGgLbScIafm0akYltpRfBKSjALwLmc/DUscJ760Xhb5Q 1GS2DgYkddw8n7h8ZB3PXr7dkBXtZJ394/oxFydOeH3DneNt0PLoOVH856riFv2u 2KZX0cQJ5ST68ZWZK6+czCY4bxJCBWbjS7yWOcHfc+o0pgizVTtwbJTEZgry3luj j8QTTKEX+7Sl2fPb29GNbkHw/wjuX9WW0e08xr465+xhRt9wsFu1kZdoPiSeV7cq /11wVcoxdo2LIAjTYGgReAWpY0ZbxJZnFiOhUE/DQpjvp6+VZpc9/XTBGS15dpPY h5LFtoHB/Od4RLJacGU6 =sR3U -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20160212/ce793d45/attachment.html>
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Julian Reschke
- [rfc-i] Fwd: Call for Comment: RFC Format Drafts Heather Flanagan RFC Series Editor
- [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