Source Address Finding (SAF) for IPv6 Translation Mechanisms
draft-thaler-ipv6-saf-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Dave Thaler | ||
| Last updated | 2011-03-14 (Latest revision 2009-07-07) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-thaler-ipv6-saf-03.txt
https://www.ietf.org/archive/id/draft-thaler-ipv6-saf-03.txt
Abstract
There are various recent proposals that would result in IPv6 translation becoming permanent. RFC 3424 discusses UNilateral Self- Address Fixing (UNSAF) mechanisms which are required for applications to work with most translation schemes, points out a number of problems with them, and requires an exit strategy for any UNSAF mechanism. This document discusses an alternative to UNSAF mechanisms should IPv6 translation become permanent.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)