Subject: [BEHAVE] TR: I-D Action:draft-thaler-behave-translator-addressing-00.txt

From: <[email-masked]>
Date: Tue, 21 Jul 2009 11:48:37 +0200

Hi all,

In this document there is an OPEN ISSUE (stated in the Introduction) on whether we should also include in the scope: addressing for IPv4 in IPv6  encapsulation (and not only IPv4-IPv6 translation) and port range info.

I think we should. The analysis for the two contexts (translation vs. encapsulaation) are likely to be rather similar.
For instance, how you retrieve, know, which Prefix to select, seems quite independent on what the packet bears.
Once the IPv6 packet is formed, whether it carries an IPv4 packet or a TCP segment (or whatsoever), the routing issues apply in the same way.

Pierre

-----Message d'origine-----
De : [email-masked] [mailto:[email-masked]] De la part de [email-masked]
Envoyé : mardi 7 juillet 2009 01:15
À : [email-masked]
Objet : I-D Action:draft-thaler-behave-translator-addressing-00.txt 

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : IPv6 Addressing of IPv6/IPv4 Translators
	Author(s)       : D. Thaler
	Filename        : draft-thaler-behave-translator-addressing-00.txt
	Pages           : 21
	Date            : 2009-07-06

This document discusses how an individual IPv6 address can be
algorithmically translated to a corresponding IPv4 address, and vice
versa, using only statically configured information.  This technique
is used in IPv6/IPv4 translators, as well as other types of proxies
and gateways (e.g., for DNS) used in IPv6/IPv4 scenarios.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-thaler-behave-translator-addressing-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.