[rfc-i] RFC Editor Report to the IETF
Brian E Carpenter
brian.e.carpenter at gmail.com
Wed Jul 29 15:01:16 PDT 2009
It isn't ISOC. It's the inconsistency between the regime created
by RFC5378 and the desired practice for the non-IETF RFC streams.
But yes, it's urgent, and people are working on resolving it ASAP.
I'll let others speak to the details.
On 2009-07-30 01:45, Joe Touch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> RFC Editor wrote:
>> The RFC Editor report to the IETF is available at
>> Please let us know if you have any questions.
> I would like to call on the ISOC to release the independent stream
> queue. It has been on hold since October 2008.
> I urge the ISOC to allow publication of these documents immediately. If
> new terms have not been determined, then publish them under the terms at
> the time they were submitted.
> Can we please take whatever steps are necessary to get this queue unstuck?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
More information about the rfc-interest