Re: [sasl] New Work Items - Kitten Recharter

"Scott Cantor" <cantor.2@osu.edu> Mon, 09 August 2010 13:55 UTC

Return-Path: <cantor.2@osu.edu>
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 4EE333A6AD6; Mon, 9 Aug 2010 06:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 0as1Z3Yumxhr; Mon, 9 Aug 2010 06:55:24 -0700 (PDT)
Received: from defang1.it.ohio-state.edu (defang1.it.ohio-state.edu [128.146.216.81]) by core3.amsl.com (Postfix) with ESMTP id 747D63A67FB; Mon, 9 Aug 2010 06:55:24 -0700 (PDT)
Received: from defang10.it.ohio-state.edu (defang10.it.ohio-state.edu [128.146.216.79]) by defang1.it.ohio-state.edu (8.13.7/8.13.1) with ESMTP id o79DtuCT003344; Mon, 9 Aug 2010 09:55:56 -0400
Received: from SNOWDOG (SNOWDOG.dyn.cio.osu.edu [164.107.161.86]) by defang10.it.ohio-state.edu (8.13.7/8.13.1) with ESMTP id o79Dtuu8008647; Mon, 9 Aug 2010 09:55:56 -0400
From: Scott Cantor <cantor.2@osu.edu>
To: 'Eliot Lear' <lear@cisco.com>, 'Shawn Emery' <shawn.emery@oracle.com>
References: <4C5CF47F.5040102@oracle.com> <4C5FC699.8060902@cisco.com>
In-Reply-To: <4C5FC699.8060902@cisco.com>
Date: Mon, 09 Aug 2010 09:55:58 -0400
Organization: The Ohio State University
Message-ID: <012a01cb37ca$984ce9d0$c8e6bd70$@osu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-index: AQJ85rZC8rLev/gGs0jS+zIiq+O3tALDC0ypkV+ugtA=
Content-language: en-us
X-CanIt-Geo: ip=128.146.216.79; country=US; region=OH; city=Columbus; latitude=39.9968; longitude=-82.9882; metrocode=535; areacode=614; http://maps.google.com/maps?q=39.9968,-82.9882&z=6
X-CanItPRO-Stream: outbound
X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.146.216.81
Cc: kitten@ietf.org, sasl@ietf.org
Subject: Re: [sasl] New Work Items - Kitten Recharter
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: Mon, 09 Aug 2010 13:55:25 -0000

> In Scott's draft, that occurs in step (4).  This requires the client to have
> substantially more capabilities than it might have today with either a fully
> functional web browser either built into the application or tied to the
> application via some form of IPC with sufficient semantic abilities to
> discern when to move through step 4 to step 5, but at the same time,
> provides for an overall simpler protocol flow than the document that Klaas
> and I have put forth.

My proposal uses ECP, which means the exchange with the IdP is generally (and can be required to be) SOAP over HTTP. There is generally no need for a web browser in the client, or anything like that. That's the IPC you're referring to.
 
> Discovery is also handled in Scott's draft.  That is something that we
> should consider incorporating into the other.

I believe the latest draft of Klaas' proposal does this, though in a different way from ECP of course.

-- Scott