IETF Logo Mail Archive

Re: URL attributes

Marshall Rose <mrose@dbc.mtview.ca.us> Tue, 23 November 1993 01:38 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15040; 22 Nov 93 20:38 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa15036; 22 Nov 93 20:38 EST
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa20622; 22 Nov 93 20:38 EST
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.08537-0@haig.cs.ucl.ac.uk>; Tue, 23 Nov 1993 00:55:14 +0000
Received: from ppp.dbc.mtview.ca.us by bells.cs.ucl.ac.uk with Internet SMTP id <g.25840-0@bells.cs.ucl.ac.uk>; Tue, 23 Nov 1993 00:54:53 +0000
Received: from localhost by dbc.mtview.ca.us (5.65/3.1.090690) id AA18404; Mon, 22 Nov 93 16:53:19 -0800
To: pays@faugeres.inria.fr
Cc: osi-ds@cs.ucl.ac.uk, Paul-Andre.Pays@faugeres.inria.fr
Reply-To: osi-ds@cs.ucl.ac.uk
Subject: Re: URL attributes
In-Reply-To: Your message of "16 Nov 1993 20:22:55 +0100." <753477775.9970.0-faugeres.inria.fr*@MHS>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Id: <18400.754015992.1@dbc.mtview.ca.us>
Date: Mon, 22 Nov 1993 16:53:13 -0800
Message-Id: <18403.754015993@dbc.mtview.ca.us>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Marshall Rose <mrose@dbc.mtview.ca.us>

FYI -  a few months back the NADF defined

	multiMediaInformation ATTRIBUTE
	    -- arbitrary multi-media information about an object,
	    -- represented as a MIME content-type
	    WITH ATTRIBUTE-SYNTAX OCTET STRING
	    ::= { nadfAttributeType 16}

The idea was similar to yours, one could simply store a

			 message/external-body

which contained a pointer to some real data, such as audio, image, or
maybe even a program to execute on the user's display (an active attribute).
The advantage with this approach is that since one can indicate whether
a MIME external-body is cachable, then in some cases, only the initial
dereference need result in a network transaction...

/mtr

v2.8.7 | Report a Bug | By Email