RFC 48 - A Possible Protocol Plateau
- Status: Unknown
- Published: April 21, 1970
- Stream: Legacy
- Errata: No Errata
Document Information
- RFC Number: 48
- Title: A Possible Protocol Plateau
- Authors: J. Postel (UCLA), S. Crocker (UCLA)
- Date: April 21, 1970
- Category: Unknown
Abstract
RFC 48 reports the results of two UCLA activities since the network meeting of March 17, 1970. Section II states UCLA's preferences on the protocol issues raised in earlier notes and in private conversations: double padding versus marking, dynamic reconnection, decoupling connections from links, error reporting, status testing and reporting, expansion and experimentation, multiplexing ports to sockets, echoing, interrupts and code conversion, broadcast facilities, instance numbers, and the naming of the low order 8 bits of the socket (AEN). Section III sets out UCLA's assumptions about the environment of the NCP — processes, user numbers, ports, event channels, local sockets and typical system calls (Init, Listen, Close, Transmit, Status). Section IV sketches the components of the NCP: five programs (Input Handler, Output Handler, Input Interpreter, Output Scheduler, System Call Interpreter), three associative tables (Rendezvous Table, Input Link Table, Output Link Table), a link assignment table, and the queues and buffers that connect them, together with a diagram of the whole design.
Table of Contents
- I. Introduction
- II. Issues and Preferences
- III. Environment
- IV. The NCP
Related Resources
- Official RFC: RFC 48
- DataTracker: RFC 48 Info
- Errata: RFC Editor Errata