RFC 5537 on Netnews Architecture and Protocols
rfc-editor@rfc-editor.org Sun, 29 November 2009 05:16 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 A64B23A6925 for <ietfarch-usefor-archive@core3.amsl.com>; Sat, 28 Nov 2009 21:16:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.931
X-Spam-Level:
X-Spam-Status: No, score=-3.931 tagged_above=-999 required=5 tests=[AWL=1.515, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4]
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 H24r+aOyRb2u for <ietfarch-usefor-archive@core3.amsl.com>; Sat, 28 Nov 2009 21:16:45 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 85AA23A68E9 for <usefor-archive@ietf.org>; Sat, 28 Nov 2009 21:16:45 -0800 (PST)
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 nAT5EnIP027709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 28 Nov 2009 22:14:49 -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 nAT5EnoV027708; Sat, 28 Nov 2009 22:14:49 -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 bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nAT5EmLw027701 for <ietf-usefor@imc.org>; Sat, 28 Nov 2009 22:14:48 -0700 (MST) (envelope-from rfc-editor@rfc-editor.org)
Received: by bosco.isi.edu (Postfix, from userid 70) id B8C6837776C; Sat, 28 Nov 2009 21:09:17 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5537 on Netnews Architecture and Protocols
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ietf-usefor@imc.org
Message-Id: <20091129050917.B8C6837776C@bosco.isi.edu>
Date: Sat, 28 Nov 2009 21:09:17 -0800
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>
A new Request for Comments is now available in online RFC libraries.
RFC 5537
Title: Netnews Architecture and Protocols
Author: R. Allbery, Ed.,
C. Lindsey
Status: Standards Track
Date: November 2009
Mailbox: rra@stanford.edu,
chl@clerew.man.ac.uk
Pages: 48
Characters: 120366
Obsoletes: RFC1036
I-D Tag: draft-ietf-usefor-usepro-14.txt
URL: http://www.rfc-editor.org/rfc/rfc5537.txt
This document defines the architecture of Netnews systems and
specifies the correct manipulation and interpretation of Netnews
articles by software that originates, distributes, stores, and
displays them. It also specifies the requirements that must be met
by any protocol used to transport and serve Netnews articles.
[STANDARDS TRACK]
This document is a product of the Usenet Article Standard Update Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute