Re: [abfab] Fwd: New Version Notification for draft-perez-abfab-gss-remote-attr-00.txt

Alejandro Pérez Méndez <alex@um.es> Mon, 05 October 2015 09:30 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 E5FCF1B4EBC for <abfab@ietfa.amsl.com>; Mon, 5 Oct 2015 02:30:40 -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 rEDMsrdIu1nH for <abfab@ietfa.amsl.com>; Mon, 5 Oct 2015 02:30:38 -0700 (PDT)
Received: from xenon21.um.es (xenon21.um.es [155.54.212.161]) by ietfa.amsl.com (Postfix) with ESMTP id 553D81B4EC0 for <abfab@ietf.org>; Mon, 5 Oct 2015 02:30:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by xenon21.um.es (Postfix) with ESMTP id 6596F406B4 for <abfab@ietf.org>; Mon, 5 Oct 2015 11:30:37 +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 MHgBs43VOOAC for <abfab@ietf.org>; Mon, 5 Oct 2015 11:30:37 +0200 (CEST)
Received: from [155.54.204.2] (alex.inf.um.es [155.54.204.2]) (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 4E32B406B1 for <abfab@ietf.org>; Mon, 5 Oct 2015 11:30:35 +0200 (CEST)
To: abfab@ietf.org
References: <20151005072718.21102.94680.idtracker@ietfa.amsl.com> <561227AA.8090602@um.es> <56123E92.5020208@ed.ac.uk>
From: =?UTF-8?Q?Alejandro_P=c3=a9rez_M=c3=a9ndez?= <alex@um.es>
Message-ID: <5612433A.6050603@um.es>
Date: Mon, 5 Oct 2015 11:30:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56123E92.5020208@ed.ac.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/abfab/3VwY7JXucfVQnIVZ15z8tab4TUg>
Subject: Re: [abfab] Fwd: New Version Notification for draft-perez-abfab-gss-remote-attr-00.txt
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: Mon, 05 Oct 2015 09:30:41 -0000


El 05/10/15 a las 11:10, Alex Stuart escribió:
> Hi Alejandro
>
> I think some names of the SAML attributes have got swapped. In section
> 5.1, the last bullet point should be:
>
> * urn:ietf:params:gss:federated-saml-attribute
> urn:oasis:names:tc:SAML:2.0:attrname-format:uri
> urn:oid:1.3.6.1.4.1.5923.1.1.1.7 (SAML eduPersonEntitlement attribute)
>
> And in 5.6, the parenthetical SAML eduPersonAffiliation and SAML
> eduPersonEntitlement should be swapped.

Hi Alex,

yup, you are right. I will change it for the next version.

>
> However, I'm not sure that an application would first receive an
> entitlement, then ask for an affiliation. Because affiliation has a
> small controlled vocabulary and entitlement can be as fine-grained as
> you like, I think the logic would be reversed. I can envisage that an
> application receives affiliation, which it finds too coarse to allow
> authorization, and then looks for entitlement to make the decision.

It was just an example, so I didn't think so much how much sense it made 
:).
But since your example seems more logical, I will borrow it and use it 
for the next version. Thanks!

Regards,
Alejandro
>
> Regards,
> Alex
>
> On 05/10/2015 08:32, Alejandro Pérez Méndez wrote:
>> Dear all,
>>
>> we have submitted a new draft called " Retrieving remote attributes
>> using GSS-API naming extensions" that aims to describe how current
>> GSS-API extensions can be used to allow mechanisms to retrieve remote
>> attributes without requiring of any change neither on the existing calls
>> nor on the way applications use the API.
>>
>> Any comment or feedback is welcome.
>>
>> Regards,
>> Alejandro
>>
>>
>> -------- Mensaje reenviado --------
>> Asunto: 	New Version Notification for
>> draft-perez-abfab-gss-remote-attr-00.txt
>> Fecha: 	Mon, 05 Oct 2015 00:27:18 -0700
>> De: 	internet-drafts@ietf.org
>> Para: 	Alejandro Perez-Mendez <alex@um.es>es>, Alejandro Perez-Mendez
>> <alex@um.es>es>, Rafa Marin-Lopez <rafa@um.es>es>, Rafael Lopez <rafa@um.es>es>,
>> Gabriel Lopez-Millan <gabilm@um.es>es>, Gabriel Lopez-Millan <gabilm@um.es>
>>
>>
>>
>> A new version of I-D, draft-perez-abfab-gss-remote-attr-00.txt
>> has been successfully submitted by Alejandro Perez-Mendez and posted to the
>> IETF repository.
>>
>> Name:		draft-perez-abfab-gss-remote-attr
>> Revision:	00
>> Title:		Retrieving remote attributes using GSS-API naming extensions
>> Document date:	2015-10-05
>> Group:		Individual Submission
>> Pages:		9
>> URL:            https://www.ietf.org/internet-drafts/draft-perez-abfab-gss-remote-attr-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-perez-abfab-gss-remote-attr/
>> Htmlized:       https://tools.ietf.org/html/draft-perez-abfab-gss-remote-attr-00
>>
>>
>> Abstract:
>>     The GSS-API Naming Extensions define new APIs that extend the GSS-API
>>     naming model to support name attribute transfer between GSS-API
>>     peers.  Historically, this set of functions has been used to obtain
>>     the authorization information contained in some sort of authorization
>>     token provided to the GSS acceptor during the context establishment
>>     process, such as a Kerberos ticket, a SAML assertion, or an X.509
>>     attribute certificate.  However, some scenarios require to allow the
>>     GSS acceptor to request additional attributes after context
>>     establishment.  If these attributes are not locally stored by the GSS
>>     mechanism they have to be retrieved from an external source (e.g.
>>     SQL database, LDAP directory, external IdP, etc.).  This document
>>     describes how current GSS-API extensions are able to encompass such
>>     functionality without requiring of any change, neither on the
>>     existing calls nor on the way applications use the API.
>>
>>                                                                                    
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>
>>
>>
>>
>> _______________________________________________
>> abfab mailing list
>> abfab@ietf.org
>> https://www.ietf.org/mailman/listinfo/abfab
>>