Re: ISMS working group and charter problems

Harald Tveit Alvestrand <harald@alvestrand.no> Wed, 07 September 2005 06:55 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECtqH-00034s-1p; Wed, 07 Sep 2005 02:55:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECtqE-00034n-VW for ietf@megatron.ietf.org; Wed, 07 Sep 2005 02:55:31 -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 CAA00861 for <ietf@ietf.org>; Wed, 7 Sep 2005 02:55:30 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECttK-00030f-P6 for ietf@ietf.org; Wed, 07 Sep 2005 02:58:45 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 5B7CB32009F; Wed, 7 Sep 2005 08:54:56 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23802-04; Wed, 7 Sep 2005 08:54:52 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id AB7ED32009B; Wed, 7 Sep 2005 08:54:51 +0200 (CEST)
Date: Wed, 07 Sep 2005 00:26:54 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: dcrocker@bbiw.net, Eliot Lear <lear@cisco.com>
Message-ID: <261A1E9D259E6FA3B9203B61@B50854F0A9192E8EC6CDA126>
In-Reply-To: <431DD94C.8070907@dcrocker.net>
References: <431DD3BD.9090108@cisco.com> <431DD94C.8070907@dcrocker.net>
X-Mailer: Mulberry/4.0.3 (Win32)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
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>
Content-Type: multipart/mixed; boundary="===============1451939080=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


--On 6. september 2005 11:00 -0700 Dave Crocker <dhc2@dcrocker.net> wrote:

> (By the way, I am awestruck at the potential impact of changing SNMP from
> UDP-based to TCP-based, given the extensive debates that took place about
> this when SNMP was originally developed.  Has THIS decision been subject
> to adequate external review, preferably including a pass by the IAB?)

just a formality note (and dropping nanog and the IESG):

I believe that the ISMS WG's proposal is about ADDING the possibility of 
SNMP over TCP, not about CHANGING SNMP to use TCP.
UDP will still work.

And I believe Eliot's concern is about letting the TCP session that carries 
the SNMP PDUs be opened from the agent to the manager, rather than from the 
manager to the agent (yes I know - this is SNMPv1 terminology, but I've 
forgotten the SNMPv3 terminology); that is another feature that comes in 
addition to what the group is apparently currently working on.
And just BTW: I find "call home" reasonable to specify too, once you've 
done TCP. It's obvious enough that I think it will be added to 
implementations whether or not we specify it, so we should have very strong 
reasons not to do so.
I don't even believe you need to "turn" the session, since SNMPv3 doesn't 
recognize the concept of a "direction" for a session.... just let the PDUs 
flow....

Disclaimer: I, too, have not seen the charter being proposed, and I have 
not followed the ISMS group. I have, however, once upon a time been 
responsible AD for the SNMPv3 WG.

                           Harald

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