RE: [Raven] Comments on Draft -- Take 2
Chris Savage <chris.savage@crblaw.com> Mon, 07 February 2000 17:23 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 MAA15937 for <raven-archive@ietf.org>; Mon, 7 Feb 2000 12:23:01 -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 MAA25233; Mon, 7 Feb 2000 12:09:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA25207 for <raven@optimus.ietf.org>; Mon, 7 Feb 2000 12:09: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 MAA15626 for <raven@ietf.org>; Mon, 7 Feb 2000 12:11:16 -0500 (EST)
Received: by webaccess.crblaw.com with Internet Mail Service (5.5.2448.0) id <1KQ81X1B>; Mon, 7 Feb 2000 12:14:02 -0500
Message-ID: <D1A6C6C41B4CD311965D00C04F2C8D514526EF@webaccess.crblaw.com>
From: Chris Savage <chris.savage@crblaw.com>
To: 'chefren' <chefren@pi.net>, raven@ietf.org
Subject: RE: [Raven] Comments on Draft -- Take 2
Date: Mon, 07 Feb 2000 12:13:59 -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: chefren [mailto:chefren@pi.net] >Sent: Monday, February 07, 2000 11:39 AM >To: raven@ietf.org >Subject: RE: [Raven] Comments on Draft -- Take 2 > > >On 7 Feb 00, at 10:56, Chris Savage wrote: > >> 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. > >Is this "tested"? I don't know of divergence of national >laws, to the contrary, all EU countries are lining up. My own knowledge is most focused on US/CALEA issues. AFAIK the specific requirements of CALEA (which applies, one will recall, only to carriers and manufacturers of carrier equipment, not to "information service" providers) are unique to the US in various respects. Other countries have other specific things that one has to do, as I understand it. Some time ago I pointed out that to actually determine the degree of difference/overlap between the legal requirements of various countries would entail a non-trivial amount of lawyer time and effort. That said, due to various quirkiness-es of US law, I would suspect that what CALEA will require for particular carriers/manufacturers will be different from what other countries will require. Note also that in most countries, I think, people who are not carriers (e.g., in the US, ISPs, backbone providers) are still subject to getting served with a court order to cough up information, allow the attachment of listening devices, etc. The questions in such cases are (a) what kind of a showing does the LEA have to make to the judge to get the order? and (b) who bears any extraordinary costs associated with the activity? From this perspective, CALEA is a lot more about allocating costs than about technical capabilities (although there is obviously a large "technical capabilities" component to it). So, to answer your question directly, no, AFAIK my proposition has not been "tested" -- the "testing" is what would take a bunch of lawyers a bunch of (high-cost) hours to confirm. But it strikes me as having a very high likelihood of being true. >> 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..." > > >I see a strong kind of "not invented here" resistance. > >There is no will to think about what wiretap standard could >be there is only an "against". It seems to me that the predominant opinion on the list is that wiretapping by LEAs is a (maybe) necessary evil, but plainly an evil that the IETF should not facilitate. Also, that any "legal" wiretapping regime could be abused by either oppressive authorities (insert your favorite villainous regime here) or by out-of-sanction LEAs (the LAPD example), not to mention random Bad Guys who somehow get in a position to use the capability. This leads to a consensus that on the whole facilitating the process from a technical perspective is, net-net-net, a Bad Thing, as opposed to a Good Thing. The point at this late stage of the discussion is not to claim that your counter-arguments have zero persuasive power. Perhaps by virtue my own (lawyer) training (every issue has at least two sides), it seems clear to me that the persuasive power of your arguments is well above zero. Even so, those arguments have failed, in this forum, to persuade very many people. Again, maybe due to my training, the notion that good, sensible arguments might lose (and, yes, I know some on the list would not credit yours in that way) is not shocking -- it happens every day. Either because better, more sensible arguments prevail, or because the decision-maker perceives the actual issue to be one as to which the arguments are not quite as strong or relevant as their proponent would like. > >IETF could perfectly design a auditable version of tcpdump. I'm not techie enough to comment on this. >A good tap just taps everything to and from a programmed IP >address without editing the content in any way. That's all, >nothing more and nothing less. Isn't that do-able today? >"Divergence of national laws", sigh... We still live in a multi-national world. Perhaps we always will. Don't think of it as social bug, think of it as a social feature... 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
- [Raven] Comments on Draft -- Take 2 Chris Savage
- Re: [Raven] Comments on Draft -- Take 2 Ben Laurie
- RE: [Raven] Comments on Draft -- Take 2 Lyal Collins
- RE: [Raven] Comments on Draft -- Take 2 chefren
- RE: [Raven] Comments on Draft -- Take 2 Chris Savage
- RE: [Raven] Comments on Draft -- Take 2 Chris Savage
- RE: [Raven] Comments on Draft -- Take 2 chefren
- RE: [Raven] Comments on Draft -- Take 2 Chris Savage
- RE: [Raven] Comments on Draft -- Take 2 chefren
- RE: [Raven] Comments on Draft -- Take 2 Ed Stone
- Re: [Raven] Comments on Draft -- Take 2 Christian Price
- Re: [Raven] Comments on Draft -- Take 2 Ed Stone
- Re: [Raven] Comments on Draft -- Take 2 chefren
- RE: [Raven] Comments on Draft -- Take 2 Chris Savage
- Re: [Raven] Comments on Draft -- Take 2 Ge' Weijers
- RE: [Raven] Comments on Draft -- Take 2 chefren
- [Raven] US NSA/DoD Wiretap funding Ed Stone
- Re: [Raven] US NSA/DoD Wiretap funding chefren