LAFT6: Lightweight address family transition for IPv6
draft-sun-v6ops-laft6-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Qiong Sun , Chongfeng Xie | ||
| Last updated | 2011-03-14 | ||
| 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
With the approaching exhaustion of IPv4 address space, large-scale ISPs are now facing the option to deploy IPv6 in a timely manner. However, most existing IPv6 transition solutions have tradeoff between scalability and efficiency. This draft proposes a lightweight address family transition mechanism named LAFT6. It only needs to maintain per-subscriber state entries in core network and there is no specific address format requirement for users' IPv6 address. It is a lightweight solution in terms of state-management, addressing and routing. The experimental results have shown that LAFT6 is scalable and can be rapidly deployed in commercial ISP network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)