Provisioning IPv4 Configuration Over IPv6 Only Networks
draft-ietf-dhc-v4configuration-06
| Document | Type | Expired Internet-Draft (dhc WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2014-07-01) | ||
| Replaces | draft-rajtar-dhc-v4configuration | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Dead WG Document | |
| Document shepherd | Tomek Mrugalski | ||
| Shepherd write-up | Show (last changed 2014-02-21) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ted Lemon | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dhc-v4configuration-06.txt
Abstract
As IPv6 becomes more widely adopted, some service providers are choosing to deploy IPv6 only networks without dual-stack functionality for IPv4. However, as access to IPv4 based services will continue to be a requirement for the foreseeable future, IPv4 over IPv6 mechanisms, such as softwire tunnels are being developed. In order to provision end-user's hosts with the IPv4 configuration necessary for such mechanisms, a number of different approaches have been proposed. This memo discusses each of the proposals, identifies the benefits and drawbacks and recommends approaches to be used as the basis for future deployment and development.
Authors
Branimir Rajtar
(branimir.rajtar@t.ht.hr)
Ian Farrer
(ian.farrer@telekom.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)