From owner-majordomo@ebt.com Thu Dec 21 14:38:08 1995 Return-Path: Received: from ebt-inc.ebt.com by utafll.uta.edu (4.1/25-eef) id AA09022; Thu, 21 Dec 95 14:36:49 CST Received: from Princeton.EDU (root@Princeton.EDU [128.112.128.1]) by ebt-inc.ebt.com (8.6.12/8.6.9) with SMTP id MAA21087 for ; Thu, 21 Dec 1995 12:58:41 -0500 Received: from acupain.UUCP by Princeton.EDU (5.65b/2.124/princeton) id AA07245; Thu, 21 Dec 95 12:52:31 -0500 Received: by Accurate.COM (4.1/SMI-4.0) id AA27075; Thu, 21 Dec 95 11:54:52 EST Message-Id: <9512211654.AA27075@Accurate.COM> To: MIME/SGML Folks Subject: New RFCs: 1872, 1873, 1874 Organization: Accurate Information Systems, Inc. X-Org-Addr: 2 Industrial Way X-Org-Addr: Eatontown, NJ 08840 X-Org-Misc: 1.908.389.5550 (phone) 1.908.389.5556 (fax) X-Mailer: MH 6.8 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Tiger-Lily" Date: Thu, 21 Dec 1995 11:54:46 -0500 From: Ed Levinson Status: R --Tiger-Lily Content-Description: Cover Letter The SGML Media Type, Multipart/Related, Access Type Content-ID RFCs have been issued. The attachements below contain the IETF announcements plus mail server and ftp External Bodies for retrieving those RFCs. I have combined the three announcements into a single one and I am redistributing it to the sgml-internet list on the assumption that many members of this list don't subscribe to either ietf or ietf-dist lists. Those are the lists where the RFC announcements are published. Ed --Tiger-Lily Content-Description: IETF Announcements New Request for Comments are now available in online RFC libraries. RFC 1872: Title: The MIME Multipart/Related Content-type Author: E. Levinson Date: December 1995 Mailbox: ELevinson@Accurate.com Pages: 8 Characters: 15,565 Updates/Obsoletes: none URL: ftp://ds.internic.net/rfc/rfc1872.txt The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME (Multipurpose Internet Mail Extensions) body parts. This document defines the Multipart/Related content-type and provides examples of its use. This RFC is the product of the MIME Content-Type for SGML Documents Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. RFC 1873: Title: Message/External-Body Content-ID Access Type Author: E. Levinson Date: December 1995 Mailbox: ELevinson@Accurate.com Pages: 4 Characters: 5,878 Updates/Obsoletes: none URL: ftp://ds.internic.net/rfc/rfc1873.txt When using MIME (Multipurpose Internet Mail Extensions) to encapsulate a structured object that consist of many elements, for example an SGML document, a single element may occur several times. An encapsulation normally maps each of the structured objects elements to a MIME entity. It is useful to include elements that occur multiple time exactly once. To accomplish that and to preserve the object structure it is desirable to unambiguously refer to another body part of the same message. The existing MIME Content-Type Message/External-Body access-types allow a MIME entity (body-part) to refer to an object that is not in the message by specifying how to access that object. The Content-ID access method described in this document provides the capability to refer to an object within the message. This RFC is the product of the MIME Content-Type for SGML Documents Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. RFC 1874: Title: SGML Media Types Author: E. Levinson Date: December 1995 Mailbox: ELevinson@Accurate.com Pages: 6 Characters: 12,515 Updates/Obsoletes: none URL: ftp://ds.internic.net/rfc/rfc1874.txt This document proposes new media sub-types of Text/SGML and Application/SGML. These media types can be used in the exchange of SGML documents and their entities. This RFC is the product of the MIME Content-Type for SGML Documents Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement was 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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@ISI.EDU. 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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@ISI.EDU. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@ISI.EDU 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 admin@DS.INTERNIC.NET. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information. Joyce K. Reynolds 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. --Tiger-Lily Content-Type: Multipart/Alternative; Boundary="OtherAccess" Content-Description: Access to the RFCs --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Description: Mail server access to the three RFCs Content-Type: text/plain Content-ID: <951219125950.RFC@ISI.EDU> SEND /rfc/rfc1872.txt SEND /rfc/rfc1873.txt SEND /rfc/rfc1874.txt --OtherAccess Content-Type: Multipart/Mixed; boundary="FTPAccess" Content-Description: FTP access to the three RFCs --FTPAccess Content-Type: Message/External-body; name="rfc1872.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Description: FTP access to 1872 Content-Type: text/plain Content-ID: <951219125950.RFC@ISI.EDU> --FTPAccess Content-Type: Message/External-body; name="rfc1873.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Description: FTP access to 1873 Content-Type: text/plain Content-ID: <951219125950.RFC@ISI.EDU> --FTPAccess Content-Type: Message/External-body; name="rfc1874.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Description: FTP access to 1874 Content-Type: text/plain Content-ID: <951219125950.RFC@ISI.EDU> --FTPAccess-- --OtherAccess-- --Tiger-Lily--