Netnews Administration System (NAS)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: RFC Editor <email@example.com> Cc: The IESG <firstname.lastname@example.org>, <email@example.com>, firstname.lastname@example.org Subject: Re: Experimental RFC to be: draft-dfncis-netnews-admin-sys-08.txt The IESG has no problem with the publication of 'Netnews Administration System (NAS)' <draft-dfncis-netnews-admin-sys-08.txt> as an Experimental RFC. The IESG would also like the IRSG or RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=5009&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Scott Hollenbeck. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-dfncis-netnews-admin-sys-08.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
Technical Summary The Netnews Administration System (NAS) is a framework to simplify the administration and usage of network news (also known as Netnews) on the Internet. Data for the administration of newsgroups and hierarchies are kept in a distributed hierarchical database and are available through a client-server-protocol. Working Group Summary This document is an individual submission requested for publication through the RFC Editor. It is not the product of an IETF working group. Protocol Quality Ned Freed and Scott Hollenbeck reviewed this specification for the IESG. IESG Note The IESG thinks that this work is related to IETF work done in the nntpext and usefor working groups, but this does not prevent publishing. The IESG asks to have the following IESG Note included in the document: This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose, and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment.