Problem Statement Regarding Limitations of the Sockets API for IPv6 Address Usage
draft-gont-taps-sockets-api-limitations-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fernando Gont , Guillermo Gont , Madelen Garcia Corbo , Christian Huitema | ||
| Last updated | 2018-09-22 (Latest revision 2018-03-21) | ||
| 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
This identifies gaps that currently prevent systems and applications from leveraging the increased flexibility and availability of IPv6 addresses.
Authors
Fernando Gont
Guillermo Gont
Madelen Garcia Corbo
Christian Huitema
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)