IETF Logo Mail Archive

Re: RFC 1524

Daniel Glazman <Daniel.Glazman@der.edfgdf.fr> Thu, 26 September 1996 16:07 UTC

Received: from cnri by ietf.org id aa10968; 26 Sep 96 12:07 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa29457; 26 Sep 96 12:07 EDT
Received: from localhost (localhost.0.0.127.in-addr.arpa [127.0.0.1]) by list.cren.net (8.7.6/8.6.12) with SMTP id LAA12154; Thu, 26 Sep 1996 11:52:17 -0400 (EDT)
Received: from cf01 (cledf.edf.fr [192.54.193.133]) by list.cren.net (8.7.6/8.6.12) with ESMTP id LAA12127 for <ietf-822@list.cren.net>; Thu, 26 Sep 1996 11:51:15 -0400 (EDT)
Received: from clserv02.edf.fr (clserv02.edf.fr [130.98.118.118]) by cf01 (8.6.12/8.6.12) with ESMTP id RAA23919; Thu, 26 Sep 1996 17:52:38 +0200
Received: from cli51ak.der.edf.fr (cli51ak.der.edf.fr [130.98.16.29]) by clserv02.edf.fr (8.6.12/8.6.12) with SMTP id RAA20896; Thu, 26 Sep 1996 17:50:45 +0200
Received: by cli51ak.der.edf.fr (5.x/SMI-SVR4) id AA28749; Thu, 26 Sep 1996 17:48:29 +0100
Message-Id: <9609261648.AA28749@cli51ak.der.edf.fr>
Date: Thu, 26 Sep 1996 17:48:29 +0100
Sender: owner-ietf-822@list.cren.net
Precedence: bulk
From: Daniel Glazman <Daniel.Glazman@der.edfgdf.fr>
To: masinter@parc.xerox.com
Cc: Daniel.Glazman@der.edfgdf.fr, ietf-822@list.cren.net
Subject: Re: RFC 1524
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Mailer: MEUF [Mail Extended Using Faces v3.0.1 beta 1.1-full-mimePL1]
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN

In message <96Sep24.132057pdt."2759"@golden.parc.xerox.com> 24 Sep 1996 13:20:57, masinter@parc.xerox.com wrote:

> Well, this isn't quite 'mailcap' but what I would like is something
> like:
> 
> 1) an improved format for what might replace what's in
>    ftp://ftp.isi.edu/in-notes about each registered media type, in a
>    way that it can be mechanically processed, and a BCP that asks IANA
>    to maintain it.

A SGML formalism (I guess that HTML is too laxist for that) in good
and simple DTD sounds interesting. I guess this is a bit hard to run
but we can dream ;-)
I agree that we need such an improvement.

> 2) possibly an improved registry of 'operating system type'
> 3) a standard way that software maintainers can provide records
>    that link (1), (2) and their software, a global registry
>    of such links, and a way that system administrators
>    can maintain databases of those links.

Hmmm... This would be nice. But it is not an easy job. What about
a special mailing-list, where would be automagically announced new
types, associated with a special MIME content-type ?
For instance a multipart containing first a description of the published
content-type and then message/external-body bodypart(s) pointing to
external reference(s).

(just thinking aloud... I'm sick, influensa does not help !-)

</Daniel>

v2.8.7 | Report a Bug | By Email