[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-ietf-ngtrans-introduction-to-ipv6-transition-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: On overviewof the Introduction of IPv6 in the Internet
	Author(s)	: W. Biemolt, M. Kaat, T. Larder, H. Steenman,
                          R. van der Pol, G. Tsirtsis, Y. Sekiya, 
                          A. Durand, K. Yamamoto, D. Finkerson, A. Hazeltine
	Filename	: draft-ietf-ngtrans-introduction-to-ipv6-transition-06.txt
	Pages		: 36
	Date		: 06-Mar-01
This document is a guide to the introduction of IPv6 in the IPv4 
based Internet or Intranets.  Several general issues to start IPv6 
networking in a predominantly IPv4 world are discussed, such as IPv6
addresses, IPv6 DNS and routing issues.  Short descriptions are given
of the different translation and migration tools and mechanisms that
translate between IPv6 and IPv4 and/or tunnel IPv6 over IPv4.  The 
remainder of this document describes how IPv6 can be introduced in 
various environments, such as ISPs, Internet Exchanges and end user 
environments.  Suggestions are given on the use of the different 
translation and migration tools in each environment.

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-introduction-to-ipv6-transition-06.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-introduction-to-ipv6-transition-06.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Content-type: text/plain