Mark Crispin's comments on draft-ietf-sasl-plain-03.txt

Rob Siemborski <rjs3@andrew.cmu.edu> Thu, 30 October 2003 00:05 UTC

Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9U05DkT053844 for <ietf-sasl-bks@above.proper.com>; Wed, 29 Oct 2003 16:05:13 -0800 (PST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id h9U05DhD053842 for ietf-sasl-bks; Wed, 29 Oct 2003 16:05:13 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from smtp1.andrew.cmu.edu (SMTP1.andrew.cmu.edu [128.2.10.81]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9U05BkT053836 for <ietf-sasl@imc.org>; Wed, 29 Oct 2003 16:05:11 -0800 (PST) (envelope-from rjs3@andrew.cmu.edu)
Received: from SOURCEFOUR.andrew.cmu.edu (SOURCEFOUR.andrew.cmu.edu [128.2.122.8]) (user=rjs3 mech=GSSAPI (0 bits)) by smtp1.andrew.cmu.edu (8.12.10/8.12.10) with ESMTP id h9U05CE7016851; Wed, 29 Oct 2003 19:05:12 -0500
Date: Wed, 29 Oct 2003 19:05:11 -0500
From: Rob Siemborski <rjs3@andrew.cmu.edu>
To: ietf-sasl@imc.org
cc: mrc@CAC.Washington.EDU
Subject: Mark Crispin's comments on draft-ietf-sasl-plain-03.txt
Message-ID: <Pine.LNX.4.58-035.0310291904060.21275@sourcefour.andrew.cmu.edu>
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>

Mark had a few comments on the PLAIN draft, mostly centered around the
issue of the initial response examples.  I tend to agree with his
assessments.  I'll note (as Kurt did), that this document has already been
through the WG last call.

a) ACAP is probably not the best choice of protocol for the example, since
it is not in wide use.  A protocol such as SMTP is probably more
appropriate (especially given the trouble we've seen with SMTP
implementations getting initial response handling correct).  SMTP has the
added advantage of having 3 digit response codes that in other have
optional text -- though that is not the case in the SASL challenges.

b) An example demonstrating plain without using the initial response
argument on a protocol that supports it.  This would again help to address
the implementation problems with the optional initial client send.

There are examples in draft-siemborski-rfc2554bis-00.txt (using SMTP) that
satisfy this, and could be used.

One thing that may also help is to place reminders in mechanism (and
protocol) documents that a correct implementation of SASL for a given
protocol requires an understanding of the protocol profile, the SASL
framework, and the mechanism, and that reading all three documents is
necessary to get it right.  Of course, in a perfect world, normative
references would be enough, but experience seems to be showing this not to
be the case.

(I'd also like to encourage people again to read over and comment more
generally on draft-siemborski-rfc2554bis-00.txt and
draft-siemborski-rfc1734bis-00.txt).

We're also both planning on being at the SASL WG meeting in Minneapolis,
and can discuss this further then.

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski | Andrew Systems Group * Research Systems Programmer
PGP:0x5CE32FCC | Cyert Hall 207 * rjs3@andrew.cmu.edu * 412.268.7456
-----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS/IT/CM/PA d- s+: a-- C++++$ ULS++++$ P+++$ L+++(++++) E W+ N o? K-
w O- M-- V-- PS+ PE++ Y+ PGP+ t+@ 5+++ R@ tv-@ b+ DI+++ G e++ h r- y?
------END GEEK CODE BLOCK-----