[NAT] the future of the NAT working group
Scott Bradner <sob@harvard.edu> Thu, 18 October 2001 21:42 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 RAA20379; Thu, 18 Oct 2001 17:42:38 -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 RAA24407; Thu, 18 Oct 2001 17:31:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24378 for <nat@optimus.ietf.org>; Thu, 18 Oct 2001 17:31:30 -0400 (EDT)
Received: from eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20204 for <nat@ietf.org>; Thu, 18 Oct 2001 17:31:26 -0400 (EDT)
Received: (from sob@localhost) by eecs.harvard.edu (8.10.2/8.10.2) id f9ILUdV07894; Thu, 18 Oct 2001 17:30:39 -0400 (EDT)
Date: Thu, 18 Oct 2001 17:30:39 -0400
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200110182130.f9ILUdV07894@eecs.harvard.edu>
To: matt.holdrege@verizon.net, nat@ietf.org, srisuresh@yahoo.com
Subject: [NAT] the future of the NAT working group
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
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
- [NAT] the future of the NAT working group Scott Bradner
- [NAT] Re: the future of the NAT working group Matt Holdrege
- [NAT] Re: the future of the NAT working group Scott Bradner
- Re: [NAT] Re: the future of the NAT working group Matt Holdrege
- Re: [NAT] the future of the NAT working group Daniel Senie
- Re: [NAT] the future of the NAT working group Matt Holdrege
- RE: [NAT] Re: the future of the NAT working group Wang, Cliff
- Re: [NAT] Re: the future of the NAT working group Rajiv Raghunarayan
- RE: [NAT] Re: the future of the NAT working group Ed Van Horne
- Re: [NAT] Re: the future of the NAT working group Rajiv Raghunarayan
- Re: [NAT] Re: the future of the NAT working group Brian E Carpenter
- Re: [NAT] the future of the NAT working group Kuniaki Kondo
- Re: [NAT] the future of the NAT working group Allison Mankin
- [NAT] WG Last call on draft-ietf-nat-app-guide-06… Pyda Srisuresh
- Re: [NAT] WG Last call on draft-ietf-nat-app-guid… Pyda Srisuresh