IETF Logo Mail Archive

[NAT] Re: IESG review of draft-ietf-nat-interface-framework-03.txt

Pyda Srisuresh <srisuresh@yahoo.com> Thu, 27 September 2001 23:29 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 TAA15362; Thu, 27 Sep 2001 19:29:54 -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 TAA07555; Thu, 27 Sep 2001 19:14:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07524 for <nat@ns.ietf.org>; Thu, 27 Sep 2001 19:14:45 -0400 (EDT)
Received: from web13804.mail.yahoo.com (web13804.mail.yahoo.com [216.136.175.14]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA15139 for <nat@ietf.org>; Thu, 27 Sep 2001 19:14:45 -0400 (EDT)
Message-ID: <20010927231447.55672.qmail@web13804.mail.yahoo.com>
Received: from [66.89.112.150] by web13804.mail.yahoo.com via HTTP; Thu, 27 Sep 2001 16:14:47 PDT
Date: Thu, 27 Sep 2001 16:14:47 -0700
From: Pyda Srisuresh <srisuresh@yahoo.com>
To: nat@ietf.org
Cc: srisuresh@yahoo.com, Allison Mankin <mankin@east.isi.edu>, Scott Bradner <sob@harvard.edu>, Matt Holdrege <matt@ipverse.com>
In-Reply-To: <20010927080551.84192.qmail@web13808.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [NAT] Re: IESG review of draft-ietf-nat-interface-framework-03.txt
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

Folks,

As you might have seen by now, the IESG response to 
<draft-ietf-nat-interface-framework-03.txt>  raised a few
serious points. Subsequent to the email response, I had
a couple of e-mail exchanges with the ADs and per the AD's
advice, I am listing below a plan of action.

   1. Interest level for the draft from the WG: 

      The IESG didnt find sufficient discussion on the draft on the 
      mailing list, even though I did recieve private e-mails from 
      some individuals. The IESG wants to assess what the interest
      level is for the draft.

      Matt and I would appreciate if you could respond to the following
      questionaire over the list. Thanks.
      (a) Is the document relevant to the WG?
      (b) Is there interest in seeing the document to completion 
          within the WG?
      (c) State reasons for your support or non-support of the document
          in the WG.

   2. Reference to MIDCOM:

      This document is focussed on discussing NAT resources and an 
      interface by which an external agent can influence NAT resources
      and operation. As such, the reference to MIDCOM was done so the 
      MIDCOM protocol could benefit from it. However, the IESG had
      gotten the impression that this was mandating a requirement on 
      MIDCOM protocol. 

      I dont have an issue with excising reference to MIDCOM from the 
      draft(in the case we choose to pursue). Please let me know if
      believe, this should not be the done.

   3. Lastly, as for the document quality issue, I will try and find a
      co-author and spend additional effort fixing the document - only
      when there is  manifestation of sufficient interest from the list. 
      
Thanks you for your time.

Regards,
suresh 

=====


__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

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

v2.23.0 | Report a Bug | By Email