Re: draft-ietf-ngtrans-ipv6-smtp-requirement-07.txt

itojun@itojun.org (Jun-ichiro itojun Hagino) Thu, 11 December 2003 03:47 UTC

Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBB3lUib079864 for <ietf-smtp-bks@above.proper.com>; Wed, 10 Dec 2003 19:47:30 -0800 (PST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id hBB3lU9V079863 for ietf-smtp-bks; Wed, 10 Dec 2003 19:47:30 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from coconut.itojun.org (coconut.itojun.org [219.101.47.130]) by above.proper.com (8.12.10/8.12.8) with ESMTP id hBB3lRib079850 for <ietf-smtp@imc.org>; Wed, 10 Dec 2003 19:47:28 -0800 (PST) (envelope-from itojun@itojun.org)
Received: by coconut.itojun.org (Postfix, from userid 1001) id AD33B94; Thu, 11 Dec 2003 12:47:13 +0900 (JST)
To: John C Klensin <john-ietf@jck.com>, hardie@qualcomm.com, Ned Freed <ned.freed@mrochek.com>, Pete Resnick <presnick@qualcomm.com>, Chris Newman <Chris.Newman@sun.com>, kre@munnari.OZ.AU
Cc: itojun@itojun.org
Cc: ietf-smtp@imc.org
Cc: motonori@econ.kyoto-u.ac.jp
Cc: randy@psg.com
Subject: Re: draft-ietf-ngtrans-ipv6-smtp-requirement-07.txt
In-Reply-To: Your message of "Thu, 23 Oct 2003 16:10:53 +0900 (JST)" <20031023071053.EFF7C96@coconut.itojun.org>
References: <20031023071053.EFF7C96@coconut.itojun.org>
X-Mailer: Cue version 0.6 (031125-1130/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Message-Id: <20031211034713.AD33B94@coconut.itojun.org>
Date: Thu, 11 Dec 2003 12:47:13 +0900
From: itojun@itojun.org
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

> 	an updated version of draft-ietf-ngtrans-ipv6-smtp-requirement
> 	is attached.
> 
> 	to ADs: it may not reflect all the coments i have received, but anyways
> 	better than nothing.  i think it should really be integrated into
> 	update to RFC2821 (instead of being standalone document).
> 	it is still using "ngtrans" in the name, however, it is suggested that
> 	the document should be discussed in APP area (there's no email-related
> 	WG exist at this point).

	ADs: let me know how to proceed on this document.  should we propose
	changes to RFC2821, or?  tnx.

itojun