RE: [Call-home] draft now posted; BoF?

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Tue, 27 September 2005 11:54 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKE2U-00020y-DV; Tue, 27 Sep 2005 07:54:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKE2T-00020n-CM for call-home@megatron.ietf.org; Tue, 27 Sep 2005 07:54:25 -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 HAA01827 for <call-home@ietf.org>; Tue, 27 Sep 2005 07:54:24 -0400 (EDT)
Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKE9f-0002fj-Np for call-home@ietf.org; Tue, 27 Sep 2005 08:01:55 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j8RBsA6X012423; Tue, 27 Sep 2005 06:54:11 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <SQW8MZ4S>; Tue, 27 Sep 2005 13:54:10 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508234BDF@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Eliot Lear <lear@cisco.com>, call-home@ietf.org
Subject: RE: [Call-home] draft now posted; BoF?
Date: Tue, 27 Sep 2005 13:54:09 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc:
X-BeenThere: call-home@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion of issues relating to &quot; call home&quot; functionality and firewall traversal" <call-home.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/call-home>, <mailto:call-home-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/call-home>
List-Post: <mailto:call-home@ietf.org>
List-Help: <mailto:call-home-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/call-home>, <mailto:call-home-request@ietf.org?subject=subscribe>
Sender: call-home-bounces@ietf.org
Errors-To: call-home-bounces@ietf.org

Eliot, in your draft I see (sect 1):

   All of this leads us to the conclusion that a flexible means for
   management applications to traverse firewalls is a useful approach in
   the face of devices that intercept unacknowledged SYNS or keep
   translation tables based on connection state.

Mmmm... "is a useful approach..."
Sure... but is it something that is really needed?
That is what I want to hear support for.

Further I see (sect 3):

   Call Home is useful for devices that do not retain a stable
   accessible point within a network.  For instance, a lap top or a
   wireless phone may move from one location to another, and yet it
   still is be desirable for that device to be managed when it is
   online.  Imagine what would be necessary in order to manage such a
   device by having the manager contact it:

I find your examples weak. I am not aware of wide-use of SNMP to
manage/monitor laptops or wireless phones. If others are, then
please let me/us know about that.
So I'd prefer you would use examples where we know that SNMP is
being used (or would be used if CH was/is available).

Bert

_______________________________________________
Call-home mailing list
Call-home@ietf.org
https://www1.ietf.org/mailman/listinfo/call-home