I-D ACTION:draft-stevens-advanced-api-02.txt
Internet-Drafts@ietf.org Thu, 27 March 1997 15:00 UTC
Received: from ietf.org by ietf.org id aa20079; 27 Mar 97 10:00 EST
Received: from ietf.ietf.org by ietf.org id aa18333; 27 Mar 97 9:57 EST
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Sender: ietf-announce-request@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-stevens-advanced-api-02.txt
Date: Thu, 27 Mar 1997 09:57:03 -0500
X-Orig-Sender: cclark@ietf.org
Message-ID: <9703270957.aa18333@ietf.org>
A Revised Internet-Draft is available from the on-line Internet-Drafts
directories.
Title : Advanced Sockets API for IPv6
Author(s) : W. Stevens, M. Thomas
Filename : draft-stevens-advanced-api-02.txt
Pages : 67
Date : 03/26/1997
Specifications are in progress for changes to the sockets API to support IP
version 6 [2]. These changes are for TCP and UDP-based applications and
will support most end-user applications in use today: Telnet and FTP
clients and servers, HTTP clients and servers, and the like.
But another class of applications exists that will also be run under IPv6.
We call these "advanced" applications and today this includes programs
such as Ping, Traceroute, routing daemons, multicast routing daemons,
router discovery daemons, and the like. The API feature typically
used by these programs that make them "advanced" is a raw socket to
access ICMPv4, IGMPv4, or IPv4, along with some knowledge of the packet
header formats used by these protocols. To provide portability for
applications that use raw sockets under IPv6, some standardization
is needed for the advanced API features.
There are other features of IPv6 that some applications will need to
access: interface identification (specifying the outgoing interface
and determining the incoming interface) and IPv6 extension headers that are
not addressed in [2]: Hop-by-Hop options, Destination options, and the
Routing header (source routing). This document provides API access
to these features too.
Internet-Drafts are available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-stevens-advanced-api-02.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-stevens-advanced-api-02.txt
Internet-Drafts directories are located at:
o Africa: ftp.is.co.za
o Europe: ftp.nordu.net
ftp.nis.garr.it
o Pacific Rim: munnari.oz.au
o US East Coast: ds.internic.net
o US West Coast: ftp.isi.edu
Internet-Drafts are also available by mail.
Send a message to: mailserv@ds.internic.net. In the body type:
"FILE /internet-drafts/draft-stevens-advanced-api-02.txt".
NOTE: The mail server at ds.internic.net can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e., documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version
of the Internet-Draft.
- I-D ACTION:draft-stevens-advanced-api-02.txt Internet-Drafts