Re: [Technical Errata Reported] RFC5537 (1983)

Russ Allbery <rra@stanford.edu> Mon, 28 December 2009 19:50 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 EE5D13A693C for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 28 Dec 2009 11:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.903
X-Spam-Level:
X-Spam-Status: No, score=-4.903 tagged_above=-999 required=5 tests=[AWL=1.143, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 S1TuiRCoIgNS for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 28 Dec 2009 11:50:22 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id E92993A697B for <usefor-archive@ietf.org>; Mon, 28 Dec 2009 11:50:21 -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 nBSJiEoZ030487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Dec 2009 12:44:14 -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 nBSJiEUT030486; Mon, 28 Dec 2009 12:44:14 -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 smtp.stanford.edu (smtp5.Stanford.EDU [171.67.219.85]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nBSJiDo7030479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-usefor@imc.org>; Mon, 28 Dec 2009 12:44:14 -0700 (MST) (envelope-from eagle@windlord.stanford.edu)
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 86BA418F57C; Mon, 28 Dec 2009 11:44:13 -0800 (PST)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) by smtp.stanford.edu (Postfix) with ESMTP id 591CD18F577; Mon, 28 Dec 2009 11:44:13 -0800 (PST)
Received: by windlord.stanford.edu (Postfix, from userid 1000) id 2BD972F5B9; Mon, 28 Dec 2009 11:44:13 -0800 (PST)
From: Russ Allbery <rra@stanford.edu>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: chl@clerew.man.ac.uk, lisa.dusseault@gmail.com, alexey.melnikov@isode.com, harald@alvestrand.no, ah@TR-Sys.de, ietf-usefor@imc.org
Subject: Re: [Technical Errata Reported] RFC5537 (1983)
In-Reply-To: <200912281343.nBSDhHRJ018791@boreas.isi.edu> (RFC Errata System's message of "Mon, 28 Dec 2009 05:43:17 -0800 (PST)")
Organization: The Eyrie
References: <200912281343.nBSDhHRJ018791@boreas.isi.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Date: Mon, 28 Dec 2009 11:44:13 -0800
Message-ID: <87tyvac29e.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

RFC Errata System <rfc-editor@rfc-editor.org> writes:

> 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.

I missed this change when updating the document from RFC 2048 to RFC 4288.
It is correct.  Thank you!

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>