Re: [OAUTH-WG] Signature crypto

Brian Eaton <beaton@google.com> Fri, 04 December 2009 19:13 UTC

Return-Path: <beaton@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0C933A685B for <oauth@core3.amsl.com>; Fri, 4 Dec 2009 11:13:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KVVEoERkJQ1k for <oauth@core3.amsl.com>; Fri, 4 Dec 2009 11:12:58 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by core3.amsl.com (Postfix) with ESMTP id 1FA093A63EB for <oauth@ietf.org>; Fri, 4 Dec 2009 11:12:57 -0800 (PST)
Received: from spaceape13.eur.corp.google.com (spaceape13.eur.corp.google.com [172.28.16.147]) by smtp-out.google.com with ESMTP id nB4JClYi000507 for <oauth@ietf.org>; Fri, 4 Dec 2009 19:12:47 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1259953967; bh=S8UUbbuk1uqVi6unVoHp/oI+yuc=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=Yh/JhEk8yfUr6O/pQkVH2AoJILhJPIlFOblDXh4Zjhg0GLCgFsQ/3qtsmtNlBsdIS hWFHMdxF2nNcGSJJ/oHKA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=N4j54txcKXFFfgNNJV60JWms8JDHNUj03syU/b0Y1tQQLppRgpp+PcsLnENoYu/5P BqtgZsPlIbLTDxiRYsKpw==
Received: from pxi26 (pxi26.prod.google.com [10.243.27.26]) by spaceape13.eur.corp.google.com with ESMTP id nB4JCQUf007611 for <oauth@ietf.org>; Fri, 4 Dec 2009 11:12:44 -0800
Received: by pxi26 with SMTP id 26so611824pxi.21 for <oauth@ietf.org>; Fri, 04 Dec 2009 11:12:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.187.8 with SMTP id k8mr237447rvf.98.1259953963230; Fri, 04 Dec 2009 11:12:43 -0800 (PST)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723437852936BC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <90C41DD21FB7C64BB94121FBBC2E72343785183009@P3PW5EX1MB01.EX1.SECURESERVER.NET> <90C41DD21FB7C64BB94121FBBC2E72343785293671@P3PW5EX1MB01.EX1.SECURESERVER.NET> <f98165700912041016k10366b88tb001f7700405083f@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343785293683@P3PW5EX1MB01.EX1.SECURESERVER.NET> <f98165700912041023y3207d801r42f01c7a0c4352bb@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E7234378529368A@P3PW5EX1MB01.EX1.SECURESERVER.NET> <daf5b9570912041037t199cc9d3rbd4d31d327f8988b@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E7234378529369B@P3PW5EX1MB01.EX1.SECURESERVER.NET> <f98165700912041048s7f1f53bs27ec2b78f7f44c8b@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723437852936BC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Fri, 04 Dec 2009 11:12:43 -0800
Message-ID: <daf5b9570912041112h71c0644dm8c908478dbff2e9a@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Signature crypto
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Dec 2009 19:13:02 -0000

On Fri, Dec 4, 2009 at 11:10 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> I am trying to avoid the need to publish a specification every time you want
> to add a new MAC-based algorithm.

People are going to end up needing to write new code every time they
want to add a new MAC-based algorithm.

Cheers,
Brian