SIPP Program Interfaces for BSD Systems
draft-ietf-sipp-bsd-api-02
| Document | Type |
Expired Internet-Draft
(sipp WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Robert E. Gilligan , Jim Bound , Dr. Susan Thomson , Dr. Ramesh Govindan | ||
| Last updated | 1994-04-28 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | parcftp.xerox.com%3A%20pub/sipp | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In order to implement the Simple Internet Protocol (SIPP) in an operating system based on 4.x BSD, changes must be made to some of the application program interfaces (APIs). TCP/IP applications written for BSD-based operating systems have in the past enjoyed a high degree of portability because most of the systems derived from BSD provide the same API, known informally as 'the socket interface'. We would like the same portability to be possible with SIPP applications. This memo presents a set of changes to the BSD socket API to support SIPP. The changes include a new data structure to carry SIPP address sequences, new name to address translation library functions, new address conversion functions, and some new setsockopt() options. The changes are designed to be minimal and to provide source and binary compatibility for existing applications.
Authors
Robert E. Gilligan
Jim Bound
Dr. Susan Thomson
Dr. Ramesh Govindan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)