RFC 2133: Basic Socket Interface Extensions for IPv6
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2553.
Current document in this lineage: RFC 3493 — Basic Socket Interface Extensions for IPv6
In plain English — editorial summary, not part of the RFC
This memo defines a set of extensions to the socket interface to support the larger address size and new features of IPv6. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2133
- Published
- April 1997
- Authors
- R. Gilligan; S. Thomson; J. Bound; W. Stevens
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 32
- Also known as
- —
- Obsoleted by:
- RFC 2553
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2133 (1997)
- RFC 2553 (1999)
- RFC 3493 (2003) ✓
Read the full history of Basic Socket Interface Extensions for IPv6 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3493Basic Socket Interface Extensions for IPv6Current
March 2003
- RFC 2292Advanced Sockets API for IPv6Obsoleted
February 1998
- RFC 2367PF_KEY Key Management API, Version 2Current
July 1998
- RFC 2614An API for Service LocationCurrent
June 1999
- RFC 3041Privacy Extensions for Stateless Address Autoconfiguration in IPv6Obsoleted
January 2001
- RFC 3542Advanced Sockets Application Program Interface (API) for IPv6Current
June 2003
- RFC 2203RPCSEC_GSS Protocol SpecificationUpdated
September 1997
- RFC 1964The Kerberos Version 5 GSS-API MechanismUpdated
June 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?