Re: Summary of the SASL working group meeting
Sam Hartman <hartmans@mit.edu> Wed, 16 July 2003 15:21 UTC
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h6GFLZqt086322 for <ietf-sasl-bks@above.proper.com>; Wed, 16 Jul 2003 08:21:35 -0700 (PDT) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h6GFLZVn086321 for ietf-sasl-bks; Wed, 16 Jul 2003 08:21:35 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from konishi-polis.mit.edu ([81.160.157.184]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h6GFLYqt086294 for <ietf-sasl@imc.org>; Wed, 16 Jul 2003 08:21:34 -0700 (PDT) (envelope-from hartmans@mit.edu)
Received: by konishi-polis.mit.edu (Postfix, from userid 8042) id 21B06151D76; Wed, 16 Jul 2003 11:21:27 -0400 (EDT)
To: Ken Murchison <ken@oceana.com>
Cc: SASL mailing list <ietf-sasl@imc.org>
Subject: Re: Summary of the SASL working group meeting
References: <tsln0feopz4.fsf@mit.edu> <3F1554B6.9090601@oceana.com>
From: Sam Hartman <hartmans@mit.edu>
Date: Wed, 16 Jul 2003 11:21:27 -0400
In-Reply-To: <3F1554B6.9090601@oceana.com> (Ken Murchison's message of "Wed, 16 Jul 2003 09:35:50 -0400")
Message-ID: <tslsmp64hvs.fsf@mit.edu>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>
>>>>> "Ken" == Ken Murchison <ken@oceana.com> writes: Ken> Sam Hartman wrote: >> Keith Burdis agreed to submit an SASL applicability statement >> as an individual submission. His document will include >> comparisons of the various sasl mechanisms and their security >> properties. Sam agreed to propose an outline for the document. >> The working group will discuss rechartering to include this >> document after the first revision. Ken> How will this document differ from the following? Ken> http://www.ietf.org/internet-drafts/draft-iab-auth-mech-00.txt The IAB document seems to discuss mechanisms at a much lower level. I was invisioning comparing SASL to similar technologies like EAP, GSSAPI and TLS. And I was hoping to discuss sasl mechansims as sasl mechanisms. We should definitely point to the IAB document and when discussing mechanisms describe them in the category they fit into that framework.
- Re: Summary of the SASL working group meeting Sam Hartman
- Summary of the SASL working group meeting Sam Hartman
- Re: Summary of the SASL working group meeting Ken Murchison