I have people working for me who write I-Ds, and who HATE the ASCII
format that they are forced to use. So much so, that they have threatened
never to write another I-D. Do we want to deprive the IETF community of the
input of experienced technical people ( and, yes, they ARE ! ), because they
are put off by archaic document formats ?
So it is not just "people who neither write RFC's nor implement
protocols" who find ASCII "incomplete".
Perhaps we ( the IETF ) should have a library of standard,
downloadable translation / formatting tools that would help people to write
in whatever format they choose, then convert it to the required ASCII.
However, this would still not solve the problem os ASCII's poor diagram
From: Vernon Schryver [SMTP:vjs(_at_)calcite(_dot_)rhyolite(_dot_)com]
Sent: Monday, February 26, 2001 8:54 PM
Subject: Re: HTML better for small PDAs
If the ASCII version of an RFC is complete, then the XML alternate is
not needed. If the alternate is needed even only for "illustration",
then the ASCII version is incomplete and so wrong. As others have
said "incomplete" as seen by people who neither write RFC's nor
implement protocols is completely irrelevant and inadmissible.
As someone else pointed out, the crux of this recurring thread
is the conflict between those who care about the form of RFC's
including whether they use "modern technology" and those who care
about the contents and function of RFC's as definitions of protocols.
It seems clear that some of those who are adamant about
replacing boring old ASCII are more readers than authors or editors.
Worse, I suspect a few have not spent much time reading the ASCII stuff
and would read little in any format, not matter how modern.
Vernon Schryver vjs(_at_)rhyolite(_dot_)com