Socket API for IPv6 flow label field
draft-itojun-ipv6-flowlabel-api-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jun-ichiro Itoh | ||
| Last updated | 2001-04-11 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The draft outlines a socket API proposal for controlling the flow label field in the IPv6 header. The API uses the sin6_flowinfo member on the IPv6 socket address structure (sockaddr_in6). The draft is, at this moment, written separately from the IPv6 basic/advanced API RFCs [Gilligan, 2000; Stevens, 1999] , as there can be many discussion items. The ultimate goal of the draft is to be a part of the IPv6 basic/advanced API.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)