IPng BSD Host Implementation Analysis
RFC 1682

Document Type RFC - Informational (August 1994; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1682 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           J. Bound
Request for Comments: 1682                 Digital Equipment Corporation
Category: Informational                                      August 1994

                 IPng BSD Host Implementation Analysis

Status of this Memo

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


   This document was submitted to the IETF IPng area in response to RFC
   1550.  Publication of this document does not imply acceptance by the
   IPng area of any ideas expressed within.  Comments should be
   submitted to the big-internet@munnari.oz.au mailing list.


   This IPng white paper, IPng BSD Host Implementation Analysis,
   was submitted to the IPng Directorate to provide a BSD host point of
   reference to assist with the engineering considerations during the
   IETF process to select an IPng proposal.  The University of
   California Berkeley Software Distribution (BSD) TCP/IP (4.3 + 4.4)
   system implementation on a host is used as a point of reference for
   the paper.

   This document only reflects the author's personal analysis based on
   research and implementation experience for IPng, and does not
   represent any product or future product from any host vendor.  Nor
   should it be construed that it is promoting any specific IPng at this


   The author would like to acknowledge the many host implementation
   discussions and inherent knowledge gained from discussions with the
   following persons within Digital over the past year: Peter Grehan,
   Eric Rosen, Dave Oran, Jeff Mogul, Bill Duane, Tony Lauck, Bill Hawe,
   Jesse Walker, John Dustin, Alex Conta, and Fred Glover.  The author
   would also like to acknowledge like discussions from outside his
   company with Bob Hinden (SUN), Bob Gilligan (SUN), Dave Crocker
   (SGI), Dave Piscitello (Core Competence), Tracy Mallory (3Comm), Rob
   Ullmann (Lotus), Greg Minshall (Novell), J Allard (Microsoft), Ramesh
   Govinden (Bellcore), Sue Thompson (Bellcore), John Curran (NEARnet),

Bound                                                           [Page 1]
RFC 1682         IPng BSD Host Implementation Analysis       August 1994

   Christian Huitema (INRIA), and Werner Volgels (INESC).  The author
   would also like to thank Digital Equipment Corporation for the
   opportunity to work on IPng within the IETF as part of his job.

1. Introduction

   A host in the context of this white paper is a system that contains
   an operating system supporting a network subsystem as one of its
   parts, and an interprocess communications facility to access that
   network subsystem.  These hosts are often referenced as a
   Workstation, Server, PC, Super Computer, Mainframe, or an Embedded
   System (Realtime Devices).

   IPng will require changes to a hosts network software architecture.
   Those changes should be as transparent as possible to the existing
   IPv4 applications executing on hosts.

   After discussing the network software architecture for a BSD host the
   paper will discuss the perceived network software alterations,
   extended capabilities, transition software, and a deployment
   consideration for IPng hosts.

   The inclusive OR of all IPng proposals was used to develop the
   engineering considerations discussed in this paper.

2. Network Software Architecture

   The BSD host network software architecture consists essentially of
   three components: the interprocess communications facility, the
   network communications subsystem, and the network protocols
   supported. These three components are tightly coupled and must be
   integrated in a way that affords high performance for the
   applications that are dependent on these components to interoperate
   efficiently.  A BSD host implementation view of the TCP/IP protocol
   suite is depicted in the following network architecture diagram.

Bound                                                           [Page 2]
RFC 1682         IPng BSD Host Implementation Analysis       August 1994

   |                        Application Layer                        |
   |                                                                 |
   |                Socket and Network Library APIs                  |
   |                                                                 |
   |  BIND DNS                                                       |
   |  SNMP Management                                                |
   |                          User Space                             |
   |                         Kernel Space          AF_INET           |
   |                                        Communications Domain    |
Show full document text