RFC 3542

Advanced Sockets Application Program Interface (API) for IPv6, May 2003

Canonical URL:
https://www.rfc-editor.org/rfc/rfc3542.txt
File formats:
Plain TextPDF
Status:
INFORMATIONAL
Obsoletes:
RFC 2292
Authors:
W. Stevens
M. Thomas
E. Nordmark
T. Jinmei
Stream:
IETF
Source:
ipv6 (int)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC3542

Discuss this RFC: Send questions or comments to iesg@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader