RFC 3072 on Structured Data Exchange Format
RFC Editor <rfc-ed@ISI.EDU> Thu, 22 March 2001 00:00 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24333; Wed, 21 Mar 2001 19:00:10 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA14305 for ietf-123-outbound.10@ietf.org; Wed, 21 Mar 2001 18:55:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA14276 for <all-ietf@loki.ietf.org>; Wed, 21 Mar 2001 18:52:45 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA23906 for <all-ietf@ietf.org>; Wed, 21 Mar 2001 18:52:45 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f2LNqi521509; Wed, 21 Mar 2001 15:52:44 -0800 (PST)
Message-Id: <200103212352.f2LNqi521509@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3072 on Structured Data Exchange Format
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 21 Mar 2001 15:52:44 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3072 Title: Structured Data Exchange Format (SDXF) Author(s): M. Wildgrube Status: Informational Date: March 2001 Mailbox: max@wildgrube.com Pages: 25 Characters: 48481 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-wildgrube-sdxf-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3072.txt This specification describes an all-purpose interchange format for use as a file format or for net-working. Data is organized in chunks which can be ordered in hierarchical structures. This format is self-describing and CPU-independent. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3072 on Structured Data Exchange Format RFC Editor