RFC 3542: Advanced Sockets Application Program Interface (API) for IPv6
In plain English — editorial summary, not part of the RFC
This document provides sockets Application Program Interface (API) to support "advanced" IPv6 applications, as a supplement to a separate specification, RFC 3493. The expected applications include Ping, Traceroute, routing daemons and the like, which typically use raw sockets to access IPv6 or ICMPv6 header fields. This document proposes some portable interfaces for applications that use raw sockets under IPv6. There are other features of IPv6 that some applications will need to access: interface identification (specifying the outgoing interface and determining the incoming interface), IPv6 extension headers, and path Maximum Transmission Unit (MTU) information. This document provides API access to these features too. Additionally, some extended interfaces to libraries for the "r" commands are defined. The extension will provide better backward compatibility to existing implementations that are not IPv6-capable. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3542
- Published
- June 2003
- Authors
- W. Stevens; M. Thomas; E. Nordmark; T. Jinmei
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 77
- Also known as
- —
- Obsoletes:
- RFC 2292
Topics
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 2614An API for Service LocationCurrent
June 1999
- RFC 2553Basic Socket Interface Extensions for IPv6Obsoleted
March 1999
- RFC 2133Basic Socket Interface Extensions for IPv6Obsoleted
April 1997
- RFC 4178The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation MechanismCurrent
October 2005
- RFC 2478The Simple and Protected GSS-API Negotiation MechanismObsoleted
December 1998
- RFC 1964The Kerberos Version 5 GSS-API MechanismUpdated
June 1996
- RFC 1961GSS-API Authentication Method for SOCKS Version 5Current
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?