Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

VMTP: Versatile Message Transaction Protocol: Protocol specification (RFC1045)

IP.com Disclosure Number: IPCOM000001851D
Original Publication Date: 1988-Feb-01
Included in the Prior Art Database: 2000-Sep-12

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D.R. Cheriton: AUTHOR

Abstract

The Versatile Message Transaction Protocol (VMTP) is a transport protocol designed to support remote procedure call (RPC) and general transaction-oriented communication. By transaction-oriented communication, we mean that:

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 1% of the total text.

Network Working Group David Cheriton

Request for Comments: 1045 Stanford University

February 1988

VMTP: VERSATILE MESSAGE TRANSACTION PROTOCOL

Protocol Specification

STATUS OF THIS MEMO

This RFC describes a protocol proposed as a standard for the Internet

community. Comments are encouraged. Distribution of this document is

unlimited.

OVERVIEW

This memo specifies the Versatile Message Transaction Protocol (VMTP)

[Version 0.7 of 19-Feb-88], a transport protocol specifically designed

to support the transaction model of communication, as exemplified by

remote procedure call (RPC). The full function of VMTP, including

support for security, real-time, asynchronous message exchanges,

streaming, multicast and idempotency, provides a rich selection to the

VMTP user level. Subsettability allows the VMTP module for particular

clients and servers to be specialized and simplified to the services

actually required. Examples of such simple clients and servers include

PROM network bootload programs, network boot servers, data sensors and

simple controllers, to mention but a few examples.

RFC 1045 VMTP February 1988

Table of Contents

1. Introduction 1

1.1. Motivation 2

1.1.1. Poor RPC Performance 2

1.1.2. Weak Naming 3

1.1.3. Function Poor 3

1.2. Relation to Other Protocols 4

1.3. Document Overview 5

2. Protocol Overview 6

2.1. Entities, Processes and Principals 7

2.2. Entity Domains 9

2.3. Message Transactions 10

2.4. Request and Response Messages 11

2.5. Reliability 12

2.5.1. Transaction Identifiers 13

2.5.2. Checksum 14

2.5.3. Request and Response Acknowledgment 14

2.5.4. Retransmissions 15

2.5.5. Timeouts 15

2.5.6. Rate Control 18

2.6. Security 19

2.7. Multicast 21

2.8. Real-time Communication 22

2.9. Forwarded Message Transactions ...