Re: [Pana] IESG discussions on draft-ohba-pana-relay

Glen Zorn <gwz@net-zen.net> Fri, 24 June 2011 01:39 UTC

Return-Path: <gwz@net-zen.net>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB32A11E81B6 for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 18:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOFd2W49vzjd for <pana@ietfa.amsl.com>; Thu, 23 Jun 2011 18:39:18 -0700 (PDT)
Received: from smtpauth12.prod.mesa1.secureserver.net (smtpauth12.prod.mesa1.secureserver.net [64.202.165.35]) by ietfa.amsl.com (Postfix) with SMTP id 490DF11E80A2 for <pana@ietf.org>; Thu, 23 Jun 2011 18:39:18 -0700 (PDT)
Received: (qmail 22794 invoked from network); 24 Jun 2011 01:39:17 -0000
Received: from unknown (124.122.156.23) by smtpauth12.prod.mesa1.secureserver.net (64.202.165.35) with ESMTP; 24 Jun 2011 01:39:16 -0000
Message-ID: <4E03EABF.501@net-zen.net>
Date: Fri, 24 Jun 2011 08:39:11 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4DF04217.3080304@toshiba.co.jp> <6491375641982933760@unknownmsgid> <BANLkTinVZ2Bvd6A+znQTiB7X-P6XXh3Cow@mail.gmail.com> <4E037743.2060602@gridmerge.com> <4E037A9D.8080200@piuha.net>
In-Reply-To: <4E037A9D.8080200@piuha.net>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------060708000504060207020101"
Cc: draft-ohba-pana-relay@tools.ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>, pana@ietf.org
Subject: Re: [Pana] IESG discussions on draft-ohba-pana-relay
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 01:39:19 -0000

On 6/24/2011 12:40 AM, Jari Arkko wrote:

> We discussed this draft today. The remaining Discuss was about how
> mandatory we should make IPsec. You had discussed about a SHOULD with
> Stephen. I suggested that while interoperability is useful and
> mandatory-to-implement mechanisms are good for it, we also have to talk
> about how much value we bring with a security mechanism. In this case
> there are some issues like MITMs able to block PANA packets. However,
> some of these vulnerabilities are not helped by relay - PAA security, as
> the relay can still do bad things, and because ARP/ND vulnerabilities
> between the client and relay in any case make it possible to become a
> MITM. Stephen had some suggested text that I agree with:
> 
> "PRE/PAA security is OPTIONAL since PANA messages are designed to be
> used in untrusted networks, but if cryptographic mechanism is supported,
> it SHOULD be IPsec."

This is an interesting statement.  Just one question: if it is not
possible to use the protocol in a secure fashion (the claim being that
MITM attacks are impossible to prevent), how is it that the protocol is
"designed to be used in untrusted networks"?

...