[OAUTH-WG] Fwd: New Version Notification for draft-erdtman-oauth-rpcc-00.txt

Samuel Erdtman <samuel@erdtman.se> Tue, 21 November 2017 10:19 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 48E0B129439 for <oauth@ietfa.amsl.com>; Tue, 21 Nov 2017 02:19:13 -0800 (PST)
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 DVz8T01HPt8B for <oauth@ietfa.amsl.com>; Tue, 21 Nov 2017 02:19:10 -0800 (PST)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 B8F8E129461 for <oauth@ietf.org>; Tue, 21 Nov 2017 02:19:10 -0800 (PST)
Received: by mail-qk0-x232.google.com with SMTP id f63so11268900qke.8 for <oauth@ietf.org>; Tue, 21 Nov 2017 02:19:10 -0800 (PST)
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=OXfCmEvAzZDwbdAOt+QwSif1avj/YPBv3x8Zdig/fs8=; b=t3v0MYcyQlOtG9IUzcm04enb0KdtcUWbk86ZFQltp8i4V9WcrnGuLpn9103C2V+U9Y SbnfNCtKr35976wRbZs5BKboyKSga6SN71F1GoqfcZwJEKhAqlOHase0KWKkEWBVsoqD samx32oq1Df7p3VaRczdlmdQaAR5J34URYZ2DrafqRET2k+f21gMpECNaLGPHjgZzif2 ntr/n1nGinK7UvfAe9ZY8QxMVrtK6wl7FXBHQMXdaJaKmIcgFgntUHtBP+HuWyoivBsX Z87fVtPphTgkf5Mdff2Sh9QbJhXHbzS5E1ebX52bV8vjlcNbC51N38KFOGYmrKmfLtkC b5pg==
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=OXfCmEvAzZDwbdAOt+QwSif1avj/YPBv3x8Zdig/fs8=; b=XRAweanFsplxXnPalbYFfE4Bviylqf8k4qjEoHgb6x+gk/OJZVt4GKRF85WNRCZ1Ib 5oSYHAX28latgQbLk5RXCqkm16Ai76pH3lca4Z+VrWh28823vxo9iPk8MVdLk8x8FL+v iQUAILeF4zWpax7dpbDIHAYEuJrXAX7GwR2+wKuOFB4DmMgXEdEHZ06WQTSM5XcGoG4F 0fnLal3D7QbQPYazctkpX+FpytxkMCq+y/u1sdLFqksUIxuzFPJPqW2xxcps9vRtFEIV H8FgKHSRJEk9lODIHvycDzL1iFGR/nrupLowAlwsclXM2o1Y6qBZkGecKExo9mEQmmMo VEEw==
X-Gm-Message-State: AJaThX5L2Uvlu3nJMtzhpvPRHLSP3ZOJvhgYxJ6xlaIfoK43BheeOFci 0zVB0rdR6l8bOlISMsUfvwwLp8oIBz3HUSJUPAg4n+mnxq8=
X-Google-Smtp-Source: AGs4zMZhPf2eUdRQ7xR7fnkrf+QPXlOC5/EvXMUSi1ta6LD5mD/VuoHS2Lo9+jvXsRnegAoyx65XhjUFVM8fF0/TNvY=
X-Received: by 10.55.71.5 with SMTP id u5mr9322992qka.166.1511259549579; Tue, 21 Nov 2017 02:19:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.3.84 with HTTP; Tue, 21 Nov 2017 02:19:09 -0800 (PST)
In-Reply-To: <CAOB_DJkdCCC3L3Dpz=cheN5KW1Kjx8ggqzS0R1zm3-npSQ5NPw@mail.gmail.com>
References: <151125895956.14726.11740003659885129774.idtracker@ietfa.amsl.com> <CAOB_DJkdCCC3L3Dpz=cheN5KW1Kjx8ggqzS0R1zm3-npSQ5NPw@mail.gmail.com>
From: Samuel Erdtman <samuel@erdtman.se>
Date: Tue, 21 Nov 2017 11:19:09 +0100
Message-ID: <CAF2hCbYxvyoRkxC5zgviz50oSQGRigPf0eLdawOeHBCzz87Twg@mail.gmail.com>
To: "<oauth@ietf.org>" <oauth@ietf.org>, ace <Ace@ietf.org>
Cc: Ludwig Seitz <ludwig.seitz@ri.se>, Marco Tiloca <marco.tiloca@ri.se>
Content-Type: multipart/alternative; boundary="001a114a8d4a9dcf0e055e7b881d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/6zV9gcl1ir9g1GIhwDF28SjV0n0>
Subject: [OAUTH-WG] Fwd: New Version Notification for draft-erdtman-oauth-rpcc-00.txt
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: Tue, 21 Nov 2017 10:19:13 -0000

Hi,

I have submitted draft-erdtman-oauth-rpcc under the OAuth WG as discussed
during IETF 100. (Moved from ACE WG since the new credentials does not have
any formal connection to the ACE documents, i.e. pure OAuth stuff)

This document defines how to user Raw-Public-Key and Pre-Shared-Key with
(D)TLS as client credentials.

We think it is essential to define this for IoT devices since the classic
client id and secret is not very suitable for devices with limited user
interfaces.

Comments, questions and reviews would be very appreciated.

Cheers
//Samuel

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Tue, 21 Nov 2017 at 11:09
Subject: New Version Notification for draft-erdtman-oauth-rpcc-00.txt
To: Marco Tiloca <marco.tiloca@ri.se>, Ludwig Seitz <ludwig.seitz@ri.se>,
Samuel Erdtman <erdtman@spotify.com>



A new version of I-D, draft-erdtman-oauth-rpcc-00.txt
has been successfully submitted by Samuel Erdtman and posted to the
IETF repository.

Name:           draft-erdtman-oauth-rpcc
Revision:       00
Title:          Raw-Public-Key and Pre-Shared-Key as OAuth client
credentials
Document date:  2017-11-20
Group:          Individual Submission
Pages:          6
URL:            https://www.ietf.org/internet-drafts/draft-erdtman-oauth-
rpcc-00.txt
Status:         https://datatracker.ietf.org/doc/draft-erdtman-oauth-rpcc/
Htmlized:       https://tools.ietf.org/html/draft-erdtman-oauth-rpcc-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-erdtman-oauth-
rpcc-00


Abstract:
   This document describes Transport Layer Security (TLS) authentication
   using Raw-Public-Key and Pre-Shared-Key as new mechanisms for OAuth
   client authentication.  Although defined for TLS the mechanisms are
   equally applicable for DTLS.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat