Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-signed-http-request-00.txt

Sergey Beryozkin <sberyozkin@gmail.com> Mon, 22 December 2014 12:36 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 6243F1A8AB1 for <oauth@ietfa.amsl.com>; Mon, 22 Dec 2014 04:36:10 -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 hznkJ56D6hhX for <oauth@ietfa.amsl.com>; Mon, 22 Dec 2014 04:36:08 -0800 (PST)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C6CD1A8A9D for <oauth@ietf.org>; Mon, 22 Dec 2014 04:36:08 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id bs8so7875582wib.16 for <oauth@ietf.org>; Mon, 22 Dec 2014 04:36:06 -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=Sy2+tGGBb1gYpGWNU5kUmAQP2XhQJpJFCgTg/bRqN2Q=; b=wNooOytaL7MyrEgjGt2NaTGBjoHereMKXn4oVJNJgrlOnhpk79XN44DRHj+z3NrR8P QAGVRzyTcRsFlvwOBHt4Pzy69y3L5S+5kbMO6CN+UB/sT9UuccOxmLpto98Q4/Ua95lR 4jShTsDh5+y3nXyQ4uEtVCjlV4V4Xm9rfleV3n2m98LGKCgcfVCIf5UIvs+JI/YBwi+z W9KHKP/Mwf1nr6PodXMmkyaHkg5O7YPoEts2n9vHya7cJJVIgIPNCem+jl9mo3K/cDoI QpShKxIqCifuyKimSTg4X3mglnQILa63OFTfO+zXlRb7IDaag8X01xqhgZPrwLM1hhEW sG/g==
X-Received: by 10.194.179.166 with SMTP id dh6mr41676858wjc.87.1419251766917; Mon, 22 Dec 2014 04:36:06 -0800 (PST)
Received: from [192.168.2.7] ([109.255.230.137]) by mx.google.com with ESMTPSA id wv8sm23538684wjc.44.2014.12.22.04.36.06 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Dec 2014 04:36:06 -0800 (PST)
Message-ID: <54981035.2060807@gmail.com>
Date: Mon, 22 Dec 2014 12:36:05 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Justin Richer <jricher@mit.edu>, oauth@ietf.org
References: <0j3djshkn5mba4hl4yvgn6r6.1419251602904@email.android.com>
In-Reply-To: <0j3djshkn5mba4hl4yvgn6r6.1419251602904@email.android.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/LYJMI5R5XgNEyNTpV7AK1oO5I5k
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-signed-http-request-00.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: Mon, 22 Dec 2014 12:36:10 -0000

Hi, yes, it is obvious for anyone who has read the text carefully :-),
sorry for the noise
Sergey
On 22/12/14 12:33, Justin Richer wrote:
> That's easy: any headers. That's why the signer specifies which ones.
> Would be good to have since guidance tough, and examples.
>
>
> -- Justin
>
> / Sent from my phone /
>
>
> -------- Original message --------
> From: Sergey Beryozkin <sberyozkin@gmail.com>
> Date:12/22/2014 7:08 AM (GMT-05:00)
> To: oauth@ietf.org
> Cc:
> Subject: Re: [OAUTH-WG] I-D Action:
> draft-ietf-oauth-signed-http-request-00.txt
>
> Hi Justin
>
> I see a fair bit of interest toward this work now being shown from my
> colleagues; it would help if the next draft could clarify which HTTP
> headers can be signed given it is difficult to get hold of some of HTTP
> headers typically created by a low level HTTP transport component.
>
> Thanks, Sergey
>
> On 21/07/14 14:58, 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           : A Method for Signing an HTTP Requests for
> OAuth
>  >          Authors         : Justin Richer
>  >                            John Bradley
>  >                            Hannes Tschofenig
>  > Filename        : draft-ietf-oauth-signed-http-request-00.txt
>  > Pages           : 11
>  > Date            : 2014-07-21
>  >
>  > Abstract:
>  >     This document a method for offering data origin authentication and
>  >     integrity protection of HTTP requests.  To convey the relevant data
>  >     items in the request a JSON-based encapsulation is used and the JSON
>  >     Web Signature (JWS) technique is re-used.  JWS offers integrity
>  >     protection using symmetric as well as asymmetric cryptography.
>  >
>  >
>  > The IETF datatracker status page for this draft is:
>  > https://datatracker.ietf.org/doc/draft-ietf-oauth-signed-http-request/
>  >
>  > There's also a htmlized version available at:
>  > http://tools.ietf.org/html/draft-ietf-oauth-signed-http-request-00
>  >
>  >
>  > 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 mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth