a dedicated SASL WG
"Raif S. Naffah" <raif@fl.net.au> Sat, 10 March 2001 19:40 UTC
Received: by above.proper.com (8.9.3/8.9.3) id LAA11608 for ietf-sasl-bks; Sat, 10 Mar 2001 11:40:13 -0800 (PST)
Received: from int-mail.syd.fl.net.au (int-mail.syd.fl.net.au [202.181.0.28]) by above.proper.com (8.9.3/8.9.3) with ESMTP id LAA11603 for <ietf-sasl@imc.org>; Sat, 10 Mar 2001 11:40:03 -0800 (PST)
Received: from solomon.fl.net.au (a4-p54.syd.fl.net.au [202.181.2.118]) by int-mail.syd.fl.net.au (Postfix) with ESMTP id AFD7D1685A; Sun, 11 Mar 2001 06:39:49 +1100 (EST)
Message-Id: <5.0.0.25.1.20010311061903.00a4a070@mail.syd.fl.net.au>
X-Sender: raif@mail.syd.fl.net.au
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Sun, 11 Mar 2001 06:39:55 +1100
To: SASL <ietf-sasl@imc.org>
From: "Raif S. Naffah" <raif@fl.net.au>
Subject: a dedicated SASL WG
Cc: jlinn@rsasecurity.com, jis@mit.edu, mleech@nortelnetworks.com, "Raif S. Naffah" <raif@forge.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
hi there, There are currently many SASL-related drafts other than the one (SASL GSS-API mechanisms <http://search.ietf.org/internet-drafts/draft-ietf-cat-sasl-gssapi-02.txt>) listed under the Common Authentication Technology WG drafts, namely: A. new SASL mechanisms: 1. Secure Remote Password SASL Mechanism <http://search.ietf.org/internet-drafts/draft-burdis-cat-srp-sasl-04.txt> 2. SM2 -- A Session Management Capable SASL Mechanism <http://search.ietf.org/internet-drafts/draft-naffah-cat-sasl-sm2-00.txt> 3. X.509 Authentication SASL Mechanism <http://search.ietf.org/internet-drafts/draft-ietf-ldapext-x509-sasl-03.txt> 4. ISO/IEC 9798-3 Authentication SASL Mechanism <http://search.ietf.org/internet-drafts/draft-zuccherato-9798-3-sasl-02.txt> B. Java SASL API: 5. The Java SASL Application Program Interface <http://search.ietf.org/internet-drafts/draft-weltman-java-sasl-04.txt> C. Using SASL with other protocols: 6. Upgrading to SASL Within HTTP/1.1 <http://search.ietf.org/internet-drafts/draft-burdis-http-sasl-00.txt> 7. SASL in HTTP/1.1 <http://search.ietf.org/internet-drafts/draft-nystrom-http-sasl-00.txt> 8. LDAP Authentication Response Control <http://search.ietf.org/internet-drafts/draft-weltman-ldapv3-auth-response-03.txt> As clarified by the Common Authentication Technology (CAT) WG Chair, John Linn, SASL mechanisms, APIs, and SASL/protocol integration documents have not been work items of the CAT-WG, and CAT has itself been placed in an idle state, pending on possible advancement of its existing RFCs but not undertaking new work. My question to the list is: how ready, and/or willing, is the SASL community to charter a new WG dedicated to SASL? TIA + cheers; rsn cc: John Linn, Jeffrey Schiller, Marcus Leech.
- a dedicated SASL WG Raif S. Naffah
- Re: a dedicated SASL WG Kurt D. Zeilenga
- Re: a dedicated SASL WG Leif Johansson
- Re: a dedicated SASL WG Kurt D. Zeilenga
- RE: a dedicated SASL WG Paul Leach
- RE: a dedicated SASL WG Kurt D. Zeilenga
- new SASL Java implementation release Raif S. Naffah
- Re: a dedicated SASL WG Raif S. Naffah
- Re: a dedicated SASL WG Kurt D. Zeilenga
- Re: a dedicated SASL WG Chris Newman
- Re: a dedicated SASL WG Kurt D. Zeilenga
- Re: a dedicated SASL WG Lawrence Greenfield
- Re: a dedicated SASL WG Chris Newman
- Re: WG formation: AD advice and consent Jeff.Hodges