Re: ISMS working group and charter problems

Eliot Lear <lear@cisco.com> Mon, 12 September 2005 14:05 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEowG-0003mM-6m; Mon, 12 Sep 2005 10:05:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEowB-0003m3-3B for ietf@megatron.ietf.org; Mon, 12 Sep 2005 10:05:37 -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 KAA19477 for <ietf@ietf.org>; Mon, 12 Sep 2005 10:05:25 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEp0E-0004Ul-MX for ietf@ietf.org; Mon, 12 Sep 2005 10:09:48 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 12 Sep 2005 07:05:16 -0700
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8CE58KC003313; Mon, 12 Sep 2005 07:05:08 -0700 (PDT)
Received: from [212.254.247.4] (ams-clip-vpn-dhcp4541.cisco.com [10.61.81.188]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j8CEHrGJ013601; Mon, 12 Sep 2005 07:17:54 -0700
Message-ID: <43258B16.3080109@cisco.com>
Date: Mon, 12 Sep 2005 16:05:10 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: j.schoenwaelder@iu-bremen.de
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> <20050912130427.GB1089@boskop.local>
In-Reply-To: <20050912130427.GB1089@boskop.local>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1009; t=1126534675; x=1126966875; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:Re=3A=20ISMS=20working=20group=20and=20charter=20problems| From:Eliot=20Lear=20<lear@cisco.com>| Date:Mon,=2012=20Sep=202005=2016=3A05=3A10=20+0200| Content-Type:text/plain=3B=20charset=3DISO-8859-1| Content-Transfer-Encoding:7bit; b=TMNYjNnwR2GYZAxKzcKmDcrNd0+ly7FBaUWfeg7v4+/5W9jcOzAWxytCQ5VoPLjSJMPvH7gJ mJiw44MFkbHCZ85+1nGplNq4e+5oASOjJCWLmwbfLA91PDH7KjyE2H6BhUwOLx7ShtyQuPO3BKE bdXvTMZljPbR/MdWHzHUC0RI=
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
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
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


Juergen Schoenwaelder wrote:

>>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).

Which is the architectural model extracted from 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>.

Juergen asked that it be presented at IETF-63, which is why I included it.

Eliot

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