RFC 2188 (rfc2188) - Page 1 of 57

AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1

Alternative Format: Original Text Document
Next >
Network Working Group                                         M. Banan
Request for Comments: 2188                                        Neda
Category: Informational                                      M. Taylor
                                                                   AWS
                                                              J. Cheng
                                                                   AWS
                                                        September 1997


          AT&T/Neda's Efficient Short Remote Operations (ESRO)
                   Protocol Specification Version 1.2


Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

IESG Note

   This protocol has not had the benefit of IETF Working Group review,
   but a cursory examination reveals several issues which may be
   significant issues for scalability.  A site considering deployment
   should conduct a careful analysis to ensure they understand the
   potential impacts.

Abstract

  This document specifies the service model, the notation and protocol
  for Efficient Short Remote Operations (ESRO). The ESRO service is
  similar to and is consistent with other Remote Procedure Call
  services.  The emphasis of ESRO service definition and the ESRO
  protocol is on efficiency.  ESRO is designed specifically with
  wireless network (e.g., CDPD) usage in mind.

  ESRO protocol provides reliable connectionless remote operation
  services on top of UDP (or any other non-reliable connectionless
  transport service) with minimum overhead.  ESRO protocol supports
  segmentation and reassembly, concatenation and separation as well as
  multiplexing for service users (applications).

  ESRO allows for trade-offs between efficiency and reliability by
  specifying both 2-way hand-shake and 3-way hand-shake based protocols.

  Encoding mechanisms for presentation of the parameters of remote
  operations are outside the scope of this document.  But,
  identification (tagging) of the encoding mechanism in use (e.g., XDR,



Banan, et. al                Informational
Next >