Ned Freed and Nathaniel S. Borenstein. Multipurpose Internet Mail Extensions (MIME) --- Part One: Format of Internet Message Bodies. Internet draft standard RFC 2045.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....For clarity of exposition, the published content is an XML element . In the general case (allowing non text based content types such as image jpeg) the content is a MIME object. The XML based publication input set and query result set is augmented with an additional MIME multipart object [19], which is a list containing all content. The content element of the result set is interpreted as an index into the MIME multipart object. A typical hyper registry that supports caching can handle content with at least MIME content type text xml and text plain. 7 The publish operation of a hyper ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045, November 1996.

....limited length (e.g. 1,000 characters or less as specified in [137] This forced users to convert non textual content into a 7bit US ASCII text representation and split the content over several mails. Such drawbacks were overcome with the introduction of the Multipurpose Internet Mail Extensions [46, 47, 48, 49, 114] (MIME) MIME mails can transport arbitrary content of (conceptually) arbitrary size. MIME mail can be exploited to make electronic mail look even more similar to a push system. Via appropriate MIME types, executable content can be transported to a receiver, unpacked there, and executed at the ....

....content is defined to be a sequence of bytes the most general data type. Its remaining fields mimeType and packing provide information that is necessary for the decoding and processing of Cargo s content. 4.4.1. 3 Agent Minstrel includes content handlers for the most frequently used MIME [46, 47, 48, 49, 114] types on the Internet. Some Cargo objects, however, may hold content types that cannot be handled by Minstrel s standard handlers. In these cases the provider of the Cargo can supply a specialized Agent to process the content of the Cargo object (if the Cargo, however, holds a MIME type that ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. Network Working Group, November

....SMTP transport service receives a message from the GNUnet core, the message is extended with a header that contains the node identity of the sender and the metainformation provided in the parameters of send. The resulting message is base64 encoded, encapsulated according to the MIME conventions [4], and sent to the MTA over the preexisting TCP connection. Most MTAs store the mail on the drive before sending an acknowledgement to the client in order to ensure guaranteed delivery even after a crash. While this is not required for GNUnet mail (especially since the semantics only specify ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. RFC 2045.

.... Consequently, we devised the WSDA based Unified Peer to Peer Database Framework (UPDF) 4] and its associated Peer Database Protocol (PDP) 15] which are unified in the sense that they allow to express specific applications for a wide range of data types (typed or untyped XML, any MIME type [16]) node topologies (e.g. ring, tree, graph) query languages (e.g. XQuery, SQL) query response modes (e.g. Routed, Direct and Referral Response) and pipelining characteristics. In the UPDF framework, an originator sends a query to an agent node, which evaluates it, and forwards it to select ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045.

....For clarity of exposition, the examples given here use short strings as values for type and context (e.g. service, parent) However, strictly speaking, this is not legal. To avoid namespace pollution and ambiguities, the value of a type must be a universally unique URI [65] a MIME contenttype [67] (e.g. application octet stream, image jpeg, audio mpeg) or the empty string. For XML content observing an XML Schema [12] the type must equal the URI of the schema namespace. The value of a context must be a URI or the empty string. For example, a service description really is of type ....

....a hyper registry has the following signature: void publish(XML tupleset) In the general case (allowing non text based content types such as image jpeg) the content is a MIME object. The XML based publication input set and query result set is augmented with an additional MIME multipart object [67], which is a list containing all content. The content element of the result set is interpreted as an index into the MIME multipart object. A typical hyper registry that supports caching can handle content with at least MIME content type text xml and text plain. Within a tuple set, a tuple is ....

[Article contains additional citation context not shown here]

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045.

....scalability, availability, performance and security. Consequently, we devised the WSDA based Unified Peer to Peer Database Framework (UPDF) 13, 2] which is unified in the sense that it allows to express specific applications for a wide range of data types (typed or untyped XML, any MIME type [14]) node topologies (e.g. ring, tree, graph) query languages (e.g. XQuery, SQL) query response modes (e.g. Routed, Direct and Referral Response) neighbor selection policies (in the form of an XQuery) pipelining characteristics, timeout and other scope options. In this framework, an originator ....

....exchanges) Its transport mapping to TCP uses application multiplexing (one TCP connection per session) with sliding windows [17] Each channel has a sliding window that indicates the number of payload octets that a peer may transmit before receiving further permission to transmit. MIME [14] with a default of text xml is used for encoding (representing messages) Octet counting with trailers is used for framing (delimiting messages) SASL [23] and or TLS SSL [24] are used for authentication (verifying user identities) and privacy (protecting against third party interception) ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045, November 1996.

....to send e mail from one machine to another. POP [33] is used to update a replica of one s main mailbox on a second machine. Both protocols function such that e mail messages are transfered in their entirety, including all attachments, over a TCP connection. Attachments are encoded in MIME format [16]. The e mail scanner subscribes with contain rights to reconstructed TCP streams corresponding to the default port numbers for these protocols (25 for SMTP and 110 for POP) Any communications other than e mail messages are passed immediately. When the start of an e mail message is detected, the ....

N. Freed and N. Borenstein. Multipurpose internet mail extensions (MIME) part one: format of internet message bodies, RFC--2045.

.... Consequently, we devised the WSDA based Unified Peer to Peer Database Framework (UPDF) 2] and its associated Peer Database Protocol (PDP) 12] which are unified in the sense that they allow to express specific applications for a wide range of data types (typed or untyped XML, any MIME type [13]) node topologies (e.g. ring, tree, graph) query languages (e.g. XQuery, SQL) neighbor selection policies (in the form of an XQuery) pipelining characteristics, timeout and other scope options. A link topology describes the link structure among nodes. For example, in a worldwide service ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045.

.... Consequently, we devised the WSDA based Unified Peer to Peer Database Framework (UPDF) 15] and its associated Peer Database Protocol (PDP) 16] which are unified in the sense that they allow to express specific applications for a wide range of data types (typed or untyped XML, any MIME type [17]) node topologies (e.g. ring, tree, graph) query languages (e.g. XQuery, SQL) query response modes (e.g. Routed, Direct and Referral Response) and pipelining characteristics. In the UPDF framework, an originator sends a query to an agent node, which evaluates it, and forwards it to select ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045.

....over HTTP. For example, given a service description with a getPhysicalFileNames(LogicalFileName) operation, a query can match on values For clarity of exposition, the content is an XML element. In the general case (allowing non text based content types such as image jpeg) the content is a MIME [27] object. The XML based publication input tuple set and query result tuple set is augmented with an additional MIME multipart object, which is a list containing all content. The content element of a tuple is interpreted as an index into the MIME multipart object. Find all (available) services. ....

....service layer on top of Internet software, because it defines appropriate services, interfaces, operations and protocol bindings. WSDA does not introduce new Internet standards. Rather, it judiciously combines existing interoperability proven open Internet standards such as HTTP(S) URI [24] MIME [27], XML, XML Schema [28] and BEEP [31] Modularity. WSDA is modular because it defines a small set of orthogonal multipurpose communication primitives (building blocks) for discovery. These primitives cover service identification, service description retrieval, publication, as well as minimal ....

[Article contains additional citation context not shown here]

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045, November 1996.

....For clarity of exposition, the examples given here use short strings as values for type and context (e.g. service, parent) However, strictly speaking, this is not legal. To avoid namespace pollution and ambiguities, the value of a type must be a universally unique URI [14] a MIME content type [15] (e.g. application octet stream, image jpeg, audio mpeg) or the empty string. For XML content observing an XML Schema [12] the type must equal the URI of the schema namespace. The value of a context must be a URI or the empty string. For example, a service description really is of type ....

....output includes cached content. The whereas the parent context really has the value http: gridforum.org content context parent 1.0. For clarity of exposition, the content is an XML element. In the general case (allowing non text based content types such as image jpeg) the content is a MIME [15] object. The XML based publication input tuple set and query result tuple set is augmented with an additional MIME multipart object, which is a list containing all content. The content element of a tuple is interpreted as an index into the MIME multipart object. getLinks( query operation is ....

[Article contains additional citation context not shown here]

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. IETF RFC 2045.

....in section 7.1. 2. 2 Messages An HTTP message consists of protocol visible header information, followed by an optional body (an opaque sequence of bytes) The body of an HTTP message has one of these higher level types, described by an orthogonal content type system that HTTP inherited from MIME[12]. The HTTP message headers can (should) convey application level content type tags for this body, such as image jpeg or text html , but HTTP per se does not concern itself with the interpretation of content types. 2.3 Entities and Entity Tags Relatively early in its history, the HTTP protocol ....

....for this body, such as image jpeg or text html , but HTTP per se does not concern itself with the interpretation of content types. 2. 3 Entities and Entity Tags Relatively early in its history, the HTTP protocol adopted a number of concepts from MIME (Multipurpose Internet Mail Extensions) [12]. In particular, MIME uses the term entity to refer to [the] MIME defined header fields and contents of either a message or one of the parts in the body of a multipart entity. The specification of such entities is the essence of MIME. HTTP adopted the term and defines it similarly, as The ....

N. Freed and N. Borenstein. Multipurpose internet mail extensions (MIME) part one: Format of Internet message bodies. RFC 2045.

....broker. A UsageConfirmation record is returned by the broker indicating acceptance or rejection of the signed CDR. An OSP message consists of an Extensible Markup Language (XML) document [WWW98] and a Secure Multipurpose Internet Mail Extension (S MIME) digital signature [Ram99] in a regular MIME [FB96] message. Use of XML will allow OSP to be easily extended. OSP messages are sent in a HyperText Transfer Protocol (HTTP) BFN96] message, using the Secure Sockets Layer (SSL) FKK96, DA99] described in Chapter 3, to secure the communications. TCP IP [Com00] provides reliable transport. Use of all ....

N. Freed and N. Borenstein. Multipurpose Internet mail extensions (MIME) part one: format of Internet message bodies. Request for Comments: RFC

....since formats do evolve, effective interaction requires some introductory content preceding the data that identifies its format. The format of this introductory or meta data has to be widely agreed upon and stable over time; our approach is to use an ASCII encoded XML format carried in a MIME [14] entity. Should the source attempt to transfer a type of content that the sink cannot handle, such as sending audio to a printer, the response indicates this error. We should also allow content negotiation , that is the source and sink should be able to exchange information on the formats they ....

Freed, N., and Borenstein, N. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. Internet RFC

.... : AssertionIdentifier SenderIdentifier : B64 representation of SHA1 hash of Sender URI AssertionIdentifier : B64 representation of SHA1 hash of Assertion ID element The construction of the SenderIdentifier and AssertionIdentifier uses a B64 representation, as specified in [MIME], of SHA1 hash results of a Sender URI and the ID element of the associated Assertion, respectively. The remainder of this section gives suggestions for implementation and use of these References. An originating site may store and manage a table of assertions for which references have been ....

Freed, N., and N. Borenstein, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, RFC 2045, Innosoft, First Virtual, November 1996, http://www.rfc-editor.org/rfc/rfc2045.txt

....Our sender side proposal is backward compatible with existing recipient systems, because it requires only changes at the sender. Furthermore, our sender stored email proposals explicitly address CM message forwarding, replying and annotation. In recent years, email user agents have become MIME [9] compatible, and are therefore capable to a limited degree of creating and rendering email messages with multimedia content. Paralleling the MIME developments, there has been increased integration of the email user agent and the Web browser. For example, mail readers now parse text messages for ....

N. Freed and N. Borenstein. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. Internet Engineering Task Force, Network Working Group, RFC 2045.

No context found.

Ned Freed and Nathaniel S. Borenstein. Multipurpose Internet Mail Extensions (MIME) --- Part One: Format of Internet Message Bodies. Internet draft standard RFC 2045.

No context found.

N. Freed and N. Borenstein. Multipurpose Internet mail extensions (MIME) part one: Format of Internet message bodies. RFC 2045.

No context found.

Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, RFC 2045.

No context found.

Freed, N.; Borenstein, N.: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. RFC 2045, November 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC