Re: Agenda items to discuss

Nicolas Williams <Nicolas.Williams@sun.com> Wed, 29 October 2003 22:55 UTC

Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9TMtKkT049836 for <ietf-sasl-bks@above.proper.com>; Wed, 29 Oct 2003 14:55:20 -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 h9TMtKOS049835 for ietf-sasl-bks; Wed, 29 Oct 2003 14:55:20 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9TMtJkT049828 for <ietf-sasl@imc.org>; Wed, 29 Oct 2003 14:55:19 -0800 (PST) (envelope-from nw141292@binky.central.sun.com)
Received: from centralmail2brm.Central.Sun.COM ([129.147.62.14]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9TMtGxA014090; Wed, 29 Oct 2003 14:55:16 -0800 (PST)
Received: from binky.central.sun.com (binky.Central.Sun.COM [129.153.128.104]) by centralmail2brm.Central.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id h9TMtG58017978; Wed, 29 Oct 2003 15:55:16 -0700 (MST)
Received: from binky.central.sun.com (localhost [127.0.0.1]) by binky.central.sun.com (8.12.5+Sun/8.12.3) with ESMTP id h9TMpAQx010060; Wed, 29 Oct 2003 14:51:10 -0800 (PST)
Received: (from nw141292@localhost) by binky.central.sun.com (8.12.5+Sun/8.12.3/Submit) id h9TMp9Jc010059; Wed, 29 Oct 2003 14:51:09 -0800 (PST)
Date: Wed, 29 Oct 2003 14:51:09 -0800
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Sam Hartman <hartmans@mit.edu>
Cc: ietf-sasl@imc.org
Subject: Re: Agenda items to discuss
Message-ID: <20031029225109.GB24528@binky.central.sun.com>
Mail-Followup-To: Sam Hartman <hartmans@mit.edu>, ietf-sasl@imc.org
References: <20031029184405.2F80E1515E8@konishi-polis.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20031029184405.2F80E1515E8@konishi-polis.mit.edu>
User-Agent: Mutt/1.4i
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>

On Wed, Oct 29, 2003 at 01:44:05PM -0500, Sam Hartman wrote:
> * There was some discussion of multiple layers of encryption (TLS vs security layers) in XMPP; do we want
> to develop guidance for protocol designers on this issue?

I think this should be discussed.

I think the guidance we want to give is: don't delegate session
protection from one layer to another without confirming that the
end-points at both layers are the same.

See:

http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-channel-bindings-00.txt


It would be nice if SASL had a channel bindings facility.  Such a
facility could be added or applications could be encouraged to exchange
channel bindings data integrity protected at the SASL layer.

Can GSS-API channel bindings facility be used when using the GSS-* SASL
mechanisms?

Cheers,

Nico
--