Re: MIME documents - the decision

Ned Freed <Ned.Freed@innosoft.com> Sun, 25 August 1996 00:31 UTC

Received: from ietf.org by ietf.org id aa21483; 24 Aug 96 20:31 EDT
Received: from cnri by ietf.org id aa21479; 24 Aug 96 20:31 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa12915; 24 Aug 96 20:31 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id UAA22584; Sat, 24 Aug 1996 20:15:20 -0400
Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by list.cren.net (8.6.12/8.6.12) with ESMTP id UAA22546 for <ietf-822@list.cren.net>; Sat, 24 Aug 1996 20:13:11 -0400
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V5.0-7 #8694) id <01I8MA7OKSM88Y59WJ@INNOSOFT.COM>; Sat, 24 Aug 1996 17:12:10 -0700 (PDT)
Message-Id: <01I8NTXOUJCM8Y59WJ@INNOSOFT.COM>
Date: Sat, 24 Aug 1996 17:10:19 -0700 (PDT)
X-Orig-Sender: owner-ietf-822@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Ned Freed <Ned.Freed@innosoft.com>
To: Harald.T.Alvestrand@uninett.no
Cc: ietf-822@list.cren.net
Subject: Re: MIME documents - the decision
In-Reply-To: "Your message dated Fri, 23 Aug 1996 16:12:04 +0200" <24299.840809524@domen.uninett.no>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

> The Apps ADs discussed the matter of implementation, features and
> when to approve things in the IESG yesterday.

> The conclusions reached were roughly:

> - The intent of the standards process is that used features are in the
>   standard, and useless features are NOT in it.
>   Clearly, this is not a simple decision to make.
> - The decision on what features should be in the standard and what not
>   is something the working group should come to consensus on, not
>   something that the ADs should decide.
> - Nevertheless, publication of the current set of MIME documents at
>   this time is a Good Thing.

> Actions resulting from this:

> - The current set of MIME drafts is APPROVED, with no changes.
> - Before the next advancement in level (to Full Standard), the working
>   group will be reconvened (probably by a formal reactivation) to review
>   the documents and decide upon the criteria for features being part of
>   the Full Standard MIME documents.

> Thus spoke the IESG - hope you all can live with that!

This is all fine with me, as you can imagine. I do have a question, however --
should I begin to develop a set of MIME conformance criteria for agents
sending MIME messages? As I stated before, there is some value in this.

> (and now to wait for the RFCs - the average wait through the RFC-editor's
> queue is around 2 months now)

I take this to mean that I should forward the documents to the RFC Editor
now. Or should I wait for a formal IESG announcement before doing so?

				Ned