[rfc-dist] RFC 4707 on Netnews Administration System (NAS)

[rfc-editor at rfc-editor.org ([e-mail])]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4707

        Title:      Netnews Administration System (NAS) 
        Author:     P. Grau, V. Heinau,
                    H. Schlichting, R. Schuettler
        Status:     Experimental
        Date:       October 2006
        Mailbox:    nas at fu-berlin.de, 
                    nas at fu-berlin.de, 
                    nas at fu-berlin.de,  nas at fu-berlin.de
        Pages:      49
        Characters: 86510
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-dfncis-netnews-admin-sys-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4707.txt

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.

The database is accessible by news servers, news administrators, and
news readers.  News servers can update their configuration
automatically; administrators are able to get the data manually.  News
reader programs are able to get certain information from an NAS
server, automatically or at a user's discretion, which provides detailed
information about groups and hierarchies to the user.

NAS is usable in coexistence with the current, established process of
control messages; an unwanted interference is impossible.
Furthermore, NAS is able to reflect the somewhat chaotic structure of
Usenet in a hierarchical database.  NAS can be used without
modification of existing news relay, news server, or news reader
software; however, some tasks will be better accomplished with
NAS-compliant software.  This memo defines an Experimental Protocol for the Internet community.


EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet 
community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.  Distribution 
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...