RE: ISMS working group and charter problems

"Nelson, David" <dnelson@enterasys.com> Thu, 08 September 2005 14:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDNQP-0001H6-Mr; Thu, 08 Sep 2005 10:30:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDNQN-0001Gn-9h for ietf@megatron.ietf.org; Thu, 08 Sep 2005 10:30:47 -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 KAA22972 for <ietf@ietf.org>; Thu, 8 Sep 2005 10:30:44 -0400 (EDT)
Received: from gtfw2.enterasys.com ([12.25.1.128] ident=firewall-user) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDNTf-0005QH-RN for ietf@ietf.org; Thu, 08 Sep 2005 10:34:18 -0400
Received: from NHROCAVG2.ets.enterasys.com ([134.141.79.124]) by gtfw2.enterasys.com (0.25.1/8.12.6) with ESMTP id j88EUaZC010133 for <ietf@ietf.org>; Thu, 8 Sep 2005 10:30:36 -0400 (EDT)
Received: from psmtp.com ([134.141.79.124]) by 134.141.79.124 with InterScan Messaging Security Suite; Thu, 08 Sep 2005 10:30:37 -0400
Received: from source ([134.141.79.122]) by host ([134.141.79.124]) with SMTP; Thu, 08 Sep 2005 10:30:30 -0400
Received: from maandmbx2 ([134.141.93.31]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 8 Sep 2005 10:30:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 08 Sep 2005 10:26:46 -0400
Message-ID: <2A5E4540D4D5934D9A1E7E0B0FDB2D6901032589@MAANDMBX2.ets.enterasys.com>
Thread-Topic: ISMS working group and charter problems
Thread-Index: AcW0f5LvVZaF5E3nQgyBXMBmh+SE0AAAPl1Q
From: "Nelson, David" <dnelson@enterasys.com>
To: IETF Discussion <ietf@ietf.org>
X-OriginalArrivalTime: 08 Sep 2005 14:30:30.0718 (UTC) FILETIME=[DD5715E0:01C5B481]
X-pstn-version: pmps:sps_win32_1_1_0c1 pase:2.8
X-pstn-levels: (C:90.8148 M:94.5022 P:95.9108 R:95.9108 S:65.9504 )
X-pstn-settings: 4 (0.2500:0.2500) p:13 m:13 c:14 r:13
X-pstn-addresses: from <dnelson@enterasys.com> forward (org good)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: quoted-printable
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

Daniel Senie writes...

> Based on your email, the consensus of the group is that TCP is good
> enough, since it'll only be interesting to manage networks that are
> operating cleanly. I can't imagine that's what the WG really
> concluded, but that's how your email reads.

It seems to me that the existing USM, SNMP over UDP, and a local user
account would be sufficient as a fallback network management method when
the network is experiencing a meltdown.  Just as you have a local
/etc/passwd file on your UNIX workstations, for those occasions when the
NIS server is unreachable.  I don't think anyone believes that ISMS will
obviate the need for at least one local account on managed entities, to
cover this type of situation.


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