Provisioning IPv4 Configuration Over IPv6 Only Networks
draft-rajtar-dhc-v4configuration-02
| Document | Type | Replaced Internet-Draft (dhc WG) | |
|---|---|---|---|
| Last updated | 2013-05-16 (latest revision 2013-04-16) | ||
| Replaced by | draft-ietf-dhc-v4configuration | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dhc-v4configuration | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-rajtar-dhc-v4configuration-02.txt
Abstract
As IPv6 becomes more widely adopted, some service providers are taking the approach of deploying IPv6 only networks, without dual- stack functionality for IPv4. However, access to IPv4 based services is still an ongoing requirement and approaches such as IPv4-in-IPv6 softwire tunnels are being developed to meet this need. In order to provision end-user's hosts with the necessary IPv4 configuration, a number of different mechanisms have been proposed. This memo discusses the benefits and drawbacks of each, with the aim of recommending a single approach as the basis for future work.
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.)