Re: [Gen-art] Assignment: draft-ietf-ediint-as3-04.txt

"Joel M. Halpern" <joel@stevecrocker.com> Mon, 27 February 2006 20:15 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDom4-0006kJ-TQ; Mon, 27 Feb 2006 15:15:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDom4-0006kB-6z for gen-art@ietf.org; Mon, 27 Feb 2006 15:15:16 -0500
Received: from mail.shinkuro.com ([216.194.124.237] helo=execdsl.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDom2-00005Z-Uy for gen-art@ietf.org; Mon, 27 Feb 2006 15:15:16 -0500
Received: from [69.17.17.130] (HELO JMHLap3.stevecrocker.com) by execdsl.com (CommuniGate Pro SMTP 4.2.7) with ESMTP id 13041938; Mon, 27 Feb 2006 13:11:12 -0700
Message-Id: <7.0.1.0.0.20060227150445.0343d710@stevecrocker.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 27 Feb 2006 15:15:10 -0500
To: Mary Barnes <mary.barnes@nortel.com>, gen-art@ietf.org
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: Re: [Gen-art] Assignment: draft-ietf-ediint-as3-04.txt
In-Reply-To: <E3F9D87C63E2774390FE67C924EC99BB0AB3D68D@zrc2hxm1.corp.nor tel.com>
References: <E3F9D87C63E2774390FE67C924EC99BB0AB3D68D@zrc2hxm1.corp.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: sah@428cobrajet.net
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org

This document is ready for publication as an Informational RFC.

However, it has a MUST reference to an internet-draft [MURRAY} 
defining securiing FTP with TLS.  The drafft is listed as a normative 
reference.  Presumably, therefore, this draft can not be published as 
an RFC until that one is also ready for publication.

minor:  Given the document name, abbreviated title, and multiple 
uses, it would be nice if there were a definition of AS3?  Just a short one?

Yours,
Joel M. Halpern

--------------
APP FTP Transport for Secure Peer-to-Peer Business Data Interchange 
over the Internet
     draft-ietf-ediint-as3-04.txt
AD: Scott Hollenbeck
Reviewer: Joel Halpern


_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art