Hi Abdussalam,
The IAB Chair asked for comments to be sent to
rfc-interest@xxxxxxxxxxxxxx (
http://www.ietf.org/mail-archive/web/ietf/current/msg86439.html ). I
assume that the reason is because the topic is about a RFC matter and
not a matter specific to the IETF.
At 18:45 04-03-2014, Abdussalam Baryun wrote:
The draft should consider reader styles then present author styles
and then RFC best practice style. I don't think the funny RFC is a
best practice style.
The style guide is the set of guidelines used by the RFC Editor. It
describes, for example, some formatting rules, reference style, etc.
One of the important issue of document styles, is the each style
purpose or benefit to all readers. Documents are for readers and
mostly new readers. RFCs should consider new readers, especially the
funny RFCs (in some cultures they may not think that style is funny).
I guess that what the above is trying to say is that a joke might not
be considered as funny in every part of the world.
IMHO , The RFC editor output general style should change to
welcome/match more reader styles. Authors should not do documents
without clarifying purpose of their writing style. Furthermore,
editors should motivate their document to easy readings to
understanding. Comment below,
The above would be about target audience. As an example, there can
be assumption that the average reader will have some familiarity with
the topic being discussed in a RFC.
Why not? If the RFC are not for users to benefit and easy understand
then why not categorising?
The style guide is about how to write a draft so that it is easier
for the RFC Editor to publish it. It is not about categories, e.g.
whether the document should be a "Proposed Standard" or whether
satirical material can be published as a RFC.
Regards,
-sm