RE: ISMS working group and charter problems

"Fleischman, Eric" <eric.fleischman@boeing.com> Wed, 07 September 2005 19:20 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED5T7-00043T-Rh; Wed, 07 Sep 2005 15:20:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED5T5-00041F-Kp for ietf@megatron.ietf.org; Wed, 07 Sep 2005 15:20:23 -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 PAA10866 for <ietf@ietf.org>; Wed, 7 Sep 2005 15:20:22 -0400 (EDT)
Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED5WI-0007i2-TO for ietf@ietf.org; Wed, 07 Sep 2005 15:23:44 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6]) by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id OAA12402; Wed, 7 Sep 2005 14:20:08 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j87JK7S10079; Wed, 7 Sep 2005 14:20:07 -0500 (CDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Sep 2005 12:20:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 07 Sep 2005 12:20:03 -0700
Message-ID: <474EEBD229DF754FB83D256004D02108BBC8F1@XCH-NW-6V1.nw.nos.boeing.com>
Thread-Topic: ISMS working group and charter problems
Thread-Index: AcWz4D5uXCF0NUMpSsetC6DFxMZnKgAABveA
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: Margaret Wasserman <margaret@thingmagic.com>, Harald Tveit Alvestrand <harald@alvestrand.no>, dcrocker@bbiw.net, Eliot Lear <lear@cisco.com>
X-OriginalArrivalTime: 07 Sep 2005 19:20:04.0148 (UTC) FILETIME=[264C5F40:01C5B3E1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable
Cc: 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

>You are correct that, in the current plan, the ISMS model would be 
>TCP-based.  That is what I meant to state by saying "UDP and the 
>current SNMPv3 USM security mechanisms will still work".  ISMS will 
>be TCP-based, but UDP/USM will still work -- in fact, it will still 
>also be mandatory-to-implement for SNMPv3 compliance...  I did not 
>mean to imply that UDP/ISMS will work, or even that it will ever be 
>defined.

Yes, Margaret, we are tracking each other on that point. 

However, the nature of my objection was that I believe that this state
of affairs is unacceptable. Since I have concluded, for the reasons I
partially enumerated in my previous post, that historic SNMPv3 USM is
unusable for very large deployments, what good is devising an ISMS
supplement that is also partly/largely unusable for different reasons
(i.e., transport reasons (ISMS) rather than security reasons SNMPv3
USM))?

I believe that network management is too important a functionality to be
designed such that it can only be usable within highly confined
environmental constraints.

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