Re: [abfab] Direction Forward for aaa-saml

Alejandro Pérez Méndez <alex@um.es> Wed, 22 July 2015 13:42 UTC

Return-Path: <alex@um.es>
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 F3E261A6FF1 for <abfab@ietfa.amsl.com>; Wed, 22 Jul 2015 06:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level:
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 lCqObe-GFBoD for <abfab@ietfa.amsl.com>; Wed, 22 Jul 2015 06:42:52 -0700 (PDT)
Received: from xenon21.um.es (xenon21.um.es [155.54.212.161]) by ietfa.amsl.com (Postfix) with ESMTP id 9060B1A702D for <abfab@ietf.org>; Wed, 22 Jul 2015 06:42:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by xenon21.um.es (Postfix) with ESMTP id 28D28403C9 for <abfab@ietf.org>; Wed, 22 Jul 2015 15:42:43 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon21.um.es
Received: from xenon21.um.es ([127.0.0.1]) by localhost (xenon21.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id PzA+sqiRflcE for <abfab@ietf.org>; Wed, 22 Jul 2015 15:42:43 +0200 (CEST)
Received: from [192.168.20.74] (186.160.broadband14.iol.cz [90.181.160.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: alex) by xenon21.um.es (Postfix) with ESMTPSA id E0E8A403C7 for <abfab@ietf.org>; Wed, 22 Jul 2015 15:42:42 +0200 (CEST)
To: abfab@ietf.org
References: <tslwpxsy0ql.fsf@mit.edu>
From: =?UTF-8?Q?Alejandro_P=c3=a9rez_M=c3=a9ndez?= <alex@um.es>
Message-ID: <55AF9DD1.6060002@um.es>
Date: Wed, 22 Jul 2015 15:42:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <tslwpxsy0ql.fsf@mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/abfab/lQgh2S_W3lckj3COxvIVLVMl76U>
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 13:42:55 -0000

Hi Sam,

that's exactly what I extracted from the discussion in the session, thanks.

Regards,
Alejandro

El 22/07/15 a las 11:56, Sam Hartman escribió:
> Leif, I wanted to write up my understanding of our proposed direction
> forward, just in case things take longer than we anticipate  to
> implement.
>
> During the meeting  Monday we discussed Alejandro's proposal.
>
> He proposes adding two new role descriptor subtypes: Radiusidpdescriptor
> and Radiusrpdescriptor.
> That seems great.
>
> He proposes adding a RadiusIdpService and RadiusRpService of
> EndpointType as well.
>
> In the meeting we discussed that we really aren't specifying an
> edpoint.  In particular, the location of the service is implicit in this
> RADIUS binding.  It's possible we might describe something in the future
> where we included radsec endpoints and keys in metadata, but that's not
> what we need now.
>
> However we also discovered that a role descriptor doesn't actually need
> any EndpointType subclasses.  So, instead, Alejandro will create a
> different extension to rolldescriptor to include the naming information
> we need.
>
> This will allow us to avoid registering an unresolvable URI to describe
> the security name of a RADIUS entity.
>
> Have I accurately summarized what we discussed?
> If so, I'd like to solicit any comments from the list.
>
> --Sam
>
> _______________________________________________
> abfab mailing list
> abfab@ietf.org
> https://www.ietf.org/mailman/listinfo/abfab