Re: [OAUTH-WG] [Ace] New OAuth client credentials RPK and PSK

Samuel Erdtman <samuel@erdtman.se> Mon, 15 May 2017 08:52 UTC

Return-Path: <samuel@erdtman.se>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5139129AFA for <oauth@ietfa.amsl.com>; Mon, 15 May 2017 01:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=erdtman-se.20150623.gappssmtp.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 2O03gyO9cPL4 for <oauth@ietfa.amsl.com>; Mon, 15 May 2017 01:52:45 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 A876E129C49 for <oauth@ietf.org>; Mon, 15 May 2017 01:49:03 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id w10so122519741oif.0 for <oauth@ietf.org>; Mon, 15 May 2017 01:49:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erdtman-se.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Pfs0LLLfbhQWwh8WIOXvB7xvm2mphNTE8Wk+6eB8QPI=; b=xgT2wpclIo2xykcLwAcSIxfkMQ3/OLfV/Ft/J6lbyO3l/+KDoZGl3uzCAyF6apZ+CW 61oZJXoFd6oToGqIkc9GldMtTgJFUggUkeQ5qqQG56AycukNlIZL6CVgn191iWmO1w7a DQTj9BjrHqixZOYMAgqHepQkZB4QfUEV0F8W2o5sq9zUNaalq/k0OqojXCVED9At5SnA RqYvE1S3juxhda/bHvwJHS/PExTldhpXp2ESp2K82tjYkeJQ1ZIpgEs9BtIQ9gF3kJhf UiHtjd7dZF0pMWdtZPkDsoEmQP4Uj4c3PN9IDPBfuRVisaU3t+hrzRcX/CSdtv6Zeiz6 VHGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Pfs0LLLfbhQWwh8WIOXvB7xvm2mphNTE8Wk+6eB8QPI=; b=BSH6xGdb7Zgc/ncxd6aiTiisdALvZa7Ok+sWpGHQH3QirYa4s/m7O8hh2lkBcoRDHf g9Nrs6y3okW++WnEmqmx0hIdA4kk0vLRO3qEh14EVXkK7SDohkonTihAYCM3BbAWIsLb WMAwJ++rzOSzz23Bds0NJtIuXfsTDzg4dtx6gaD8phxGuAm0/3y+Z8yn7uiW3TCuwH9I SYPRtymfecDU3lOsEO0sEZVNtFyLn2bKPRZRI0pw6HlLguuS1m4dc8nsvyYe0lBp+r+D OcLhhlNQVYQ5Kjjjm5q94ZHQ9ub/5CHcijzrHr9P5b5E/vMtFbQd6t/i7Ha5pMLNll0E ezaQ==
X-Gm-Message-State: AODbwcATlkHwLG4aHVXL+Jy94mdflq4Fbs/OYUrGJoFcSMT4VnzGesWG 7J1DhP5OGGXk/qlc6g7amECS8np9EA==
X-Received: by 10.157.82.95 with SMTP id q31mr2600441otg.165.1494838142882; Mon, 15 May 2017 01:49:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.255.137 with HTTP; Mon, 15 May 2017 01:49:02 -0700 (PDT)
In-Reply-To: <000501d2ccef$398d0940$aca71bc0$@augustcellars.com>
References: <CAF2hCbZpWTCMg617dK7D+F+0w=hxrz4VNdsFZHPGM1rZy+K3TA@mail.gmail.com> <000501d2ccef$398d0940$aca71bc0$@augustcellars.com>
From: Samuel Erdtman <samuel@erdtman.se>
Date: Mon, 15 May 2017 10:49:02 +0200
Message-ID: <CAF2hCbY0p=kN3FHWk8+GaQa4drPa8batV9cqLqmehEbBwTnSqw@mail.gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>, ace <Ace@ietf.org>, Ludwig Seitz <ludwig.seitz@ri.se>
Content-Type: multipart/alternative; boundary="f403043c496480eb1f054f8c2086"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/ucGq5ZBVN6H0VQiQvdJKSuhjqfg>
Subject: Re: [OAUTH-WG] [Ace] New OAuth client credentials RPK and PSK
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 15 May 2017 08:52:48 -0000

In short this draft focuses on the C to AS connection and
draft-gerdes-ace-dtls-authorize focuses on the C to RS connection.

This draft details on how to use RPK or PSK as client credentials to setup
the (D)TLS between C and AS while draft-gerdes-ace-dtls-authorize provides
details for how to use the RPK or PSK bound to an access token to setup the
connection between C and RS.

//Samuel


On Sun, May 14, 2017 at 10:18 PM, Jim Schaad <ietf@augustcellars.com>; wrote:

> How is this draft supposed to interact with draft-gerdes-ace-dtls-
> authorize?
>
>
>
> Jim
>
>
>
>
>
> *From:* Ace [mailto:ace-bounces@ietf.org] *On Behalf Of *Samuel Erdtman
> *Sent:* Friday, May 12, 2017 1:03 AM
> *To:* <oauth@ietf.org>; <oauth@ietf.org>;; ace <Ace@ietf.org>;
> *Cc:* Ludwig Seitz <ludwig.seitz@ri.se>;
> *Subject:* [Ace] New OAuth client credentials RPK and PSK
>
>
>
> Hi ACE and OAuth WGs,
>
> I and Ludwig submitted a new draft yesterday defining how to use Raw
> Public Key and Pre Shared Key with (D)TLS as OAuth client credentials,
> https://datatracker.ietf.org/doc/draft-erdtman-ace-rpcc/.
>
>
>
> We think this is valuable to the ACE work since the ACE framework is based
> on OAuth, but client credentials as defined in the OAuth framework are not
> the best match for embedded devices.
>
> We think Raw Public Keys and Pre Shared Keys are more suitable credentials
> for embedded devices for the following reasons:
>
> * Better security by binding to transport layer.
>
> * If PSK DTLS is to be used a key need to be distributed any way, why not
> make use of it as credential.
>
> * Client id and client secret accommodates for manual input by a humans.
> This does not scale well and requires some for of input device.
>
> * Some/many devices will have crypto-hardware that can protect key
> material, to not use that possibility would be a waste.
>
> * There are probably more reasons these was just the once on top of my
> head.
>
>
>
> This is not the first resent initiative to create new client credential
> types, the OAuth WG adopted a similar draft for certificate based client
> credentials (https://tools.ietf.org/html/draft-ietf-oauth-mtls-00.html).
> That work is also valuable to ACE but not all devices will be able to work
> with certificates or even asymmetric cryptos .
>
> Please review and comment.
>
> Cheers
>
> //Samuel
>
>
>