XML related protocols survey

Has very little to do with XML, other than that it can be used to encapsulate XML data. Also, the metadata expression capabilities of MIME are fairly limited, and may be better served by attaching XML-formatted content.

Has very little to do with XML, other than that it allows XML namespace URIs to be used as document payload type identifiers.

Performs a small subset of the functions of MIME. There is a clearer division of functional capability between DIME and XML than between MIME and XML.

Uses XML and MIME for its own protocol elements, and can transfer arbitrary MIME content.

Uses XML for its own protocol elements, and can transfer arbitrary XML content.

SOAP has three inter-related parts:

• envelope structure for conveying arbitrary XML data
• data encoding (optional)
• protocol binding framework; HTTP is commonly used

An XML text protocol that permits multiple service providers to perform object provisioning operations using a shared central object repository.

???what is "object provisioning"?

The following protocols are currently defined:

• Peer Discovery Protocol
• Peer Information Protocol
• Pipe Binding Protocol
• Peer Resolver Protocol
• Endpoint Routing Protocol
• Peer Membership Protocol

The Peer Discovery Protocol (PDP) is the protocol by which a peer publishes its own advertisements, and dis-covers advertisements from other peers (peer, peergroup, module, pipe and content). PDP uses the Peer Resolver Protocol for sending and propagating discovery advertisement requests.

The Peer Information Protocol (PIP) is the protocol by a which a peer may obtain status information about other peers, such as state, uptime, traffic load, capabilities, etc. PIP uses the PRP for sending and propagating peer information requests.

The Pipe Binding Protocol (PBP) is the protocol by which a peer can establish a virtual communication channel or pipe between one or more peers. The PBP is used by a peer to bind the two or more pipe ends of the connec-tion (input and output pipe) to a physical peer endpoint. PBP uses the PRP for sending and propagating pipe binding requests.

The Peer Resolver Protocol (PRP) is the protocol by which a peer can send a generic resolver query to one or more peers, and receive a response (or multiple responses) to the query. The PRP protocol permits the dissemi-nation of generic queries to one or more handlers within the group and to match them with responses. Each query is addressed to a specific handler name. This handler name defines the particular semantics of the query and its responses, but is not associated with any specific peer. A given query may be received by any number of peers in the group, possibly all, and processed according to the handler name if such a handler name is defined on that peer.

The Peer Endpoint Protocol (PEP) is the protocol by which a peer can discover a route (sequence of hops) used to send a message to another peer. If a peer A wants to send a message to peer C, and there is no direct route between A and C, then peer A needs to find the intermediary relay peer(s) to route the message to C. PEP is used to determine the routing information. If the network topology has changed such that the route to C can no longer be used, the peer can use PEP to find routes known by other peers to construct a new route to C.

The Rendezvous Protocol (RVP) is the protocol by which peers can subscribe or be a subscriber to a propagation service. Within a peergroup, peers can be rendezvous peers, or peers that are listening to rendezvous peers. RVP allows messages to be sent to all of the listeners of the service. RVP is used by the Peer Resolver Protocol in order to propagate messages.