IETF Logo Mail Archive

Re: [sasl] Discussion about SAML&OpenID SASL mechanisms during the Apps Area meeting in Anaheim

=JeffH <Jeff.Hodges@KingsMountain.com> Wed, 03 March 2010 21:04 UTC

Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: sasl@core3.amsl.com
Delivered-To: sasl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CF2428C25A for <sasl@core3.amsl.com>; Wed, 3 Mar 2010 13:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.665
X-Spam-Level:
X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_46=0.6]
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 L141D-tQlM-y for <sasl@core3.amsl.com>; Wed, 3 Mar 2010 13:04:40 -0800 (PST)
Received: from outbound-mail-01.bluehost.com (outbound-mail-01.bluehost.com [69.89.21.11]) by core3.amsl.com (Postfix) with SMTP id 1BAF128C186 for <sasl@ietf.org>; Wed, 3 Mar 2010 13:04:40 -0800 (PST)
Received: (qmail 10300 invoked by uid 0); 3 Mar 2010 21:04:41 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy1.bluehost.com with SMTP; 3 Mar 2010 21:04:41 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=w42W8REyuFlgP11aeVzAC7T4+jfYSGqzeV70j0+ie6DXtpvVSgI9ONjTjwbrcmEuhlQerX7OoYs7XZuNbas8tHKWX6za8x2liDYAjL2CoyAS3Gpd3zrrb/0jTtREqyAB;
Received: from c-67-161-32-29.hsd1.ca.comcast.net ([67.161.32.29] helo=[192.168.11.16]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1NmvkH-0003bi-EU; Wed, 03 Mar 2010 14:04:41 -0700
Message-ID: <4B8ECEE7.6050109@KingsMountain.com>
Date: Wed, 03 Mar 2010 13:04:39 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: IETF SASL WG list <sasl@ietf.org>, Eliot Lear <lear@cisco.com>, Klaas Wierenga <klaas@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 67.161.32.29 authed with jeff.hodges+kingsmountain.com}
Subject: Re: [sasl] Discussion about SAML&OpenID SASL mechanisms during the Apps Area meeting in Anaheim
X-BeenThere: sasl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SASL Working Group <sasl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sasl>
List-Post: <mailto:sasl@ietf.org>
List-Help: <mailto:sasl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sasl>, <mailto:sasl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2010 21:04:41 -0000

Eliot, Klaas, Hannes, & Hank,

> If you – or anyone else –  have 
> substantial comments to make the documents less "handwavy", the authors 
> would be grateful.  These are individual -00s, btw.  We would expect the 
> docs to evolve.  We're also looking for comments on the general approach.

Which mailing list should comments be sent to, sasl@  ?

thanks,

=JeffH

v2.23.0 | Report a Bug | By Email