Re: ISMS working group and charter problems

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Mon, 12 September 2005 13:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEnzW-0002Es-8K; Mon, 12 Sep 2005 09:04:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEnzO-0002BM-Id for ietf@megatron.ietf.org; Mon, 12 Sep 2005 09:04:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16799 for <ietf@ietf.org>; Mon, 12 Sep 2005 09:04:40 -0400 (EDT)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEo3Q-00031k-Av for ietf@ietf.org; Mon, 12 Sep 2005 09:09:01 -0400
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 5E8AC3AAA4; Mon, 12 Sep 2005 15:04:29 +0200 (CEST)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 13252-04; Mon, 12 Sep 2005 15:04:28 +0200 (CEST)
Received: from boskop.local (unknown [10.50.250.214]) by hermes.iu-bremen.de (Postfix) with ESMTP id 22B843AA97; Mon, 12 Sep 2005 15:04:28 +0200 (CEST)
Received: by boskop.local (Postfix, from userid 501) id 65A743F35B9; Mon, 12 Sep 2005 15:04:27 +0200 (CEST)
Date: Mon, 12 Sep 2005 15:04:27 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Eliot Lear <lear@cisco.com>
Message-ID: <20050912130427.GB1089@boskop.local>
Mail-Followup-To: Eliot Lear <lear@cisco.com>, Sam Hartman <hartmans-ietf@mit.edu>, IETF Discussion <ietf@ietf.org>
References: <200509081520.IAA02206@cisco.com> <00a101c5b49c$5e913680$0601a8c0@pc6> <tslirxbnyqz.fsf@cz.mit.edu> <20050908200547.GA25650@boskop.local> <43252D43.3050602@cisco.com> <20050912082646.GA520@boskop.local> <43255285.6040707@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <43255285.6040707@cisco.com>
User-Agent: Mutt/1.5.10i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF Discussion <ietf@ietf.org>
Subject: Re: ISMS working group and charter problems
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Mon, Sep 12, 2005 at 12:03:49PM +0200, Eliot Lear wrote:
> Just to clarify:
> > The option
> > of SSH is mentioned in the architectural document, even though we did
> > not went to the glory details of all the options that were on the
> > table back then (TLS, SASL, DTLS, SSH). In fact, I fail to see how you
> > get the conclusion that we went down to zero drafts by the end of
> > IETF-63.
> 
> The four I had in mind were TLSM, EUSM, SBSM, and SNMP/BEEP.  Prior to
> the meeting the WG had ruled out the first three and during the meeting
> the fourth was also shelved, leaving none.

This does not match my recollection. My understanding was that the WG
decided prior to the IETF-63 that it will follow the transport mapping
security model (TMSM) approach, which was initially called "transport
layer security model" (TLSM). Under the discussion during the IETF-63
meeting were the selection of transport layer security protocols that
could be used, such as TLS, SSH, DTLS, and BEEP. This is inline with
what <draft-kaushik-isms-btsm-01> says:

   This document leverages the TMSM framework and describes the use of
   the BEEP for securing SNMPv3.  This specification describes BEEP
   Transport Mapping Security Model.

I don't think BEEP was even on the table when the discussions between
EUSM, SBSM and TMSM was made - at least it is not mentioned in the
evaluation document <draft-ietf-isms-proposal-comparison>.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf