Protocol Action: 'Netnews Architecture and Protocols' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 16 March 2009 16:25 UTC

Return-Path: <owner-ietf-usefor@mail.imc.org>
X-Original-To: ietfarch-usefor-archive@core3.amsl.com
Delivered-To: ietfarch-usefor-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1992F28C1B6 for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 16 Mar 2009 09:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NMrS0Su5574 for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 16 Mar 2009 09:25:04 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id C377128C1DC for <usefor-archive@ietf.org>; Mon, 16 Mar 2009 09:24:48 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n2GGMvt4074348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Mar 2009 09:22:57 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n2GGMvMg074347; Mon, 16 Mar 2009 09:22:57 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n2GGMtgd074339 for <ietf-usefor@imc.org>; Mon, 16 Mar 2009 09:22:56 -0700 (MST) (envelope-from wwwrun@core3.amsl.com)
Received: by core3.amsl.com (Postfix, from userid 30) id 55E6628C1B2; Mon, 16 Mar 2009 09:22:13 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, usefor mailing list <ietf-usefor@imc.org>, usefor chair <usefor-chairs@tools.ietf.org>
Subject: Protocol Action: 'Netnews Architecture and Protocols' to Proposed Standard
Message-Id: <20090316162213.55E6628C1B2@core3.amsl.com>
Date: Mon, 16 Mar 2009 09:22:13 -0700
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>

The IESG has approved the following document:

- 'Netnews Architecture and Protocols '
   <draft-ietf-usefor-usepro-14.txt> as a Proposed Standard

This document is the product of the Usenet Article Standard Update 
Working Group. 

The IESG contact persons are Lisa Dusseault and Alexey Melnikov.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-usefor-usepro-14.txt

     Technical summary:
        This document describes the operational procedures involved
        in running the NetNews service, including the roles of all
        the components of the service. It establishes terminology and
        expectations of behaviour for News servers independent of the
        protocol they use to communicate.
	 This, together with draft-ietf-usefor-usefor, obsoletes RFC
        1036.

     Working group summary:
        The USEFOR working group has been working on this document in
        various versions since 1998. This version was split from
        the -usefor document in 2004. Progress has been slow, and
        contention has erupted over both major and minor matters.
	 The group is now down to a very small size (~5 people), and
        it is not believed that working at this longer will improve
        the document significantly.
	 The WG has consensus that this document is a far better
        specification than RFC 1036.

     Protocol quality
        The specification allows major News implementations to claim
        conformance as-is. Some innovations done in the course of the
        WG's work have been incorporated into existing News servers.
	 The editor is himself a News server implementor.