RE: [Raven] Internet Draft comments

Chris Savage <chris.savage@crblaw.com> Tue, 15 February 2000 18:31 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 NAA17549 for <raven-archive@ietf.org>; Tue, 15 Feb 2000 13:31:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA12535; Tue, 15 Feb 2000 12:35:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA12502 for <raven@optimus.ietf.org>; Tue, 15 Feb 2000 12:35:50 -0500 (EST)
Received: from crbexch.crblaw.com (webaccess.crblaw.com [216.88.51.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15655 for <raven@ietf.org>; Tue, 15 Feb 2000 12:37:24 -0500 (EST)
Received: by webaccess.crblaw.com with Internet Mail Service (5.5.2448.0) id <101A8T9C>; Tue, 15 Feb 2000 12:42:49 -0500
Message-ID: <D1A6C6C41B4CD311965D00C04F2C8D5145277D@webaccess.crblaw.com>
From: Chris Savage <chris.savage@crblaw.com>
To: "'P.J. Ponder'" <ponder@freenet.tlh.fl.us>, "IETF Wiretapping List (E-mail)" <raven@ietf.org>
Subject: RE: [Raven] Internet Draft comments
Date: Tue, 15 Feb 2000 12:42:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: raven-admin@ietf.org
Errors-To: raven-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Raven Discussion List <raven.ietf.org>
X-BeenThere: raven@ietf.org

>-----Original Message-----
>From: P.J. Ponder [mailto:ponder@freenet.tlh.fl.us]
>Sent: Tuesday, February 15, 2000 11:15 AM
>To: raven@ietf.org
>Subject: [Raven] Internet Draft comments
>
>
>In the interest of nudging the list back toward the actual draft of the
>wiretapping document, I think the document as originally 
>posted is concise
>and addresses the major points that are the subject of the questions
>raised.  
>
>There were some comments about the definition of 
>'wire-tapping', and some
>other more or less substantive comments in the rest of the 
>draft.  These
>comments may deserve further discussion.
>
>Overall, though, I think the draft is more than adequate as it 
>stands to
>set forth a reasoned and articulate policy statement for the IETF, the
>IAB, and the IESG regarding wiretapping.  I don't see any 
>glaring errors
>or 'show-stoppers' in the draft, and I am willing to argue that we have
>reached that state of grace once described as 'rough consensus'.  
>
>We could debate grammatical niceties and diction, but in terms of
>substance, I think we have a policy statement that makes sense 
>and cleary
>states a position.

As the (AFAIK) only proponent of a significant number of word changes, let
me say that I agree.

As I said earlier, the point of my proposed changes was to clarify the
draft's evident intent, not to make actual, substantive changes.  The only
possible exception was that, having defined "wiretapping" for purposes of
the document to relate to communications on the 'net, an example that
asserted that certain telco practices would "be" wiretapping seemed
inconsistent; that discussion received, I think, my heaviest suggested
editorial pen.  But even that was intended to clarify and tighten up the
discussion, not to change its basic thrust in any way.

Time to declare victory and go home?

Chris S.


*************************************************************************** 
This electronic mail transmission may contain confidential or 
privileged information.  If you believe that you have received the 
message in error, please notify the sender by reply transmission 
and delete the message without copying or disclosing it. 
***************************************************************************

_______________________________________________
raven mailing list
raven@ietf.org
http://www.ietf.org/mailman/listinfo/raven