The RFC editor has finally released
- K. Murchison, Ed., C. Lindsey, D. Kohn: Netnews Article Format. RFC 5536, November 2009.
- R. Allbery, Ed., C. Lindsey: Netnews Architecture and Protocols. RFC 5537, November 2009.
They obsolete the venerable RFC 1036 (Standard for Interchange of USENET Messages) from December 1987.
The new RFCs are the work of the IETF working group USEFOR, chartered November 1997 and concluded March 2009. I’ve heard it was not quite the longest lived IETF working group ever. (I personally missed the group by a couple of months, since I started following Netnews and NNTP standardization in April, due to Alue.)
Both RFCs are on the Standards Track, currenlty as Proposed Standards. In my opinion, they are a huge improvement over both RFC 1036 and son-of-1036 (which will probably be published as a Historic RFC real soon now).
In May, I posted about the discussion forum software I am writing, Alue. Since then –
- The NNTP interface is essentially complete.
- There is a rudimentary reading and posting HTTPS interface .
- Users are able to self-register, manage their own accounts and reset lost passwords using an email challenge system.
What is broken:
- NNTP control messages.
- MIME message display in HTTPS (including character set conversions)
- Web design. Although – all HTML is template-generated, so it’s more a problem with the test installation than with the actual software.
What is missing:
- HTTPS-based administration
- Spam control
- Email distribution of messages
- Posting by email
- Packaging (including proper installation and upgrade procedures)
And it would probably use a proper security review of the code.
If you are interested, go check out the test installation. The code and the test installation templates are available through Git. If you are really brave (and are a skilled system administrator), you might try creating your own installation – if you do, let me know.