Re: [OAUTH-WG] Few questions about HOTK

Sergey Beryozkin <sberyozkin@gmail.com> Fri, 21 December 2012 16:00 UTC

Return-Path: <sberyozkin@gmail.com>
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 2ACCC21F8712 for <oauth@ietfa.amsl.com>; Fri, 21 Dec 2012 08:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5fBXaIP3VVI for <oauth@ietfa.amsl.com>; Fri, 21 Dec 2012 08:00:03 -0800 (PST)
Received: from mail-bk0-f49.google.com (mail-bk0-f49.google.com [209.85.214.49]) by ietfa.amsl.com (Postfix) with ESMTP id F169921F86C3 for <oauth@ietf.org>; Fri, 21 Dec 2012 08:00:02 -0800 (PST)
Received: by mail-bk0-f49.google.com with SMTP id jm19so2527765bkc.36 for <oauth@ietf.org>; Fri, 21 Dec 2012 08:00:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VENBG2N2YUZuaQX+jclSINFSFBOeeoypnFdU0+3/cBQ=; b=BBBWUGXM2V21qsLvkd3q5JzYMyrps/cQFI7ss2wHY/RcnML9b9segt4Q8R6zNt0sn6 RGDNSmtXfsJCocLAxOJNgOA25gpYp1+vu+Rft4KobeNT5RIYFsRrmzmVXu0CtYcxsawc iU6I6cTVba/0U2fw71Jfz7lWx45PmDd5DLxHKPKvO5xSA5IM0cqSIn8r2wKV0LK8l6Zk yXadVX0OG1aVydL91hRBLpS+yyG3Nqzz9wIfSeEMswGe9RAiA81RnblFRgD5TViFutQ4 c3FrHEQjj5pjAooI5GJiifitJiOLeoKUGlsbJ5ELHrArm+3xjhb9yyDbK/cj0jsZnN9l aamw==
X-Received: by 10.204.147.67 with SMTP id k3mr6544717bkv.117.1356105602043; Fri, 21 Dec 2012 08:00:02 -0800 (PST)
Received: from [10.36.224.146] ([217.173.99.61]) by mx.google.com with ESMTPS id l17sm10499462bkw.12.2012.12.21.08.00.00 (version=SSLv3 cipher=OTHER); Fri, 21 Dec 2012 08:00:01 -0800 (PST)
Message-ID: <50D4877F.5090301@gmail.com>
Date: Fri, 21 Dec 2012 15:59:59 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: William Mills <wmills_92105@yahoo.com>
References: <50D387DB.4080608@gmail.com> <1356067808.32663.YahooMailNeo@web31810.mail.mud.yahoo.com> <50D444DB.4000003@gmail.com> <1356105294.799.YahooMailNeo@web31805.mail.mud.yahoo.com>
In-Reply-To: <1356105294.799.YahooMailNeo@web31805.mail.mud.yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Few questions about HOTK
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Dec 2012 16:00:04 -0000

On 21/12/12 15:54, William Mills wrote:
> No, MAC as I'm using it is a MAC token per
> http://tools.ietf.org/html/draft-ietf-oauth-v2-http-mac-02

Sure, what do you mean though when saying
"HOTK payload can be carried in a MAC token." ?

I'm presuming you have in mind the parameters as defined in the draft, 
and specifically I thought it was the 'mac' attribute which is 
effectively a HOTK payload, possibly alongside few other Authorization 
MAC scheme attributes ?

Sergey

>
> ------------------------------------------------------------------------
> *From:* Sergey Beryozkin <sberyozkin@gmail.com>
> *To:* William Mills <wmills_92105@yahoo.com>
> *Cc:* "<oauth@ietf.org>" <oauth@ietf.org>
> *Sent:* Friday, December 21, 2012 3:15 AM
> *Subject:* Re: [OAUTH-WG] Few questions about HOTK
>
> On 21/12/12 05:30, William Mills wrote:
>  > MAC and HOTK describe different properties of a token, and could both be
>  > used in the same token. MAC specifies a basic format for a signed token
>  > payload and transaction. HOTK defines part of a token payload. HOTK
>  > payload can be carried in a MAC token.
>
> Speaking of MAC, are you referring to
> "mac" parameter within MAC Authorization payload representing a HOTK
> property ?
>
> Cheers, Sergey
>
>  >
>  > -bill
>  >
>  > ------------------------------------------------------------------------
>  > *From:* Sergey Beryozkin <sberyozkin@gmail.com
> <mailto:sberyozkin@gmail.com>>
>  > *To:* "<oauth@ietf.org <mailto:oauth@ietf.org>>" <oauth@ietf.org
> <mailto:oauth@ietf.org>>
>  > *Sent:* Thursday, December 20, 2012 1:49 PM
>  > *Subject:* [OAUTH-WG] Few questions about HOTK
>  >
>  > Hi Hannes, others,
>  >
>  > I'd like to understand what is the difference between HOTK Symmetric [1]
>  > and MAC [2].
>  >
>  > I'm reading about HOTK Symmetric and JWS profile and it seems like HOTK
>  > Symmetric text can support MAC.
>  >
>  > My main question at the moment: does HOTK (Symmetric) offer an
>  > alternative to MAC or is HOTK actually a higher-level token scheme which
>  > can support different types of tokens ?
>  >
>  > thanks, Sergey
>  >
>  > [1] http://tools.ietf.org/html/draft-tschofenig-oauth-hotk-01
>  > [2] http://tools.ietf.org/html/draft-ietf-oauth-v2-http-mac-02
>  > _______________________________________________
>  > OAuth mailing list
>  > OAuth@ietf.org <mailto:OAuth@ietf.org> <mailto:OAuth@ietf.org
> <mailto:OAuth@ietf.org>>
>  > https://www.ietf.org/mailman/listinfo/oauth
>  >
>  >
>
>