[ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"

On Mar 16, 2013, at 2:20 PM, Gerry Demaret <ml+ripe-list at x-net.be> wrote:

>  * The RFC style guide [1] could be a good base. Replace ASCII with
>    UTF-8, remove the paging requirement and perhaps some other bits
>    and pieces we don't need and I think we could be there.
>    Having very similar guidelines as other major organizations does
>    seem like a big plus to me.
> 
[...]
> [1] http://www.rfc-editor.org/rfc-style-guide/rfc-style





FYI (and since it is fun to sign with a specific job-title), 

Note that the RFC Editor has just finished gathering requirements on how to evolve the series to deal with i18n issues and inclusion of diagrams (the document is approved for publication as RFC last week).

http://tools.ietf.org/html/draft-iab-rfcformatreq-03

The RFC community is probably a little conservative as the RFC Series is an 'archival series'. But that draft documents some pros and cons. The issues that Gerry lists above can be found in the requirements draft.


--Olaf Kolkman
  former ARSE (Acting RFC Series Editor)





NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf at NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/ncc-services-wg/attachments/20130318/f9b40890/attachment.html>