W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

[Harald.T.Alvestrand@uninett.no: nonexistent-WG Last Call on MIME documents]

From: Larry Masinter <masinter@parc.xerox.com>
Date: Mon, 17 Jun 1996 10:48:49 PDT
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <96Jun17.104849pdt."2763"@golden.parc.xerox.com>
MIME and HTTP are intertwined in the use of media types and character
sets. The important documents to review from the perspective of HTTP
are:

  draft-ietf-822ext-mime-imt-04.txt (standards track)
  draft-ietf-822ext-mime-reg-03.txt (BCP)
  draft-freed-charset-reg-00.txt (BCP)

Please note that discussion of these drafts are on the ietf-822 list,
currently.

================================================================

Date: Fri, 14 Jun 1996 06:59:53 PDT
From: Harald.T.Alvestrand@uninett.no
To: ietf-822@list.cren.net
Cc: moore@cs.utk.edu
Subject: nonexistent-WG Last Call on MIME documents

Folks,
the time has come to move on the next step of the MIME documents.

The proposal on the table before us is:

There exist 6 new drafts, with the following names and proposed grade:

draft-ietf-822ext-mime-imb-06.txt	- Draft
draft-ietf-822ext-mime-imt-04.txt	- Draft
draft-ietf-822ext-mime-hdrs-00.txt	- Draft
draft-ietf-822ext-mime-reg-03.txt	- BCP
draft-ietf-822ext-mime-conf-05.txt	- Draft
draft-freed-charset-reg-00.txt		- BCP

Most of these have been out for quite a while, and what initial discussion
there was has largely died down.

There is no active working group that has within its scope a mandate to
review these documents.

What I propose is this:

- All of the interested parties, read the documents NOW.
- If discussion on this list provokes no strong reactions against the
  current text of the document, issue an IETF-wide Last Call.

I propose a deadline for discussion on this list of ***** JULY 4, 1996.*****
(which will give me time to get back from the IETF and catch my breath)
At this time, if no significant (in the minds of me and Keith) objections
to the documents have been raised, the IETF-wide Last Call (4-week)
will go out.

NOTE: The assumption behind a recycle at Draft is that:

- There is no new functionality.
- There exist multiple interoperable implementations.
- The current documents are clearer than the old specs, but specify
  the same protocol.

Valid objections are that the document changes the protocol in an
incompatible manner, that the documents are unclear, or that there
are features that are not implemented and should be removed.

If you want to CHANGE MIME, this is NOT the time to do it,
since any CHANGE to the protocol requires a reset to Proposed level.

Comments?

             Harald A
Received on Monday, 17 June 1996 10:52:00 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:04 EDT