Problem Statement Regarding IPv6 Address Usage
draft-gont-taps-address-usage-problem-statement-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Fernando Gont , Guillermo Gont , Madelen Garcia Corbo , Christian Huitema | ||
| Last updated | 2018-09-01 (Latest revision 2018-02-28) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 document analyzes the security and privacy implications of IPv6 addresses based on a number of properties (such as address scope, stability, and usage type), and 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.)