Re: [Ace] [OAUTH-WG] Resource, Audience, and req_aud

Hannes Tschofenig <Hannes.Tschofenig@arm.com> Thu, 07 February 2019 16:05 UTC

Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B598126D00; Thu, 7 Feb 2019 08:05:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com
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 nN7sDJPhljPH; Thu, 7 Feb 2019 08:05:23 -0800 (PST)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50041.outbound.protection.outlook.com [40.107.5.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2123B12008F; Thu, 7 Feb 2019 08:05:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0+37Ytd0Kdz6A1NaT323fj49zs3Hxf3hCsW/9N5c960=; b=Jsoi8TJQtfTo0ZMwx5r9tMuP+/mti1YK+KsXg4wlyFvKOvoiQbYhu++Dd6mLHNxVSeInSbnrUxHUwqhhfZZse2THKgb4KE9tCaEdoe93CFkJ4cHyQPvQjJc39OitCx02oszZXy9Qog8NGK4F9HShsgD1dFO0OSRDxZyR/rKs3Ck=
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com (10.173.75.16) by VI1PR0801MB1774.eurprd08.prod.outlook.com (10.168.67.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1601.17; Thu, 7 Feb 2019 16:05:20 +0000
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::3ce6:d8fa:3271:6019]) by VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::3ce6:d8fa:3271:6019%8]) with mapi id 15.20.1580.019; Thu, 7 Feb 2019 16:05:20 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Filip Skokan <panva.ip@gmail.com>
CC: "ace@ietf.org" <ace@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Resource, Audience, and req_aud
Thread-Index: AdS++E7Ly8Q8wLQXRVClxzlDwlE9TQAAsgOAAADi1lA=
Date: Thu, 7 Feb 2019 16:05:20 +0000
Message-ID: <VI1PR0801MB21122AAF0736E7BBD9A0524BFA680@VI1PR0801MB2112.eurprd08.prod.outlook.com>
References: <VI1PR0801MB21126944E558E53992EB7FD3FA680@VI1PR0801MB2112.eurprd08.prod.outlook.com> <CALAqi_9YUWBcUWtaG2g=mXQLJoq1X=dgm72exDU9akqxuhK_HQ@mail.gmail.com>
In-Reply-To: <CALAqi_9YUWBcUWtaG2g=mXQLJoq1X=dgm72exDU9akqxuhK_HQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hannes.Tschofenig@arm.com;
x-originating-ip: [80.92.122.55]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR0801MB1774; 6:aphtQthjYKzn56gTae2XFbP5lgtOSPLG5fLE+RAlSchs4ANcNS3bFJ4rwFYrLEdX3bZ9smhAw3Ul/PYVeiBkNXlJjMZXpua+lLhkhyL1kWFRGYbefLAXIMP9mW0forKH6cT0KdL7fH3W3/16nS2eeZ0Rl2gYcfJuS7EJBxVMTbk0uHuQzfxOTfKed7uALHaaIDw3NwBWSK1qKvtpafL1q3MtAU78v1vc9GjHZitziF21IERAczo+mipnTleomM3REPX4dCNYij+9oc4EhzFelpYUkP0Ab4sowcpuaGH+9MIKBNFKah7RKEVGbCWLcK9Cy95fepZgWxkBfeam44Kb9Kjl6i1MTT2KQYfaN1mQzUvObp9XkviWILoTH/GuWRqX4Xso+ny6oe9DBYVnMDIWH9+Fzihr4hWwuplCppLPbCPCuXHsCcAPow7pqbIU2bClfzuMyp9JAuO37S/WktXtVA==; 5:eF29SS/CM5XjdsWfNLo8XrTiTZR4TDorzGEiaaWidrOlas3PZbMneu2vwfL6EdKwA4rh7KufbyoVuHsaipBTpZQstf+C9rxqsi4pRNHqwjFFyhDqwxo2SaUepU1ZaMMsfsH+/EEDLJKaOqymzc/yJj/sQSBs580YGL8GWY9q4z1MRb6lNzY0WInq7QMs48zXjA5wgbbcNcAnUpsPeHoV6Q==; 7:S6hMySohFg+0vOPL++lWqiGT5leN33JxJ7klAhbIQysCwCymXAL5goUSrkERC7xX9jo5cd4oYuPVyUbCksLi8hovxpOaiD5+w27fVGCKJZA+roh3lOdFYQCTrOAuw81mCgAXoPd5rkxhNI16onB0Hg==
x-ms-office365-filtering-correlation-id: e868a82e-8461-4a68-9316-08d68d160f23
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(4618075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0801MB1774;
x-ms-traffictypediagnostic: VI1PR0801MB1774:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <VI1PR0801MB1774D5D5405F2265F560FEB4FA680@VI1PR0801MB1774.eurprd08.prod.outlook.com>
x-forefront-prvs: 0941B96580
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(346002)(136003)(376002)(39860400002)(189003)(199004)(53754006)(40434004)(186003)(229853002)(7736002)(5070765005)(14444005)(6116002)(53546011)(5024004)(102836004)(256004)(99286004)(81166006)(53936002)(54906003)(6506007)(26005)(316002)(3846002)(54896002)(76176011)(236005)(6306002)(606006)(25786009)(86362001)(8936002)(8676002)(74316002)(4326008)(66066001)(6436002)(81156014)(97736004)(55016002)(71190400001)(6246003)(7696005)(105586002)(106356001)(71200400001)(790700001)(9686003)(33656002)(486006)(68736007)(14454004)(966005)(2906002)(72206003)(478600001)(6916009)(446003)(11346002)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0801MB1774; H:VI1PR0801MB2112.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Kq3NSyZ+1K18Giaj6VIVJCwJzvAM+U7YcF2CaH12Foy4zDqF9pCZ71j4D309E8VQ3L3InqR7WmIqnCkf5yfHAIE51unXOBl2ESnpK6b3flGlEWXYZJiQD/LLAFPIuMHn90J0tazz0LjgkItrFhNF9jqh2dvm9EuHsQgYJ7MZZ0HId7l7FEnIzE3+/fCoykeDJhd1E7iWBAcRSp54JD8iaij4+m5DyPHP6C+rYgA4e1qIhz3UxVvQhQtQaJgbY5HwjRa14irhSMx9Z67jnLfqnrnI0jsvQffaqSOl94kCqxDSjXhERV/l4H29AoP8/lS3p18DJjbR+xf30whu6EhN1st8wMqXdy5r0sM4Ftu4fmG2w+t3Qg9bTUtbHbozsk/JWtwrNd/EMXFIoCicq3F1fTjWInI0vD7by7ryWcPVKmM=
Content-Type: multipart/alternative; boundary="_000_VI1PR0801MB21122AAF0736E7BBD9A0524BFA680VI1PR0801MB2112_"
MIME-Version: 1.0
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e868a82e-8461-4a68-9316-08d68d160f23
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Feb 2019 16:05:20.1519 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0801MB1774
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/1db0JJbq8SyMwSQpilJuMy-1d5A>
Subject: Re: [Ace] [OAUTH-WG] Resource, Audience, and req_aud
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2019 16:05:27 -0000

Since the authors of the token exchange draft have asked IANA for an early registration of the parameters I get the impression that the question is more “ does the resource indicator spec need to define the resource parameter (or rather reference the resource and audience parameters from the token exchange spec)”?

From: Filip Skokan <panva.ip@gmail.com>
Sent: Donnerstag, 7. Februar 2019 16:38
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: ace@ietf.org; oauth@ietf.org
Subject: Re: [OAUTH-WG] Resource, Audience, and req_aud

To add to that,

3. If a device uses HTTP Token Exchange it can use both resource and audience parameters.

With the recent discussion and changes to the language in the resource indicators draft, does the token exchange spec need a unique audience parameter?

S pozdravem,
Filip Skokan


On Thu, 7 Feb 2019 at 16:25, Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote:
Hi all,

after re-reading token exchange, the resource indicator, and the ace-oauth-params drafts I am wondering whether it is really necessary to have different functionality in ACE vs. in OAuth for basic parameters.

Imagine I use an Authorization Server and I support devices that use CoAP and HTTP.


  1.  If a device uses CoAP then it has to use the req_aud parameter to indicate to the authorization server that it wants to talk to a specific resource server. It would either put a URI or a logical name there.
  2.  If a device uses HTTP then it has to use either the resource parameter to indicate to the authorization server that it wants to talk to a resource server, which is identified using a URI, or the audience parameter, if it uses a logical name.

Ciao
Hannes



IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.