(ngtrans) I-D ACTION:draft-ietf-ngtrans-natreq4ipv6-00.txt
Internet-Drafts@ietf.org Sat, 24 February 2001 07:51 UTC
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17620 for <ngtrans-archive@odin.ietf.org>; Sat, 24 Feb 2001 02:51:39 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA13411; Fri, 23 Feb 2001 23:50:50 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA18868; Fri, 23 Feb 2001 23:50:45 -0800 (PST)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.3.Beta0+Sun/8.11.3.Beta0) id f1O7o4W27045 for ngtrans-dist; Fri, 23 Feb 2001 23:50:04 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6]) by sunroof.eng.sun.com (8.11.3.Beta0+Sun/8.11.3.Beta0) with ESMTP id f1O7ntG27038 for <ngtrans@sunroof.eng.sun.com>; Fri, 23 Feb 2001 23:49:55 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id XAA06629 for <ngtrans@sunroof.eng.sun.com>; Fri, 23 Feb 2001 23:49:56 -0800 (PST)
Received: from china.com (TCE-E-7-182-12.bta.net.cn [202.106.182.12]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id XAA24471 for <ngtrans@sunroof.eng.sun.com>; Fri, 23 Feb 2001 23:49:54 -0800 (PST)
Received: from china.com([10.1.7.101]) by china.com(JetMail 2.5.3.0) with SMTP id jm73a97cc16; Sat, 24 Feb 2001 07:42:34 -0000
Received: from loki.ietf.org([132.151.1.177]) by china.com(JetMail 2.5.3.0) with SMTP id jmd63a96dea5; Fri, 23 Feb 2001 16:42:28 -0000
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA07674 for ietf-123-outbound.02@ietf.org; Fri, 23 Feb 2001 11:35:00 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA05629 for <all-ietf@loki.ietf.org>; Fri, 23 Feb 2001 06:45:26 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27578; Fri, 23 Feb 2001 06:45:25 -0500 (EST)
Message-Id: <200102231145.GAA27578@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-natreq4ipv6-00.txt
Date: Fri, 23 Feb 2001 06:45:25 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org
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 : Short term NAT requirements for IPv6 transition Author(s) : C. Huitema Filename : draft-ietf-ngtrans-natreq4ipv6-00.txt Pages : 8 Date : 22-Feb-01 During the next few years, as the Ipv4 address space moves toward exhaustion, it is likely that the deployment of NAT will accelerate. By 2005, millions of NAT devices will likely be deployed on the Internet, both within enterprises and consumer households. Should those NAT devices not support either native Ipv6, or IPv6 transition mechanisms such as 6 to 4, the result would be significant delays in the deployment of IPv6. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-natreq4ipv6-00.txt 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-natreq4ipv6-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ngtrans-natreq4ipv6-00.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 Internet-Draft.
- (ngtrans) I-D ACTION:draft-ietf-ngtrans-natreq4ip… Internet-Drafts