Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-01.txt
Sergey Beryozkin <sberyozkin@gmail.com> Thu, 13 November 2014 09:45 UTC
Return-Path: <sberyozkin@gmail.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 4954E1A6FC8 for <oauth@ietfa.amsl.com>; Thu, 13 Nov 2014 01:45:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 vfgsCIWFNZmw for <oauth@ietfa.amsl.com>; Thu, 13 Nov 2014 01:45:09 -0800 (PST)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 539021A6FC4 for <oauth@ietf.org>; Thu, 13 Nov 2014 01:45:09 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id l15so3697860wiw.16 for <oauth@ietf.org>; Thu, 13 Nov 2014 01:45:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jHmVNQHamDYy8Zd+6V76qqzgGZlUtYTz2nC29H36mOE=; b=zlLrZXETp7+wXB3xoizzIWwSTwoSDDvzpjdFjPmgWw9baIwKuxB9XLgJjnSxShxqjA 8DvONxlPLDBBMwWvrBE9CFyF2Yvw6FnUL87tXFzMU4JWrOO8gET8j6NBFn0P5X3ZNXxS dGRxIVx/noOnU0ighmefFIyr6IgYGRTky+z23DiIzxLHXirP8hlqba5PMgjhpGBZGa3d jNjk2bZWSivwmk6aQ/LiwXKr3i8qPGjjpd+kj5pYwk1VSfPXHLIO8FhNUSBwr9jeVmUI 1WsUJFimnJc+SS1mbhRodAWHVeK5acW9HWRDsr+rvF4YfXl0TDYVNvbr8+j19l5J6ynk CaPA==
X-Received: by 10.180.99.163 with SMTP id er3mr2159646wib.18.1415871907590; Thu, 13 Nov 2014 01:45:07 -0800 (PST)
Received: from [10.36.226.2] ([80.169.137.63]) by mx.google.com with ESMTPSA id bc1sm24980371wib.16.2014.11.13.01.45.06 for <oauth@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Nov 2014 01:45:06 -0800 (PST)
Message-ID: <54647D9E.2030403@gmail.com>
Date: Thu, 13 Nov 2014 09:45:02 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: oauth@ietf.org
References: <20141113040729.675.60416.idtracker@ietfa.amsl.com>
In-Reply-To: <20141113040729.675.60416.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/CuR5krFtYxToY78qweFBVk10c1U
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-01.txt
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: <http://www.ietf.org/mail-archive/web/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: Thu, 13 Nov 2014 09:45:11 -0000
Hi Very nice. Can it become drat-oauth-jwsreqres ? I know spop-04 has been released, we'll update our implementation as needed, but if an optional signing of a request is of interest, why can't be signing of the response be of interest too ? Thanks, Sergey On 13/11/14 04:07, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Web Authorization Protocol Working Group of the IETF. > > Title : Request by JWS ver.1.0 for OAuth 2.0 > Authors : Nat Sakimura > John Bradley > Filename : draft-ietf-oauth-jwsreq-01.txt > Pages : 9 > Date : 2014-11-12 > > Abstract: > The authorization request in OAuth 2.0 utilizes query parameter > serialization. This specification defines the authorization request > using JWT serialization. The request is sent through "request" > parameter or by reference through "request_uri" parameter that points > to the JWT, allowing the request to be optionally signed and > encrypted. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-oauth-jwsreq-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwsreq-01 > > > 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. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-01… internet-drafts
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsre… Nat Sakimura
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsre… Sergey Beryozkin
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsre… Sergey Beryozkin
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsre… John Bradley
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsre… Sergey Beryozkin
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsre… John Bradley