RE: [Raven] Comments on Draft -- Take 2

Chris Savage <chris.savage@crblaw.com> Mon, 07 February 2000 16:12 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 LAA13702 for <raven-archive@ietf.org>; Mon, 7 Feb 2000 11:12:22 -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 KAA21640; Mon, 7 Feb 2000 10:49:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA21611 for <raven@optimus.ietf.org>; Mon, 7 Feb 2000 10:49:36 -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 KAA13238 for <raven@ietf.org>; Mon, 7 Feb 2000 10:51:00 -0500 (EST)
Received: by webaccess.crblaw.com with Internet Mail Service (5.5.2448.0) id <1KQ81XAH>; Mon, 7 Feb 2000 10:56:39 -0500
Message-ID: <D1A6C6C41B4CD311965D00C04F2C8D514526EB@webaccess.crblaw.com>
From: Chris Savage <chris.savage@crblaw.com>
To: 'Lyal Collins' <lyalc@ozemail.com.au>, Chris Savage <chris.savage@crblaw.com>, "IETF Wiretapping List (E-mail)" <raven@ietf.org>
Subject: RE: [Raven] Comments on Draft -- Take 2
Date: Mon, 07 Feb 2000 10:56:33 -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: Lyal Collins [mailto:lyalc@ozemail.com.au]
>Sent: Friday, February 04, 2000 8:56 PM
>To: Chris Savage; IETF Wiretapping List (E-mail)
>Subject: RE: [Raven] Comments on Draft -- Take 2
>
>
>I'm not entirely comfortable with the summary position, which focusses
>heavily on national laws.
>While national laws have one level of impact on wiretapping, the global
>nature of the Internet means it is no more costly (and probably more
>convenient) for a LE agency in one jurisdiction to monitor 
>communications in
>an external jurisdiction.
>
>As one example, this may free LE from the burden of having to 
>comply with
>local jurisdiction approval/warrant processes by tapping 
>communications with
>"out-of-jurisdiction" entities, who may or may not be invovled in
>inappropriate activities.
>
>Think "LAPD-style wiretapping" in every state/country, not 
>just a single
>city.
>
>Is the resulting assumption, that IETF does not see itself 
>having a global
>role in this matter, true?
>
>If so, is there an indication of how many countries will need to have a
>"common" requirement for tapping before IETF acts further in 
>this area (in
>either the pro- or anti- directions)?
>
>And, have we a definitive count of such countries?
>There are at least 4 I can think of (US, Holland, Australia 
>and China spring
>to mind).

IMHO this portion of the draft is pointing out that as matters stand today,
the divergence of national laws regarding wiretapping is one thing that
makes an IETF standard to facilitate tapping a bad or unworkable idea.  In a
totally hypothetical world in which (say) countries making up 95% of 'net
traffic and users had effectively identical wiretapping requirements,
divergence of national laws would not be as strong an argument against IETF
activity in this area.  It does not follow that the IETF, in such a
situation, either would or should create a standard.  It is just that in
such a situation the reasoning might have to be a bit different.  As someone
famous once said, "sufficient unto the day is the evil thereof..."

Chris S.
All views/opinions my own


*************************************************************************** 
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