Re: ISMS working group

Daniel Senie <dts@senie.com> Mon, 12 September 2005 14:16 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEp6t-0005y7-V9; Mon, 12 Sep 2005 10:16:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEp6q-0005xP-LY; Mon, 12 Sep 2005 10:16:36 -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 KAA20751; Mon, 12 Sep 2005 10:16:25 -0400 (EDT)
Received: from parsley.amaranth.net ([204.10.1.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEpAs-0004pN-FF; Mon, 12 Sep 2005 10:20:47 -0400
Received: from ancho.senie.com (c-24-34-19-2.hsd1.ma.comcast.net [24.34.19.2]) (authenticated bits=0) by parsley.amaranth.net (8.12.11/8.12.11) with ESMTP id j8CEG6hP010494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 10:16:08 -0400
Message-Id: <6.2.3.4.2.20050912095651.07d12800@mail.amaranth.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Mon, 12 Sep 2005 10:06:43 -0400
To: Margaret Wasserman <margaret@thingmagic.com>, Eliot Lear <lear@cisco.com>
From: Daniel Senie <dts@senie.com>
In-Reply-To: <p062007e1bf4b28530a35@[192.168.2.7]>
References: <431DD59A.4000400@ofcourseimright.com> <AE6514F0-4714-4A48-9F56-A155823489F2@moonhill.org> <p0620074bbf44d3d23a6d@[192.168.2.7]> <432531CB.3070109@cisco.com> <p062007e1bf4b28530a35@[192.168.2.7]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on parsley.amaranth.net
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: ietf@ietf.org, iesg@ietf.org
Subject: Re: ISMS working group
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

At 08:44 AM 9/12/2005, Margaret Wasserman wrote:

>Hi Eliot,
>
>At 9:44 AM +0200 9/12/05, Eliot Lear wrote:
>>Actually, depending on how the solution is developed it certainly CAN
>>help the problem with the manager being outside a NAT.  But we are now
>>being somewhat loose with terms, so let me be more specific.
>
>I am sorry that I attempted to state any properties of the call-home 
>solution, because it is clear that the term is not well-enough 
>defined or specified to be discussed clearly.  I thought that I 
>understood what it was, but apparently I am mistaken.
>
>If you really believe that this solution is needed, I think you 
>would do best to write a draft and _then_ try to get it adopted by 
>an appropriate WG.

Stepping back a bit from this discussion and thinking about what has 
been said to date, it occurs to me that part of the problem with how 
the IETF presently does business comes from a reliance on 
pigeon-holing any particular work into one of several areas. The 
Security area is working on fixing the security issues of SNMP, but 
O&M is the "home" of SNMP. Is there enough involvement of folks from 
both sides? Should there be working groups that are co-owned by 
multiple areas/ADs? Would this result in a more balanced set of conclusions?

Eliot rightly asks the question in one of his emails whether SNMP 
changes should be considered more widely so as to develop one new 
protocol revision for implementers to work toward, rather than a 
series of incremental changes. If indeed we're talking about SNMPv4, 
then perhaps a series of drafts should work toward that, and be 
unified into one or a few proposed standard documents that are 
released at one time, with all of the new work.



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