Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!daemon
From: jkrey@venera.isi.edu (Joyce K. Reynolds)
Newsgroups: comp.doc
Subject: RFC1197 on Using ODA
Message-ID: <9012312319.AA10269@venera.isi.edu>
Date: 31 Dec 90 23:19:08 GMT
Sender: daemon@ucsd.Edu
Reply-To: jkrey@venera.isi.edu
Lines: 59
Approved: rfc
Posted-Date: Mon, 31 Dec 90 15:19:08 PST
To: Request-for-Comments-List:;@NIC.DDN.MIL
Cc: jkrey@venera.isi.edu


A new Request for Comments is now available from the Network Information
Center in the online library at NIC.DDN.MIL.

	RFC 1197:

        Title:      Using ODA for Translating Multimedia Information
       	Author:     M. Sherman
	Mailbox:    mss+@andrew.cmu.edu
	Pages:      2
	Characters: 3,620

		pathname: RFC:RFC1197.TXT


The purpose of this RFC is to inform implementors of multimedia
systems about our experiences using ISO 8613: Office Document
Architecture (ODA).  Because ODA is being proposed as an encoding
format for use in multimedia mail and file exchange, implementors
wishing to use ODA in an open systems environment may profit from our
experiences.  This memo provides information for the Internet
community.  It does not specify any standard.  Distribution of this
memo is unlimited.

RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname
RFC:RFCnnnn.TXT (where "nnnn" refers to the number of the RFC).  Login
with FTP, username "anonymous" and password "guest".

The NIC also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to SERVICE@NIC.DDN.MIL and in the
subject field of the message indicate the RFC number, as in "Subject:
RFC nnnn".

RFCs can also be obtained via FTP from NIS.NSF.NET.  Using FTP, login
with username "anonymous" and password "guest"; then connect to the RFC
directory ("cd RFC").  The file name is of the form RFCnnnn.TXT-1
(where "nnnn" refers to the number of the RFC).

The NIS also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to NIS-INFO@NIS.NSF.NET and leave
the subject field of the message blank.  The first line of the text of
the message must be "SEND RFCnnnn.TXT-1", where nnnn is replaced by
the RFC number.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.

Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.


Joyce K. Reynolds
USC/Information Sciences Institute