RE: [Raven] Internet Draft comments
Harald Tveit Alvestrand <Harald@Alvestrand.no> Mon, 21 February 2000 00:26 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 TAA13924 for <raven-archive@ietf.org>; Sun, 20 Feb 2000 19:26:32 -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 TAA19022; Sun, 20 Feb 2000 19:13:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA18955 for <raven@optimus.ietf.org>; Sun, 20 Feb 2000 19:12:58 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13878 for <raven@ietf.org>; Sun, 20 Feb 2000 19:14:38 -0500 (EST)
Received: from alden ([10.128.167.143]) by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id BAA21880; Mon, 21 Feb 2000 01:14:21 +0100
Message-Id: <4.2.0.58.20000221010724.0349c1f0@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Mon, 21 Feb 2000 01:13:05 +0100
To: Ed Stone <estone@synernet.com>, raven@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: RE: [Raven] Internet Draft comments
In-Reply-To: <4.2.0.58.20000216094658.009993b0@fast.synernet.com>
References: <4.2.0.58.20000216152627.0278bba0@dokka.maxware.no> <D1A6C6C41B4CD311965D00C04F2C8D5145277D@webaccess.crblaw.co m>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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
At 09:57 16.02.00 -0500, Ed Stone wrote: >The draft is a good general document, in my view, but it should be judged >in light of how it will be applied. For example, if evaluated as a limited >technical document expressing a general policy, I think it serves that >purpose adequately. If evaluated as a clear, complete and unambiguous >statement that plugs all loopholes that government lawyers may want to >find in it by way of pointing to industry and user support for some kind >of intrusion, experience teaches us that any crevice will be so exploited. Anyone who thinks you can get a loophole-free document that is also understandable either has not worked much with standards or laws, or worked too long with them. I think the former interpretation is the only sensible one. >If the draft needs only to serve the former purpose, I think it is >sufficient, with one modification: the wiretapping definition should >include intercepts whether they are targeted or untargeted, whether >processed in realtime or stored for potential subsequent processing. I don't believe we can do that without declaring traffic statistics as wiretaps. Or spending an extremely long time arguing about the borderline cases. Harald Harald -- Harald Tveit Alvestrand, EDB Maxware, Norway Harald.Alvestrand@edb.maxware.no _______________________________________________ raven mailing list raven@ietf.org http://www.ietf.org/mailman/listinfo/raven
- [Raven] Internet Draft comments P.J. Ponder
- RE: [Raven] Internet Draft comments Chris Savage
- RE: [Raven] Internet Draft comments Harald Tveit Alvestrand
- Re: [Raven] Internet Draft comments Richard Payne
- RE: [Raven] Internet Draft comments Ed Stone
- RE: [Raven] Internet Draft comments Harald Tveit Alvestrand