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

Sam Hartman <hartmans@mit.edu> Thu, 30 October 2003 20:04 UTC

Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9UK4FkT083738 for <ietf-sasl-bks@above.proper.com>; Thu, 30 Oct 2003 12:04:15 -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 h9UK4FZa083737 for ietf-sasl-bks; Thu, 30 Oct 2003 12:04:15 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from konishi-polis.mit.edu (KONISHI-POLIS.MIT.EDU [18.18.3.10]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9UK4EkT083732 for <ietf-sasl@imc.org>; Thu, 30 Oct 2003 12:04:14 -0800 (PST) (envelope-from hartmans@mit.edu)
Received: by konishi-polis.mit.edu (Postfix, from userid 8042) id 852C41515E8; Thu, 30 Oct 2003 15:04:03 -0500 (EST)
To: Cyrus Daboo <daboo@cyrusoft.com>
Cc: Ken Murchison <ken@oceana.com>, "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>, Mark Crispin <mrc@CAC.Washington.EDU>, Rob Siemborski <rjs3@andrew.cmu.edu>, ietf-sasl@imc.org
Subject: Re: Mark Crispin's comments on draft-ietf-sasl-plain-03.txt
References: <Pine.LNX.4.58-035.0310291904060.21275@sourcefour.andrew.cmu.edu> <6.0.0.22.0.20031029220508.046461a0@127.0.0.1> <Pine.LNX.4.60.0310292315180.23462@shiva1.cac.washington.edu> <6.0.0.22.0.20031030004344.0467f8e8@127.0.0.1> <3FA12679.3070409@oceana.com> <2147483647.1067515216@[10.0.1.8]>
From: Sam Hartman <hartmans@mit.edu>
Date: Thu, 30 Oct 2003 15:04:03 -0500
In-Reply-To: <2147483647.1067515216@[10.0.1.8]> (Cyrus Daboo's message of "Thu, 30 Oct 2003 12:00:16 -0500")
Message-ID: <tsl8yn2fq6k.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>

>>>>> "Cyrus" == Cyrus Daboo <daboo@cyrusoft.com> writes:

    Cyrus> | I think that encouraging/enforcing this point | is more
    Cyrus> important than cross-pollinating the docs with the same
    Cyrus> info.

    Cyrus> Again I would like to suggest some kind of "implementer's
    Cyrus> guide" document for SASL that would provide comprehensive
    Cyrus> examples for each type of protocol and each mechanism, as
    Cyrus> well as a list of the common implementation errors that
    Cyrus> have cropped up. That's not meant to replace having to read
    Cyrus> and understand each of the other documents, but can be used
    Cyrus> more as a starting point for multiple protocol
    Cyrus> implementations etc.


Why is this preferable to including protocol specific implementation
notes in the protocol profile documents?

--Sam