Re: [abfab] AD review of draft-ietf-abfab-arch-09

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 17 December 2013 21:03 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: abfab@ietfa.amsl.com
Delivered-To: abfab@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFCB31A1F06 for <abfab@ietfa.amsl.com>; Tue, 17 Dec 2013 13:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zE2c3v5kD4Oz for <abfab@ietfa.amsl.com>; Tue, 17 Dec 2013 13:03:22 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 27C541A1F33 for <abfab@ietf.org>; Tue, 17 Dec 2013 13:03:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E0A23BE58; Tue, 17 Dec 2013 21:03:19 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pv5NB5Wn2wkg; Tue, 17 Dec 2013 21:03:18 +0000 (GMT)
Received: from [10.87.48.9] (unknown [86.42.29.6]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 89739BE57; Tue, 17 Dec 2013 21:03:18 +0000 (GMT)
Message-ID: <52B0BC16.7030703@cs.tcd.ie>
Date: Tue, 17 Dec 2013 21:03:18 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Sam Hartman <hartmans@painless-security.com>, Jim Schaad <ietf@augustcellars.com>
References: <52AF2A4C.5000304@cs.tcd.ie> <027c01cefaeb$79b97960$6d2c6c20$@augustcellars.com> <tsleh5bxofu.fsf@mit.edu>
In-Reply-To: <tsleh5bxofu.fsf@mit.edu>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: abfab@ietf.org
Subject: Re: [abfab] AD review of draft-ietf-abfab-arch-09
X-BeenThere: abfab@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application Bridging, Federated Authentication Beyond \(the web\)" <abfab.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abfab>, <mailto:abfab-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/abfab/>
List-Post: <mailto:abfab@ietf.org>
List-Help: <mailto:abfab-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abfab>, <mailto:abfab-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2013 21:03:25 -0000

On 12/17/2013 07:33 PM, Sam Hartman wrote:
> Couple of points.
> 
> Note that the MSK is encrypted even if you don't use RADIUS over TLS.
> The encryption is questionable (md5 as a stream cipher) but might
> randomly happen to be good enough for encrypting a randomly chosen key.
> for myself I'll choose to deploy with TLS rather than trusting that:-)

Yep.

> I don't mind removing the trust router references, but I also don't
> think it is problematic to leave them in.  This document points out
> there are multiple ways of solving the trust router solves.  I think
> it's fine to note that people are working on the trust router, one
> specific manifestation of the trust broker approach for managing the
> connection between RP and IDP.  Other approaches are discussed besides
> the trust broker deployment pattern.
> So, I don't think there's a dependency creater or implied.
> On the other hand, I don't mind removing the reference either.

Fair enough. So long as its sorta consistent and doesn't over
promise it'll be fine.

S.

> 
>