Re: [Crisp] I-D ACTION:draft-ietf-crisp-iris-xpc-03.txt

Andrew Newton <andy@hxr.us> Wed, 22 March 2006 23:20 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMCcW-0001yt-N9; Wed, 22 Mar 2006 18:20:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMCcV-0001yo-T2 for crisp@ietf.org; Wed, 22 Mar 2006 18:20:03 -0500
Received: from zeke.blacka.com ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMCcU-0008O9-Iy for crisp@ietf.org; Wed, 22 Mar 2006 18:20:03 -0500
Received: from [130.129.130.179] ([::ffff:130.129.130.179]) (AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA) by zeke.ecotroph.net with esmtp; Wed, 22 Mar 2006 18:19:06 -0500 id 01584386.4421DB6B.00004252
In-Reply-To: <487354f10603221405m410c5c39k@mail.gmail.com>
References: <E1F7Ijq-0000Lb-92@newodin.ietf.org> <487354f10603201041k46b00b72x@mail.gmail.com> <95328E91-0624-4A1D-BB87-FB1D33D0681C@hxr.us> <487354f10603221405m410c5c39k@mail.gmail.com>
Mime-Version: 1.0
Message-Id: <9C5C92CF-F257-4AAE-8A33-3C0DF898A53A@hxr.us>
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] I-D ACTION:draft-ietf-crisp-iris-xpc-03.txt
Date: Wed, 22 Mar 2006 18:19:54 -0500
To: Robert Martin-Legene <rlegene@gmail.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: crisp@ietf.org
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1509774645=="
Errors-To: crisp-bounces@ietf.org

On Mar 22, 2006, at 5:05 PM, Robert Martin-Legene wrote:

> BTW, is it a problem to mention SASL PLAIN when RFC2595 is for "IMAP,
> POP3 and ACAP"?  Section 6 paragraph 2 of the RFC does actually say
> "This defines the "PLAIN" SASL mechanism for use with ACAP and other
> protocols with no clear-text login command.". So maybe it's ok? Btw,
> it's not in the references either, so maybe I'm just barking up the
> wrong tree.

At the time this draft was written, the new SASL PLAIN draft was not  
done and the normative reference to SASL PLAIN is 2595.  Other  
protocols have done this too.  Since I have to respin this draft,  
I'll check to see if the reference has changed to the new document  
that pulls SASL PLAIN out of IMAP.

-andy
_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp