draft-ietf-ngtrans-ipv6-smtp-requirement
Jun-ichiro itojun Hagino <itojun@itojun.org> Wed, 09 July 2003 13:08 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29618 for <ietf-web-archive@odin.ietf.org>; Wed, 9 Jul 2003 09:08:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19aEbf-0006Jf-Mn for ietf-list@asgard.ietf.org; Wed, 09 Jul 2003 09:03:35 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19aAMQ-0005kI-Oy for ietf@asgard.ietf.org; Wed, 09 Jul 2003 04:31:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23794 for <ietf@ietf.org>; Wed, 9 Jul 2003 04:31:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aAMN-00053J-00 for ietf@ietf.org; Wed, 09 Jul 2003 04:31:31 -0400
Received: from coconut.itojun.org ([219.101.47.130]) by ietf-mx with esmtp (Exim 4.12) id 19aAMM-00053D-00 for ietf@ietf.org; Wed, 09 Jul 2003 04:31:30 -0400
Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 1924F9F for <ietf@ietf.org>; Wed, 9 Jul 2003 17:31:30 +0900 (JST)
Date: Wed, 09 Jul 2003 17:31:26 +0900
From: Jun-ichiro itojun Hagino <itojun@itojun.org>
Subject: draft-ietf-ngtrans-ipv6-smtp-requirement
Message-Id: <20030709083130.1924F9F@coconut.itojun.org>
To: undisclosed-recipients:;
Sender: owner-ietf@ietf.org
Precedence: bulk
------- Blind-Carbon-Copy To: iesg@ietf.org Cc: ngtrans@sunroof.eng.sun.com, Ned Freed <ned.freed@mrochek.com>, Ted Hardie <hardie@qualcomm.com> Subject: draft-ietf-ngtrans-ipv6-smtp-requirement X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 From: itojun@iijlab.net Date: Wed, 09 Jul 2003 17:31:26 +0900 Sender: itojun@itojun.org a couple of IETFs ago, it was suggested at the ngtrans wg meeting that the document draft-ietf-ngtrans-ipv6-smtp-requirement-xx "should be handed to SMTP experts in application area". since then, there has been no actions taken. the fact is, there is no active working group for SMTP and email-related activities. also ngtrans wg is concluded. therefore, the document is in "zombie" state. I still want the document (or the contents of it) be published, as it contains critical guidelines for IPv6/v4 dual stack SMTP operation. I would like to ask IESG to decide and take appropriate actions, such as: - poke SMTP experts, let them work on the topic and produce an RFC - let me handle the document as an individual submission and publish it as an RFC thanks. itojun ------- End of Blind-Carbon-Copy
- draft-ietf-ngtrans-ipv6-smtp-requirement Jun-ichiro itojun Hagino
- Re: draft-ietf-ngtrans-ipv6-smtp-requirement Cyrus Daboo
- Re: draft-ietf-ngtrans-ipv6-smtp-requirement itojun