Re: [NAT] the future of the NAT working group

Daniel Senie <dts@senie.com> Thu, 18 October 2001 22:34 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20930; Thu, 18 Oct 2001 18:34:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA26042; Thu, 18 Oct 2001 18:24:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA26018 for <nat@optimus.ietf.org>; Thu, 18 Oct 2001 18:24:44 -0400 (EDT)
Received: from garlic.amaranth.net (garlic.amaranth.net [216.235.243.195]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20830 for <nat@ietf.org>; Thu, 18 Oct 2001 18:24:39 -0400 (EDT)
Received: from yarrow.senie.com (amaranth.ne.mediaone.net [24.218.3.14] (may be forged)) (authenticated (0 bits)) by garlic.amaranth.net (8.11.6/8.11.6) with ESMTP id f9IMO9R25434 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Thu, 18 Oct 2001 18:24:10 -0400
Message-Id: <5.1.0.14.2.20011018182316.040c0af0@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 18 Oct 2001 18:24:09 -0400
To: Scott Bradner <sob@harvard.edu>, matt.holdrege@verizon.net, nat@ietf.org, srisuresh@yahoo.com
From: Daniel Senie <dts@senie.com>
Subject: Re: [NAT] the future of the NAT working group
In-Reply-To: <200110182130.f9ILUdV07894@eecs.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Network Address Translation <nat.ietf.org>
X-BeenThere: nat@ietf.org

I had exchanged email with Matt about taking the App Friendly doc to Last 
Call some time ago. Any reason we haven't done this yet? I thought we were 
about done just after Minneapolis, and have been waiting for last call or 
any other feedback.

Dan

At 05:30 PM 10/18/01, Scott  Bradner wrote:

>Matt, Srisuresh and the NAT WG,
>
>         Allison and I have been discussing the status of the NAT WG.  It is
>our conclusion that it should close.  The working group has achieved its
>main goals and published a number of RFCs, it should be seen as a success
>but it is now time to conclude it.
>
>There are two WG documents in progress that would be useful to have
>finished.  One is the NAT MIB, which has potential to be a useful
>document, and we would like opinions as to whether to
>
>1. have it completed as an individual submission (the nat mailing list
>    be used discussion, as we usually keep concluded working
>    group mailing lists alive).
>2. have it transferred to another working group's charter - one
>    candidate is midcom.
>
>The other is the NAT Friendly Application Design Guidelines.  We
>have not seen progress on this and think this can continue on the
>basis of being an individual informational, if energy increases.
>
>We saw insufficient expression of support for the framework
>document, so we do not not think it is worth the considerable effort that
>would be required to revise it to fix the issues that the IESG had with it.
>
>Scott
>
>_______________________________________________
>nat mailing list
>nat@ietf.org
>http://www1.ietf.org/mailman/listinfo/nat

-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.                    http://www.amaranth.com


_______________________________________________
nat mailing list
nat@ietf.org
http://www1.ietf.org/mailman/listinfo/nat