(ngtrans) I-D ACTION:draft-ietf-ngtrans-ipv6-smtp-requirement-06.txt

Internet-Drafts@ietf.org Wed, 03 July 2002 10:35 UTC

Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04337 for <ngtrans-archive@lists.ietf.org>; Wed, 3 Jul 2002 06:35:11 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA12631; Wed, 3 Jul 2002 03:33:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA08655; Wed, 3 Jul 2002 03:32:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.4/8.12.4) with ESMTP id g63AW5k7025889 for <ngtrans-dist@sunroof.eng.sun.com>; Wed, 3 Jul 2002 03:32:05 -0700 (PDT)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.4/8.12.4/Submit) id g63AW4ob025888 for ngtrans-dist; Wed, 3 Jul 2002 03:32:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.12.4/8.12.4) with ESMTP id g63AVuk7025864 for <ngtrans@sunroof.eng.sun.com>; Wed, 3 Jul 2002 03:31:57 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id DAA25531 for <ngtrans@sunroof.eng.sun.com>; Wed, 3 Jul 2002 03:32:01 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA18103 for <ngtrans@sunroof.eng.sun.com>; Wed, 3 Jul 2002 04:32:00 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03948; Wed, 3 Jul 2002 06:31:11 -0400 (EDT)
Message-Id: <200207031031.GAA03948@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-ipv6-smtp-requirement-06.txt
Date: Wed, 03 Jul 2002 06:31:11 -0400
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		: SMTP operational experience in mixed IPv4/IPv6 
                          environements
	Author(s)	: M. Nakamura, J. Hagino
	Filename	: draft-ietf-ngtrans-ipv6-smtp-requirement-06.txt
	Pages		: 8
	Date		: 02-Jul-02
	
This document lists operational requirements for IPv6 SMTP and
IPv6-capable MX DNS records.  As IPv6 SMTP servers are deployed, it has
become apparent that certain configurations are necessary in
IPv6-capable MX DNS records for stable dual-stack (IPv4 and IPv6) SMTP
operation.  This document clarifies the problems that exist in the
transition period between IPv4 SMTP and IPv6 SMTP.  It also defines
operational requirements for stable IPv4/v6 SMTP operation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-ipv6-smtp-requirement-06.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ipv6-smtp-requirement-06.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-ipv6-smtp-requirement-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
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-ipv6-smtp-requirement-06.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-ipv6-smtp-requirement-06.txt>