IETF Logo Mail Archive

Re: [OAUTH-WG] [Ace] Questions about OAuth and DTLS

Ludwig Seitz <ludwig@sics.se> Fri, 05 February 2016 08:30 UTC

Return-Path: <ludwig@sics.se>
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 529A61A8A6C for <oauth@ietfa.amsl.com>; Fri, 5 Feb 2016 00:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 oKv6VRYAaSDw for <oauth@ietfa.amsl.com>; Fri, 5 Feb 2016 00:30:45 -0800 (PST)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 CE8391A8A1E for <oauth@ietf.org>; Fri, 5 Feb 2016 00:30:44 -0800 (PST)
Received: by mail-lf0-x22e.google.com with SMTP id j78so52478432lfb.1 for <oauth@ietf.org>; Fri, 05 Feb 2016 00:30:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sics-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=L8ITAPUEg1RywruAPjoo8eet0Qy+oNFMUI34biTDbNE=; b=GvhGGmA2kK0HYLdsczdNwhRHdKlFyOOMuqo0SekGVfLYsSZrLhJhR05IwSWC2rqDZw tcT6Oy6I6JBzsJ3yi1yhWZyCTgCoFPLk1Mlo0g5gLNcOunpxpdjghA65AlM36sAxR3lb da3QEf8mKiwKObDl2FS3GkGpfzNeZZd9E+Yh9M+3FEtp+xGzJ//PF6QYjd7RXHlfxeDG IYiXZwv4jb53x4F0ukv6kGWIy1tBE5E8NWu/xyGhDNcPseUlTb3jghCzbS4WyDPeeTPH xVzqWyiSrcKXk2eFr9qMj9zG3oBarwydxt2q4SAsVa1qeGnTlWFFZDepRDin+Gggn3Xd uUpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type; bh=L8ITAPUEg1RywruAPjoo8eet0Qy+oNFMUI34biTDbNE=; b=ie2ByNm8+IdEG5CYuYM449gb2Dd46FO6Xu9qbUC/KXLSnqUqaKtR6BdIi5+jUmIgDc lM4yNAA/TUjJucr1seKPCVuB/ou59wn/mgpQzkh61nMc9V8Rh3jSkenGsEOtZRmW960J l8rgR0ztbScAqlAQN8Ze6s0RORTvzKKumlyZ6q6cCfFs8TQvWV5uQgjq+vxZeWGVFG9m EeGb0zJ/gRfhKRTJfuLfyzGzQkp92BplAJLQEMnRmXIc2w798IlGTXRkOe/v7GBmLIAn ijVqqPTjkvXotLissm+Fy635i3RLKCq2ItV/OpMfq5VqxyMQxBZ6yx91ttm52ncChaNL lCqA==
X-Gm-Message-State: AG10YOTg49M2Ramt+rguzgwopC1Hni3POOtABTbqfpT+HcwD+1rceBe0vRyGrIGZweh08iyR
X-Received: by 10.25.18.25 with SMTP id h25mr4504220lfi.165.1454661042921; Fri, 05 Feb 2016 00:30:42 -0800 (PST)
Received: from Hyperion.suse ([85.235.10.186]) by smtp.gmail.com with ESMTPSA id 87sm2155732lft.20.2016.02.05.00.30.41 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 00:30:42 -0800 (PST)
To: John Bradley <ve7jtb@ve7jtb.com>
References: <56B31FEB.4010204@sics.se> <16330.1454596303@obiwan.sandelman.ca> <56B36703.8060305@sics.se> <36D7AE64-51CB-4437-AC28-9F912CD6B0D9@ve7jtb.com>
From: Ludwig Seitz <ludwig@sics.se>
Message-ID: <56B45DA7.6040408@sics.se>
Date: Fri, 05 Feb 2016 09:30:31 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <36D7AE64-51CB-4437-AC28-9F912CD6B0D9@ve7jtb.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms020008060204040207000408"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/XOsLmBEwginNI6BQFDXcvbZHrlc>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, oauth@ietf.org, ace@ietf.org
Subject: Re: [OAUTH-WG] [Ace] Questions about OAuth and DTLS
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: Fri, 05 Feb 2016 08:30:47 -0000

On 02/04/2016 05:14 PM, John Bradley wrote:
> In https://tools.ietf.org/html/draft-ietf-oauth-pop-key-distribution
>
> The proof key is included in the access token or provided out of band.
>
> The proof mechanism to the RS is what would determine if the key type needs to match DTLS .
> If the proof is DTLS then they would need to match.
>

Thank you John, this leads me to another question (maybe I just missed 
it in the PoP drafts): Who decides what the proof mechanism should be? 
How is the proof mechanism signaled to the client (the client may 
support several proof mechanisms)?

/Ludwig


-- 
Ludwig Seitz, PhD
SICS Swedish ICT AB
Ideon Science Park
Building Beta 2
Scheelevägen 17
SE-223 70 Lund

Phone +46(0)70 349 9251
http://www.sics.se

v2.23.0 | Report a Bug | By Email