[Technical Errata Reported] RFC5537 (1983)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 28 December 2009 13:52 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 A63203A65A6 for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 28 Dec 2009 05:52:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.714
X-Spam-Level:
X-Spam-Status: No, score=-3.714 tagged_above=-999 required=5 tests=[AWL=1.249, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, URIBL_RHS_DOB=1.083]
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 eSiJh7kRkkhz for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 28 Dec 2009 05:52:19 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 73E113A659A for <usefor-archive@ietf.org>; Mon, 28 Dec 2009 05:52:19 -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 nBSDjm2L009686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Dec 2009 06:45:48 -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 nBSDjm7K009685; Mon, 28 Dec 2009 06:45:48 -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 boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nBSDjjXA009677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-usefor@imc.org>; Mon, 28 Dec 2009 06:45:45 -0700 (MST) (envelope-from web-usrn@ISI.EDU)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id nBSDhHKR018792; Mon, 28 Dec 2009 05:43:18 -0800 (PST)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id nBSDhHRJ018791; Mon, 28 Dec 2009 05:43:17 -0800 (PST)
Date: Mon, 28 Dec 2009 05:43:17 -0800
Message-Id: <200912281343.nBSDhHRJ018791@boreas.isi.edu>
To: rra@stanford.edu, chl@clerew.man.ac.uk, lisa.dusseault@gmail.com, alexey.melnikov@isode.com, alexey.melnikov@isode.com, harald@alvestrand.no
Subject: [Technical Errata Reported] RFC5537 (1983)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ah@TR-Sys.de, ietf-usefor@imc.org, rfc-editor@rfc-editor.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
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 following errata report has been submitted for RFC5537, "Netnews Architecture and Protocols". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5537&eid=1983 -------------------------------------- Type: Technical Reported by: Alfred Hoenes <ah@TR-Sys.de> Section: GLOBAL Original Text ------------- (a) Section 3.10, first paragraph: A gateway transforms an article into the native message format of another medium, or translates the messages of another medium into news articles, or transforms articles into proto-articles for injection into a separate Netnews network. Encapsulation of a news | article into a message of MIME type application/news-transmission, or the subsequent undoing of that encapsulation, is not gatewaying since it involves no transformation of the article. (b) Section 4 (page 29): | The updated MIME media type definition of message/news is: | MIME type name: message | MIME subtype name: news Required parameters: ... (c) Section 4.1 (bottom of page 30): | The MIME media type definition of application/news-transmission is: | MIME type name: application | MIME subtype name: news-transmission Required parameters: ... (d) Section 4.2 (bottom of page 31 plus top of page 32): | The MIME media type definition of application/news-groupinfo is: | MIME type name: application | MIME subtype name: news-groupinfo Required parameters: none Optional parameters: charset, which MUST be a charset | registered for use with MIME text types. It has the same syntax as the parameter defined for text/plain [RFC2046]. [...] (e) Section 4.3 (page 33): | The MIME media type definition of application/news-checkgroups is: | MIME type name: application | MIME subtype name: news-checkgroups Required parameters: none Optional parameters: charset, which MUST be a charset | registered for use with MIME text types. It has the same syntax as the parameter defined for text/plain [RFC2046]. Corrected Text -------------- (a) Section 3.10, first paragraph: A gateway transforms an article into the native message format of another medium, or translates the messages of another medium into news articles, or transforms articles into proto-articles for injection into a separate Netnews network. Encapsulation of a news | article into a message of media type application/news-transmission, or the subsequent undoing of that encapsulation, is not gatewaying since it involves no transformation of the article. (b) Section 4 (page 29): | The updated media type definition of message/news is: | Type name: message | Subtype name: news Required parameters: ... (c) Section 4.1 (bottom of page 30): | The media type definition of application/news-transmission is: | Type name: application | Subtype name: news-transmission Required parameters: ... (d) Section 4.2 (bottom of page 31 plus top of page 32): | The media type definition of application/news-groupinfo is: | Type name: application | Subtype name: news-groupinfo Required parameters: none Optional parameters: charset, which MUST be a charset | registered for use with 'text' media types. It has the same syntax as the parameter defined for text/plain [RFC2046]. [...] (e) Section 4.3 (page 33): | The media type definition of application/news-checkgroups is: | Type name: application | Subtype name: news-checkgroups Required parameters: none Optional parameters: charset, which MUST be a charset | registered for use with 'text' media types. It has the same syntax as the parameter defined for text/plain [RFC2046]. Notes ----- Rationale: RFC 5537 does not follow the IETF standard terminology reinforced by RFC 4288 and does not properly use the media type registration template from Section 10 of RFC 4288. RFC 4288 clarifies that IETF media types (and subtypes) have outgrown the Internet Email MIME environment and now are used in non-email environments as well; for instance in the context of Netnews (this RFC!). Therefore, all mention of "MIME" in the context of Internet media types must be avoided. See Sections 1 through 3 of RFC 4288 for more rationale and Section 10 there for the registration template to be used since RFC 4288, in 2005. Editorial Note (keep for update): The structure of Section 4 would perhaps more reasonably have been split into a single-paragraph Section 4 and packing the remainder of 4. into a new subsection 4.1, "Obsolescence of message/news", with the remaining subsection numbers 4.* bumped accordingly. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5537 (draft-ietf-usefor-usepro-14) -------------------------------------- Title : Netnews Architecture and Protocols Publication Date : November 2009 Author(s) : R. Allbery, Ed., C. Lindsey Category : PROPOSED STANDARD Source : Usenet Article Standard Update Area : Applications Stream : IETF Verifying Party : IESG
- [Technical Errata Reported] RFC5537 (1983) RFC Errata System
- Re: [Technical Errata Reported] RFC5537 (1983) Russ Allbery