IETF Logo Mail Archive

Re: [kitten] CB data characteristics Re: Fw: New Version Notification for draft-mills-kitten-sasl-oauth-02

Nico Williams <nico@cryptonector.com> Sat, 09 April 2011 06:54 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: kitten@core3.amsl.com
Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EFB63A69EC for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 23:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.944
X-Spam-Level:
X-Spam-Status: No, score=-1.944 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 jXAfD8FxwKnL for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 23:54:53 -0700 (PDT)
Received: from homiemail-a64.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by core3.amsl.com (Postfix) with ESMTP id 23E333A69E0 for <kitten@ietf.org>; Fri, 8 Apr 2011 23:54:53 -0700 (PDT)
Received: from homiemail-a64.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTP id 223FC438072 for <kitten@ietf.org>; Fri, 8 Apr 2011 23:56:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=hESjNkqzhobXRA7F+wYms jSe/qfObH+uT0BzYBxFfv95fJFb+6jb0Gf2MVXdM21HriO2TrK+rjq0/lsJfc6Qv BYJVC1wAW4UcNlSmbKCxscrbfla+WU88wGPTIyj/KBaU3cT7MD2js8M2Sl7SqW16 tUpV6SyAF4jqokBVLq3+0g=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=vmWPWJaNbk1PHKTaXW5b vvgt/Ks=; b=yZ+AXQ1nVCDDZm+AdshrcC58K4keowPhuKYDDnU84bOLKHd92/gT wqkCK4fFT38ImSOXkdmqhGw5U0mx6H7FvuB4vhvWSgSQZ5yvSoDyTmFK1l/XHp2v 7KjNVjOZnOIos/pLczqyvM2tIedpmkZQbCTOplq14wgnIDNgjYI3P1c=
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTPSA id F3E7443806C for <kitten@ietf.org>; Fri, 8 Apr 2011 23:56:38 -0700 (PDT)
Received: by vxg33 with SMTP id 33so3888828vxg.31 for <kitten@ietf.org>; Fri, 08 Apr 2011 23:56:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.100.1 with SMTP id eu1mr1271616vdb.174.1302332198257; Fri, 08 Apr 2011 23:56:38 -0700 (PDT)
Received: by 10.52.166.42 with HTTP; Fri, 8 Apr 2011 23:56:38 -0700 (PDT)
Received: by 10.52.166.42 with HTTP; Fri, 8 Apr 2011 23:56:38 -0700 (PDT)
In-Reply-To: <342439.86947.qm@web32303.mail.mud.yahoo.com>
References: <20110408070506.12ECB3A6A4C@core3.amsl.com> <416848.75882.qm__16525.0710481361$1302247955$gmane$org@web32314.mail.mud.yahoo.com> <87hba9b13i.fsf@latte.josefsson.org> <tsl4o684s5q.fsf@mit.edu> <754979.46407.qm@web32303.mail.mud.yahoo.com> <tslr59c3asv.fsf@mit.edu> <7EE86E89365CA94F8E7B8251F926071007AC12BC@CIO-KRC-D1MBX01.osuad.osu.edu> <tslipuo378b.fsf@mit.edu> <7EE86E89365CA94F8E7B8251F926071007AC141F@CIO-KRC-D1MBX01.osuad.osu.edu> <BANLkTi=XyB7cAF7wmC0mjQKgNsbWhT7QgA@mail.gmail.com> <991228.73942.qm@web32303.mail.mud.yahoo.com> <BANLkTikocC0_B8CYhjmSw+j-2vaTEHD=1g@mail.gmail.com> <342439.86947.qm@web32303.mail.mud.yahoo.com>
Date: Sat, 09 Apr 2011 01:56:38 -0500
Message-ID: <BANLkTimP_L=kYd8HExbW-0t3BJT2AtZcdw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "William J. Mills" <wmills@yahoo-inc.com>
Content-Type: multipart/alternative; boundary="20cf3071c6fc0e850304a076d841"
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] CB data characteristics Re: Fw: New Version Notification for draft-mills-kitten-sasl-oauth-02
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Apr 2011 06:54:53 -0000

On Apr 9, 2011 12:23 AM, "William J. Mills" <wmills@yahoo-inc.com> wrote:
>
> At the moment in the IANA registry I only see the tls-* channel bindings
defined.  Does that sound correct?  Does this mean the mechanism has to
roll-it's-own in cases other than TLS?

No, mechanisms never get to "roll their own".  The channel is responsible
for producing its CB data.  We know how to construct CB for other channel
types...  We just haven't registered them yet :)

v2.23.0 | Report a Bug | By Email