Re: ISMS working group and charter problems

Michael Thomas <mat@cisco.com> Wed, 07 September 2005 15:41 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED23b-0005gc-M6; Wed, 07 Sep 2005 11:41:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED23Y-0005dO-SK for ietf@megatron.ietf.org; Wed, 07 Sep 2005 11:41:49 -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 LAA27883 for <ietf@ietf.org>; Wed, 7 Sep 2005 11:41:46 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED26k-00019V-F3 for ietf@ietf.org; Wed, 07 Sep 2005 11:45:07 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 07 Sep 2005 08:41:38 -0700
X-IronPort-AV: i="3.96,176,1122879600"; d="scan'208"; a="339513429:sNHT35105120"
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 j87FfYKC013545; Wed, 7 Sep 2005 08:41:34 -0700 (PDT)
Received: from [216.102.208.12] (sjc-vpn6-293.cisco.com [10.21.121.37]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j87Fai10008301; Wed, 7 Sep 2005 08:36:46 -0700
Message-ID: <431F0A2B.4060805@cisco.com>
Date: Wed, 07 Sep 2005 08:41:31 -0700
From: Michael Thomas <mat@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Thunderbird/0.8 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <431DD3BD.9090108@cisco.com> <431DD94C.8070907@dcrocker.net> <261A1E9D259E6FA3B9203B61@B50854F0A9192E8EC6CDA126> <431EB020.8090101@zurich.ibm.com>
In-Reply-To: <431EB020.8090101@zurich.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=885; t=1126107408; x=1126539608; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=mat@cisco.com; z=Subject:Re=3A=20ISMS=20working=20group=20and=20charter=20problems| From:Michael=20Thomas=20<mat@cisco.com>| Date:Wed,=2007=20Sep=202005=2008=3A41=3A31=20-0700| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=OCCSRdtLD2/eFeQMrhRwah5z8s5ev3pYc2fCMrxVCEVKPl8yrJyR4TAUwVVd6hRflwEwONYh d1vqjcNM9TAjKxtrCLy7TO4+suJtNBpyJUmP3WD13kZpyh29x7xmK34pvkBJXIM5BZp4stIvIwP 9SlTm4/3P1b5KWlidj2DuZ7s=
Authentication-Results: imail.cisco.com; header.From=mat@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, dcrocker@bbiw.net, Eliot Lear <lear@cisco.com>, 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

Brian E Carpenter wrote:
>> 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.
> 
> 
> "Call home" is IMHO a fairly radical departure for SNMP and
> raises trust model questions that I don't find easy to get
> hold of. It seems quite distinct from both firewall traversal
> and NAT traversal, conceptually, even if they might be
> a side-effect of calling home.

Really? What is a trap/inform but a "call home" by another
name?

In answer to Margaret's question about how it would know
where to "call home", it seems to me to be about the same
problem as with traps/informs. I haven't had anything to do
with this wg, but it seems pretty plausible that you'd
initiate the session from the agent using a trap/inform
over tcp/ssh/whatever and then just reuse the connection
for subsequent pdu's sort of akin to http 1.1 reuse. It
would just all sort of fall out of the overall snmp
architecture.

		Mike

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