IETF Logo Mail Archive

[Atoca] What information is used for authorization?

Hannes Tschofenig <hannes.tschofenig@gmx.net> Sat, 15 January 2011 19:28 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 799443A6E24 for <earlywarning@core3.amsl.com>; Sat, 15 Jan 2011 11:28:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.609
X-Spam-Level:
X-Spam-Status: No, score=-102.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3j5ZUWDtbX3 for <earlywarning@core3.amsl.com>; Sat, 15 Jan 2011 11:28:49 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 29DE23A6E23 for <earlywarning@ietf.org>; Sat, 15 Jan 2011 11:28:49 -0800 (PST)
Received: (qmail invoked by alias); 15 Jan 2011 19:31:17 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.7]) [88.115.222.204] by mail.gmx.net (mp060) with SMTP; 15 Jan 2011 20:31:17 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19zDJJBaMVzjCzxyeIWwFQ4ey5DVIZKhdtbdubsnk NZDTEUNz7NWWs2
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 15 Jan 2011 21:31:16 +0200
Message-Id: <9C2879D3-CDE1-48A6-B4F0-DC98B6EF1E0C@gmx.net>
To: earlywarning@ietf.org, Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
Subject: [Atoca] What information is used for authorization?
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jan 2011 19:28:50 -0000

Hi all, 

it was Igor again who raised a question regarding authorization at the IETF#79 ATOCA meeting. He was wondering whether we would only consider the identity of the originator for authorization or some other information as well.
 
Are we considering trait-based authorization, see http://www.rfc-editor.org/rfc/rfc4484.txt,  to be utilized in this context? 

So, what model do we envision? 
What other information is useful in the context of an authorization decision? 

Ciao
Hannes

v2.23.0 | Report a Bug | By Email