Re: ISMS working group

Ken Arnold <arnold@moonhill.org> Thu, 08 September 2005 15:51 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDOgV-0005XG-70; Thu, 08 Sep 2005 11:51:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED5cD-00066U-FZ; Wed, 07 Sep 2005 15:29: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 PAA11616; Wed, 7 Sep 2005 15:29:47 -0400 (EDT)
Received: from out4.smtp.messagingengine.com ([66.111.4.28]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED5fQ-00080R-Sf; Wed, 07 Sep 2005 15:33:10 -0400
Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 5BE5BCCF555; Wed, 7 Sep 2005 15:29:37 -0400 (EDT)
Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend1.internal (MEProxy); Wed, 07 Sep 2005 15:29:37 -0400
X-Sasl-enc: Xd0avxJC4ifP0dLNGy6o77Zlb5CtKlgsX0QqNQBP0rUR 1126121377
Received: from [192.168.1.103] (209-6-251-216.c3-0.lex-ubr2.sbo-lex.ma.cable.rcn.com [209.6.251.216]) by frontend3.messagingengine.com (Postfix) with ESMTP id 1D23A1DC; Wed, 7 Sep 2005 15:29:36 -0400 (EDT)
In-Reply-To: <p0620074bbf44d3d23a6d@[192.168.2.7]>
References: <431DD59A.4000400@ofcourseimright.com> <AE6514F0-4714-4A48-9F56-A155823489F2@moonhill.org> <p0620074bbf44d3d23a6d@[192.168.2.7]>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <3282F4B9-93F4-43ED-BD5E-B0D26E20968F@moonhill.org>
Content-Transfer-Encoding: 7bit
From: Ken Arnold <arnold@moonhill.org>
Date: Wed, 07 Sep 2005 15:29:35 -0400
To: Margaret Wasserman <margaret@thingmagic.com>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 08 Sep 2005 11:51:23 -0400
Cc: Eliot Lear <lear@ofcourseimright.com>, iesg@ietf.org, ietf@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

On Sep 7, 2005, at 1:44 PM, Margaret Wasserman wrote:

> The call home solution doesn't help with the problem of the  
> _manager_ being behind a NAT.  It only applies to situations where  
> the manager is at a fixed location on a globally-addressable  
> network and the managed device is behind a NAT or firewall.

Thanks, Margaret.  I know that some think CH is good and some think  
it isn't, etc.  I'm not taking a stand on that, I'm just saying that  
the standard needs to *handle* these cases.  I actually have no horse  
in that race; I'm sitting at the "deliver SNMP solutions for our  
products to the customer" end of the world, and I want the standard  
-- whatever it is -- to work in these cases.  If CH is a partial  
solution that needs augmenting with another approach, itself also  
incomplete, fine.  If the best that can be done, no matter what  
protocol is defined, is to handle the case you describe, well, nobody  
can do the theoretically impossible and it will have to do.  At least  
it's an important case in this world, and better to include it than not.

But honestly, I didn't mention Call Home or any other approach in my  
letter.  I'm implementation-neutral on the subject.  I'm solution- 
centric -- I want the problems addressed so they are solved.

         Ken

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