RFC 2188 on ESRO
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 2188 on ESRO
- To: IETF-Announce: ;
- Subject: RFC 2188 on ESRO
- From: RFC Editor <rfc-ed@isi.edu>
- Date: Tue, 09 Sep 97 15:28:32 PDT
- Cc: rfc-ed@isi.edu
- Content-Length: -919
- Content-Type: Multipart/Mixed; Boundary=NextPart
- Sender: ietf-announce-request@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 2188: Title: AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2 Author: M. Banan, M. Taylor, and J. Cheng Date: September 1997 Mailbox: mohsen@neda.com, mark.taylor@airdata.com, jcheng@airdata.com Pages: 57 Characters: 118374 Updates/Obsoletes: None URL: ftp://ds.internic.net/rfc/rfc2188.txt 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. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@ISI.EDU. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@ISI.EDU Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Alegre Ramos USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
<<< multipart/alternative: No recognizable part >>>
- Prev by Date: Re: ESRO ID
- Next by Date: Re: ESRO ID
- Prev by thread: Clarifications on ESRO SAP Addressing
- Index(es):