home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_i
/
draft-ietf-ipngwg-bsd-api-07.txt
< prev
next >
Wrap
Text File
|
1997-04-21
|
2KB
|
58 lines
A new Request for Comments is now available in online RFC libraries.
RFC 2133:
Title: Basic Socket Interface Extensions for IPv6
Author: R. Gilligan, S. Thomson, J. Bound, W. Stevens
Date: April 1997
Mailbox: gilligan@freegate.net, set@thumper.bellcore.com,
bound@zk3.dec.com, rstevens@kohala.com
Pages: 32
Characters: 69737
Updates/Obsoletes: None
URL: ftp://ds.internic.net/rfc/rfc2133.txt
The de facto standard application program interface (API) for TCP/IP
applications is the "sockets" interface. But changes are required to
the sockets API to support IPv6 and this memo describes these changes.
These include a new socket address structure to carry IPv6 addresses,
new address conversion functions, and some new socket options. This
document is the product of the IPNG Working Group of the IETF.
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 announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute