SIPP Program Interfaces for BSD Systems
draft-ietf-sipp-bsd-api-02

Document Type Expired Internet-Draft (sipp WG)
Authors Robert Gilligan  , Jim Bound  , Susan Thomson  , Ramesh Govindan 
Last updated 1994-04-28
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-sipp-bsd-api-02.txt

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 Gilligan (gilligan@freegate.com)
Jim Bound (Jim.Bound@hp.com)
Susan Thomson (sethomso@cisco.com)
Ramesh Govindan (govindan@isi.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)