[OAUTH-WG] Status of draft-tschofenig-oauth-audience

Sergey Beryozkin <sberyozkin@gmail.com> Wed, 20 January 2016 10:26 UTC

Return-Path: <sberyozkin@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C7931B399F for <oauth@ietfa.amsl.com>; Wed, 20 Jan 2016 02:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 r5i_UV2v86WZ for <oauth@ietfa.amsl.com>; Wed, 20 Jan 2016 02:25:58 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A0A61A700B for <oauth@ietf.org>; Wed, 20 Jan 2016 02:25:58 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id b14so21434163wmb.1 for <oauth@ietf.org>; Wed, 20 Jan 2016 02:25:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=mR+ivPhA8kkW+FrvTz7fimzNY4ljHDKQYxqOKqxd42c=; b=XL67XigN0E+wTfnq2jGuZmcdJJVF81AyKvVijV/zH+libmn5XNxzBEc0o4t9h0msqO Rg+Q3d6ycMrFZsymYkdrLbQxkaYo4Jk7evhEhHgvN5VdJmM7fqOgljX6MxpBH/YpLX9m U1jRd0NsZ5uFeT5dk99gKECYmIetAyojk/Q1iYS8XAWHVB5X5nWpOgngEFkfB0jN3p1M Phf0tIY4FXfD2PfaYSlGg2yQ9ekGCkeOh/G2uup0BJlIM7ySjiWNa/8WfB4yEF5Aqdrx RFvBSYKS9O2+D7E4FGnvf9DqKlCjofDCBTSVSdfN7VYGhNgXkqtUe7+7bE+DN3duTw1n snFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=mR+ivPhA8kkW+FrvTz7fimzNY4ljHDKQYxqOKqxd42c=; b=e6HLkv5xUfyPUtOPWtynHfbGxTJVKGlzAHN/oVDVT/ZKilHYNwfEjcBPKFn2VxR/9g 65qcdgXNqL47d788PQLZIfazdOJf9B4oNPhBMChzjQv1RUQ5MsNnPPB07bpXVcAre423 4H+CUXTrOxSscWXAjVaKrhCqYie16kUJjIV38tuBlNmfcT/DhwDhXMdehDqLU1WC6sec gsbNbd8Zem7FWT/2a1BYCi99+Lu3ZL2LIuTx2LEbWxeL3jrhMyugiAOp4NPzcddjhR/C +n74qEyv1sxPVIgcTPLeE0lFO2V7NMs0yc2lXvOZbirKADDsCaRJ4EVCK1eY4dMQB0W7 Lb6Q==
X-Gm-Message-State: AG10YORFqdOnXp0Z3Sot6Lkn7HWxWvnpsQVB22MiudvjUNrmcPKb+KS1e7HVN4aSTUitnA==
X-Received: by 10.28.232.208 with SMTP id f77mr3264018wmi.34.1453285557048; Wed, 20 Jan 2016 02:25:57 -0800 (PST)
Received: from [10.36.226.98] ([80.169.137.63]) by smtp.googlemail.com with ESMTPSA id x189sm1125894wmg.1.2016.01.20.02.25.55 for <oauth@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Jan 2016 02:25:55 -0800 (PST)
References: <CA+k3eCSpWFwyvk=XHP4b_zxzu-zrMYsS-axF6csO90-ahmkueQ@mail.gmail.com> <BY2PR03MB4423033D5604E9E36B20C23F5CA0@BY2PR03MB442.namprd03.prod.outlook.com> <5CA9073D-BBF7-48BD-BEC5-1F626E8C3818@mit.edu> <8EB68572-DA59-482D-A660-FA6D9848AAD2@oracle.com> <ade5692aa1afa2d9d79b8ac7a55bf150@lodderstedt.net> <5698CB3D.1030306@gmail.com> <69B0E23E-818A-4FE4-81A0-A8106EB6C312@ve7jtb.com> <5698F885.3030009@gmail.com> <569A69A5.7020006@connect2id.com> <A1C1786C-BE13-4D0F-9541-BEAE4DB8F284@mit.edu> <569ABB30.9060703@gmail.com> <569D0AE6.3060708@mit.edu> <569D0E86.60908@gmail.com> <569D1297.2000805@mit.edu> <569D1631.4030705@gmail.com> <569E1804.8010803@gmail.com>
To: oauth@ietf.org
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <569F60B3.3030501@gmail.com>
Date: Wed, 20 Jan 2016 10:25:55 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <569E1804.8010803@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/L60Xpp2z2j49bUtmwE2a10jarjU>
Subject: [OAUTH-WG] Status of draft-tschofenig-oauth-audience
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Wed, 20 Jan 2016 10:26:00 -0000

Hi

Given that the draft-tschofenig-oauth-audience [1] has expired, I'm 
wondering if it is still relevant.

I know the token introspection response can provide the audience 
value(s), but the question is really how a client is associated with a a 
given audience in the first place. As such [1] may still make sense, for 
example, I can think of two options:
1. the client audiences are set out of band during the client 
registration time and all the tokens issued to that client will be 
restricted accordingly
2. the client is requesting a specific audience during the grant to 
token exchange as per [1]

I guess 1. is how it is done in practice or is 2. is also a valid option ?


Thanks, Sergey


[1] https://tools.ietf.org/html/draft-tschofenig-oauth-audience-00