idnits 2.17.1 draft-herriot-application-multiplexed-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3391 5 Title: The MIME Application/Vnd.pwg-multiplexed 6 Content-Type 7 Author(s): R. Herriot 8 Status: Informational 9 Date: December 2002 10 Mailbox: bob@herriot.com 11 Pages: 25 12 Characters: 54739 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-herriot-application-multiplexed-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3391.txt 19 The Application/Vnd.pwg-multiplexed content-type, like the 20 Multipart/Related content-type, provides a mechanism for representing 21 objects that consist of multiple components. An 22 Application/Vnd.pwg-multiplexed entity contains a sequence of chunks. 23 Each chunk contains a MIME message or a part of a MIME message. Each 24 MIME message represents a component of the compound object, just as a 25 body part of a Multipart/Related entity represents a component. With 26 a Multipart/Related entity, a body part and its reference in some 27 other body part may be separated by many octets. With an 28 Application/Vnd.pwg-multiplexed entity, a message and its reference in 29 some other message can be made quite close by chunking the message 30 containing the reference. For example, if a long message contains 31 references to images and the producer does not know of the need for 32 each image until it generates the reference, then 33 Application/Vnd.pwg-multiplexed allows the consumer to process the 34 reference to the image and the image before it consumes the entire 35 long message. This ability is important in printing and scanning 36 applications. This document defines the 37 Application/Vnd.pwg-multiplexed content-type. It also provides 38 examples of its use. 40 This memo provides information for the Internet community. It does 41 not specify an Internet standard of any kind. Distribution of this 42 memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.