Framework for accessing IPv6 content for IPv4-only clients
draft-rfvlb-behave-v6-content-for-v4-clients-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Branimir Rajtar, Ian Farrer , Vizdal Ales , Xing Li , Congxiao Bao | ||
Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
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 expansion of IPv6 usage and content available on IPv6, it is important that clients with legacy (i.e. non IPv6-capable) operating systems are able to access such content. This document describes a method for achieving this, including how the method could be implemented in real-world scenarios.
Authors
Branimir Rajtar
Ian Farrer
Vizdal Ales
Xing Li
Congxiao Bao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)