[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf
Subject:    RE: RFC production center XML format usage, was: [IAOC] xml2rfc	and
From:       "Worley, Dale R (Dale)" <dworley () avaya ! com>
Date:       2011-02-24 22:09:54
Message-ID: CD5674C3CD99574EBA7432465FC13C1B220B5C14FC () DC-US1MBEX4 ! global ! avaya ! com
[Download RAW message or body]

> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Paul Hoffman [paul.hoffman@vpnc.org]
> 
> So, I suspect that the large percentage of the non-00 drafts getting
> kicked back are due to the IETF Trust requirements changing over
> time. We can argue (and have argued!) about all that, but I think
> saying "idnits" is likely just shooting the messenger.

I wouldn't be surprised.  And although "idnits" catches the bullets
that should be aimed elsewhere, it is where the problem is discovered.
In a perfect world, we would ensure that the users are educated enough
that they can discern the correct entity to blame and file their
reports correctly.  But in the real world, the target audience turns
over fast enough that (collectively) it cannot learn.  So would be
more effective if the necessary information is presented to the user
at the moment the problem becomes evident.

Dale
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
[prev in list] [next in list] [prev in thread] [next in thread]