IETF Logo Mail Archive

[OAUTH-WG] "access grant" terminology

Brian Eaton <beaton@google.com> Sun, 11 July 2010 02:46 UTC

Return-Path: <beaton@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA3233A6915 for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 19:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.757
X-Spam-Level:
X-Spam-Status: No, score=-104.757 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, 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 dETfmHs22F+Z for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 19:46:39 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 348A83A6914 for <oauth@ietf.org>; Sat, 10 Jul 2010 19:46:39 -0700 (PDT)
Received: from kpbe14.cbf.corp.google.com (kpbe14.cbf.corp.google.com [172.25.105.78]) by smtp-out.google.com with ESMTP id o6B2kinj003890 for <oauth@ietf.org>; Sat, 10 Jul 2010 19:46:45 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1278816405; bh=bskzuun5QOi61/LI38ekDeF7Bbg=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=ECkyVqzvAtx7lYKw10OF85A8AVFp5XbVrs8ZazamXGWX57He7N6EP0h1gDL9H2F2p z8y9dWilXsrgOOsek3HmQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:date:message-id:subject:from:to:content-type:x-system-of-record; b=ZkG6w5k/gFrhyEZfdbAbaeV7ab0ubD3Z5SBtHjzcOqbzsa2mHNtsTop8TFYhSkkRM Pp9Ty8ytIb+ab49RHw4Ww==
Received: from pvc21 (pvc21.prod.google.com [10.241.209.149]) by kpbe14.cbf.corp.google.com with ESMTP id o6B2khX1029341 for <oauth@ietf.org>; Sat, 10 Jul 2010 19:46:44 -0700
Received: by pvc21 with SMTP id 21so1579068pvc.7 for <oauth@ietf.org>; Sat, 10 Jul 2010 19:46:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.225.8 with SMTP id x8mr14077170wfg.291.1278816403155; Sat, 10 Jul 2010 19:46:43 -0700 (PDT)
Received: by 10.142.193.19 with HTTP; Sat, 10 Jul 2010 19:46:43 -0700 (PDT)
Date: Sat, 10 Jul 2010 19:46:43 -0700
Message-ID: <AANLkTikq4C9FYySiDmJqEBJIiYoYGxC9ZbpaPqHKgDgY@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: oauth@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Subject: [OAUTH-WG] "access grant" terminology
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jul 2010 02:46:41 -0000

The term "access grant" in the -09 spec is a bit odd.  Normally
"access grant" or "permission grant" would refer to a specific policy
decision made by a resource owner.

But that's not how the -09 spec uses the term.  The -09 spec refers to
authorization codes and assertions as "access grants".  Again, that's
weird.  Normally an assertion would be referred to as a "credential",
not a grant.

I think the term "authorization credential" might be a better fit than
"access grant".

It certainly describes the purpose of the authorization code and the
assertion.  And the term "credential" is normally used to describe
things that need to be verified and protected.

Cheers,
Brian

v2.34.0 | Report a Bug | By Email | System Status