IETF Logo Mail Archive

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

John Bradley <ve7jtb@ve7jtb.com> Mon, 08 February 2016 15:04 UTC

Return-Path: <ve7jtb@ve7jtb.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 732881B2CB0 for <oauth@ietfa.amsl.com>; Mon, 8 Feb 2016 07:04:17 -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 fTgq2B_F7Rh7 for <oauth@ietfa.amsl.com>; Mon, 8 Feb 2016 07:04:15 -0800 (PST)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (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 54D1E1B2CAB for <oauth@ietf.org>; Mon, 8 Feb 2016 07:04:15 -0800 (PST)
Received: by mail-qg0-x234.google.com with SMTP id b35so118230515qge.0 for <oauth@ietf.org>; Mon, 08 Feb 2016 07:04:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rpMXDMmAOLKUAvIbqtc3MnPu23bg+sDGGxeIPQBgaT0=; b=2QvQllZ6u+lqg6+PrEL4/HL/3oz1iV1o7EhMahF7JH4YEN1GGcODEn2I/muAsqVn7H ihzy8v+UxhRVLxSMSKbkdzOKGAESho2dwooWKV0Sg//6WHa9TJt0m9Wi7K0xp3JE5wp8 4D3nQW1+EUlfwuhriifIOD9NEnROCyAY3+H5bRyd9ZqVXuWC6hQs104xfc+JAjdWUv5h fKFdEKrJl/mmJaOrBayJhflPFRrCctiWIcgtpm3XcOyNIEYI3shl9CstmC/FvFAlkf3B +1LpJkStZB7c1dvbQLIswhWOFdm0XAGNKroFdM8u4z1bf0bYDK3u3s9p7ozot+BLn+2g kidA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=rpMXDMmAOLKUAvIbqtc3MnPu23bg+sDGGxeIPQBgaT0=; b=gtkeNXdoQZqJwMGAJ70oeRhztHJDMT+MLqPxcb9mvM2pOCtR7HG6KCaEgkWhSohSH7 KPqvzHq0KnlpKAWptdzsv+8/b8DH4VdTFvHZk+1dvCKQF2ym4mcW8wPIa1m/eYIQmhM9 BT/EMIqab+TGt+tPhXn//wQ1I0brozhgHmYkuQvpzTKwKV7n3ZG8XVTKofhnZAayVqQ2 WJlZ/26BOOJiE0RTHvUUpA6YLLZolcMruQsVJI/Bn5kuHqLzRHcsqPX8TnbMVkJNf0Hb p2zO3V1EyS863l9S6cMx3q9yGL496Wp9oKBENjLsAucNB66JSoLlLtR5Le4Lpl4D+o1t whbg==
X-Gm-Message-State: AG10YOQGN+gKS0oW66MhZGtlcVqDQFG394+yo0DtAjhWdq4ErRbZRFIpPoGJXpKhL4N9dQ==
X-Received: by 10.140.162.2 with SMTP id i2mr37167437qhi.44.1454943854366; Mon, 08 Feb 2016 07:04:14 -0800 (PST)
Received: from [192.168.1.68] ([191.115.87.228]) by smtp.gmail.com with ESMTPSA id x136sm14069824qka.0.2016.02.08.07.04.11 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 08 Feb 2016 07:04:13 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <56B45DA7.6040408@sics.se>
Date: Mon, 08 Feb 2016 12:04:05 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <82E817C1-B95F-4E08-A7BC-E11164FFDD61@ve7jtb.com>
References: <56B31FEB.4010204@sics.se> <16330.1454596303@obiwan.sandelman.ca> <56B36703.8060305@sics.se> <36D7AE64-51CB-4437-AC28-9F912CD6B0D9@ve7jtb.com> <56B45DA7.6040408@sics.se>
To: Ludwig Seitz <ludwig@sics.se>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/g6INUGmyoS6tWms9M1Osps7KNGY>
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: Mon, 08 Feb 2016 15:04:17 -0000

The RS is going to have to advertise what presentment mechanisms it supports.

We don’t have that yet.   I suspect that it might be part of OAuth Discovery.  Currently that mostly cover AS discovery, but for the RS I could see doing a head on the resource and getting back a link to a JSON document that would contain meta-data about the RS.

The standard OAuth answer to this question is the client would get it from the service documentation, but that is not really scalable.


> On Feb 5, 2016, at 5:30 AM, Ludwig Seitz <ludwig@sics.se> wrote:
> 
> 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