Re: [abfab] Direction Forward for aaa-saml

Sam Hartman <hartmans@painless-security.com> Wed, 22 July 2015 16:15 UTC

Return-Path: <hartmans@painless-security.com>
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 D1C651A6F10 for <abfab@ietfa.amsl.com>; Wed, 22 Jul 2015 09:15:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level:
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 B-H1YMjSXvtm for <abfab@ietfa.amsl.com>; Wed, 22 Jul 2015 09:15:08 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BC9A1A1F70 for <abfab@ietf.org>; Wed, 22 Jul 2015 09:15:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 06E7C2075D; Wed, 22 Jul 2015 12:14:42 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3nbfD0VRpB0; Wed, 22 Jul 2015 12:14:41 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (dhcp-89db.meeting.ietf.org [31.133.137.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed, 22 Jul 2015 12:14:41 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id B98B28867F; Wed, 22 Jul 2015 12:15:04 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: Alejandro =?utf-8?B?UMOpcmV6IE3DqW5kZXo=?= <alex@um.es>
References: <tslwpxsy0ql.fsf@mit.edu> <8E4E5965-0E43-4ABD-8853-8A6C7C6926C5@mnt.se> <tsloaj4xzvr.fsf@mit.edu> <0B96365A-4F6B-427A-9A87-70F069473F84@mnt.se> <tsl7fpsxrve.fsf@mit.edu> <0A08B89E-5533-4E34-9014-97C0D7877B6E@osu.edu> <tslio9cw8yd.fsf@mit.edu> <D143C9FB-F878-49C1-89C4-6A494714A3EC@mnt.se> <tslegk0w7iw.fsf@mit.edu> <1FA8CCED-221E-4A88-B525-BF46FAA53A3F@mnt.se> <55AFC0E3.8030500@um.es>
Date: Wed, 22 Jul 2015 12:15:04 -0400
In-Reply-To: <55AFC0E3.8030500@um.es> ("Alejandro =?utf-8?Q?P=C3=A9rez_M?= =?utf-8?Q?=C3=A9ndez=22's?= message of "Wed, 22 Jul 2015 18:12:19 +0200")
Message-ID: <tslpp3kuq2f.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/abfab/4DR1Z31iIP5o9T4nM4HFYXXclkg>
Cc: abfab@ietf.org
Subject: Re: [abfab] Direction Forward for aaa-saml
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 22 Jul 2015 16:15:10 -0000

>>>>> "Alejandro" == Alejandro Pérez Méndez <alex@um.es> writes:

    Alejandro> I might be mistaken, but wasn't that what we wanted to
    Alejandro> avoid in the first place when we decided not to use the
    Alejandro> RADIUS URI scheme from my original proposal?  I guess
    Alejandro> having an endpoint for radsec will require to define how
    Alejandro> the "Location" values will look like, and they should be
    Alejandro> in a URI format as well.

Standardizing a URI that /looked like
radsec://host:port would be *lots* easier than the URI you proposed.
However, yes I believe even that's work I don't think belongs in ABFAB
or aaa-saml.