Re: [proxies] [IETF Proxy] Next Steps

"Dan Harkins" <dharkins@lounge.org> Fri, 02 May 2008 23:06 UTC

Return-Path: <proxies-bounces@ietf.org>
X-Original-To: proxies-archive@ietf.org
Delivered-To: ietfarch-proxies-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D73313A6D1B; Fri, 2 May 2008 16:06:50 -0700 (PDT)
X-Original-To: proxies@core3.amsl.com
Delivered-To: proxies@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF9253A6D1B for <proxies@core3.amsl.com>; Fri, 2 May 2008 16:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.861
X-Spam-Level:
X-Spam-Status: No, score=-1.861 tagged_above=-999 required=5 tests=[AWL=0.404, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i4b+jIVicIdD for <proxies@core3.amsl.com>; Fri, 2 May 2008 16:06:49 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by core3.amsl.com (Postfix) with ESMTP id 040113A6CEE for <proxies@ietf.org>; Fri, 2 May 2008 16:06:49 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id DE38AA8882BA; Fri, 2 May 2008 16:06:50 -0700 (PDT)
Received: from 216.31.249.246 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Fri, 2 May 2008 16:06:51 -0700 (PDT)
Message-ID: <273c5c8bff26c3c057519da2b038e1ba.squirrel@www.trepanning.net>
In-Reply-To: <200804171550.48931.stefan.winter@restena.lu>
References: <7.0.1.0.2.20080416172531.02401228@nist.gov> <200804171550.48931.stefan.winter@restena.lu>
Date: Fri, 2 May 2008 16:06:51 -0700 (PDT)
From: "Dan Harkins" <dharkins@lounge.org>
To: "Stefan Winter" <stefan.winter@restena.lu>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Cc: proxies@ietf.org
Subject: Re: [proxies] [IETF Proxy] Next Steps
X-BeenThere: proxies@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for ad hoc group interested in security and proxies <proxies.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/proxies>, <mailto:proxies-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:proxies@ietf.org>
List-Help: <mailto:proxies-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/proxies>, <mailto:proxies-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: proxies-bounces@ietf.org
Errors-To: proxies-bounces@ietf.org

  Hi Stefan,

On Thu, April 17, 2008 6:50 am, Stefan Winter wrote:
[snip]
> To me, the above model seems to have two role models of proxies:
>
> - the "technical" proxy - to aggregate or channelize traffic for
> managability
> reasons
> - the "political" proxy - due to the requirement or wish to inspect,
> control
> or modify traffic while in flight
>
> The first kind might go away with dynamic discovery between service
> provider
> and home server; the second might most certainly not. So my answer to the
> proxy problem in general is: we will have to live with them.

  This political proxy thing concerns me. The only traffic that a AAA proxy
could inspect, control or modify is AAA traffic. So what this entity would
do is glean information about who is using what network where and, in
some cases, prevent some people somewhere from using some network.

  These are not things that I think we _have_ to deal with especially in
a technical forum. These are issues that a customer will require a vendor
of AAA product to support, in much the same way that "lawful intercept"
is a political add-on to a technical solution-- e.g. the IPsec WG did not
architect "lawful intercept" into RFC2401 but people that have implemented
IPsec have added backdoors into their products to allow for it. I'm sure
that some RFP somewhere will mandate, if it doesn't already, that
evesdropping and controlling entities be required in between AAA client
and AAA server but that isn't really the problemspace we're dealing with.

  I have heard many other reasons why AAA proxies must exist. If a magic
wand made all those reasons disappear I really hope this political
justification would not keep them around. (Note: I'm not entertaining the
notion of getting rid of proxies, just theorizing, so don't attack me).

  This does highlight threats though. It's not just that proxies can
listen to AAA exchanges, they can glean information out of AAA exchanges,
and they can constrain or deny service that should otherwise be
unconstrained or allowed.

  Dan.





_______________________________________________
Proxies mailing list
Proxies@ietf.org
https://www.ietf.org/mailman/listinfo/proxies