beep use of sasl

"Marshall Rose" <mrose+mtr.netnews@dbc.mtview.ca.us> Sat, 07 October 2000 18:31 UTC

Received: by ns.secondary.com (8.9.3/8.9.3) id LAA09044 for ietf-sasl-bks; Sat, 7 Oct 2000 11:31:24 -0700 (PDT)
Received: from dbc.mtview.ca.us (ppp-63-207-83-130.ded.pacbell.net [63.207.83.130]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA09040 for <ietf-sasl@imc.org>; Sat, 7 Oct 2000 11:31:19 -0700 (PDT)
Received: from shaylashayla (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131]) by dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id e97IYC112657; Sat, 7 Oct 2000 11:34:13 -0700 (PDT)
Message-ID: <01dc01c0308d$5e43d680$8353cf3f@dbc.mtview.ca.us>
From: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
To: ietf-sasl@imc.org
Cc: Marshall Rose <mrose@dbc.mtview.ca.us>
References: <5B90AD65A9E8934987DB0C8C0762657446D1D4@DF-BOWWOW.platinum.corp.microsoft.com> <20001001001342.A55138@rucus.ru.ac.za>
Subject: beep use of sasl
Date: Sat, 07 Oct 2000 11:35:29 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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>

the IETF work on BEEP - a framework for application layer protocols -
includes the use of both SASL and TLS.

although several people have individually commented/improved on the
specification, a solicitation has never been made to this mailing list for
comments.

i refer you to Sections 4 and 9 of

    http://search.ietf.org/internet-drafts/draft-ietf-beep-framework-02.txt

if you are interested, please review these sections and direct
questions/comments/suggestions to either myself or bxxpwg@invisible.net

earlier versions of this specification have already been independently
implemented with various SASL mechanisms; even so, any experience from folks
who have integrated SASL with other application protocols is appreciated.

thanks!

/mtr