Re: RFC 1524
Larry Masinter <masinter@parc.xerox.com> Tue, 24 September 1996 20:42 UTC
Received: from cnri by ietf.org id aa28102; 24 Sep 96 16:42 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa08294;
24 Sep 96 16:42 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 QAA00031;
Tue, 24 Sep 1996 16:28:01 -0400 (EDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by list.cren.net
(8.7.6/8.6.12) with SMTP id QAA29986 for <ietf-822@list.cren.net>;
Tue, 24 Sep 1996 16:27:06 -0400 (EDT)
Received: from golden.parc.xerox.com ([13.1.100.139]) by alpha.xerox.com with
SMTP id <15762(2)>; Tue, 24 Sep 1996 13:21:03 PDT
Received: by golden.parc.xerox.com id <2759>; Tue, 24 Sep 1996 13:20:57 PDT
Message-Id: <96Sep24.132057pdt."2759"@golden.parc.xerox.com>
Date: Tue, 24 Sep 1996 13:20:57 PDT
Sender: owner-ietf-822@list.cren.net
Precedence: bulk
From: Larry Masinter <masinter@parc.xerox.com>
To: Chris.Newman@innosoft.com
Cc: Daniel.Glazman@der.edfgdf.fr, ietf-822@list.cren.net
Subject: Re: RFC 1524
In-Reply-To: <Pine.SOL.3.95.960923122854.24077G-100000@elbonia.innosoft.com>
(message from Chris Newman on Mon, 23 Sep 1996 12:37:49 PDT)
X-Sender: Larry Masinter <masinter@parc.xerox.com>
X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
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. 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. What I'm encouraging is a focus on "what's kept in the global registry", and let "what might system maintainers want to keep and share" be derived from that, not vice-versa. At least, IETF might have some say over what IANA does, but not as much over what happens inside some particular operating systems. > name="Graphic Interchange Format" media-type=image/gif extension=gif > mac-type=GIFf mac-creator=JVWR unix-helper=xv magic=gif8 > Windows-Helper=whatever ... Some of the links here are globally true, some are tied to specific operating system platforms, some might be overridden by particular system administrators. Globally, there might be a media type, operating system(s), helper, helper URL table. Globally, there's a media type, operating system(s), file extension(s) link, too, which might also be overriden by particular systems. This might sound ambitious, but I'm just trying to sort out the information that's already there. Larry
- Re: RFC 1524 Larry Masinter
- Re: RFC 1524 Keith Moore
- Re: RFC 1524 Ned Freed
- Re: RFC 1524 Nathaniel Borenstein
- Re: RFC 1524 Daniel Glazman
- Re: RFC 1524 Chris Newman
- Re: RFC 1524 Larry Masinter
- Re: RFC 1524 Daniel Glazman