Interface ID lifetime Algorithms
draft-rafiee-v6ops-iid-lifetime-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hosnieh Rafiee , Christoph Meinel , Erik Nordmark | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-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 document introduces a framework, i.e., an application layer based lifetime [applicationiid] to enable applications maintaining their users' privacy as well as controlling the number of Interface IDs (IIDs) per network adapter. It will also explain different approaches that can be used for maintaining the lifetime of an IID. We also compare this framework to the other available mechanisms. This document also explains when to remove deprecated IP addresses from the a network interface.
Authors
Hosnieh Rafiee
Christoph Meinel
Erik Nordmark
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)