Re: [Call-home] draft minutes

Eliot Lear <lear@cisco.com> Mon, 21 November 2005 13:20 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeBaY-0000PE-Un; Mon, 21 Nov 2005 08:20:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeBaX-0000Oy-3j for call-home@megatron.ietf.org; Mon, 21 Nov 2005 08:20:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29402 for <call-home@ietf.org>; Mon, 21 Nov 2005 08:19:26 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EeBsy-0002gI-FF for call-home@ietf.org; Mon, 21 Nov 2005 08:39:09 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 21 Nov 2005 05:19:54 -0800
X-IronPort-AV: i="3.97,356,1125903600"; d="scan'208"; a="232774084:sNHT26769748"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jALDJsCJ018789; Mon, 21 Nov 2005 05:19:54 -0800 (PST)
Received: from [144.254.23.75] (dhcp-data-vlan10-23-75.cisco.com [144.254.23.75]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id jALDSG2K012932; Mon, 21 Nov 2005 05:28:16 -0800
Message-ID: <4381C978.6050307@cisco.com>
Date: Mon, 21 Nov 2005 14:19:52 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051025)
MIME-Version: 1.0
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: Re: [Call-home] draft minutes
References: <7D5D48D2CAA3D84C813F5B154F43B15506AD7844@nl0006exch001u.nl.lucent.com>
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15506AD7844@nl0006exch001u.nl.lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1119; t=1132579697; x=1133011897; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:Re=3A=20[Call-home]=20draft=20minutes| From:Eliot=20Lear=20<lear@cisco.com>| Date:Mon,=2021=20Nov=202005=2014=3A19=3A52=20+0100| Content-Type:text/plain=3B=20charset=3DISO-8859-1| Content-Transfer-Encoding:7bit; b=lGLn+b/FJm661QWjYieXOh4wIF42l48rWtKVwmCd+7mtnwy/mdFkAMKyUmo74eAnT64wat+K bp+WvcMYkwU7a6S6fc9Ll2rudqBmnN232AeH9PNfIJo5Ph/IQS4c+yD80nvW/E0+9dHKv51OT+u NK375FVDqBdUr0yynKghISl4=
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: call-home@ietf.org
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

Thank you, Bert.  I'll fix the nits and use the help.  As to the comment
you made, your recollection matches mine, I think.

Wijnen, Bert (Bert) wrote:
> Eliot,
> 
> nits:
> - pls check for spelling errors.
> - You also made a few "duplicate words or sets of words"
> 
> help:
> - the gentleman from a cable company was Jean-Francois Mule
>   from cablelabs
> 
> My comment you recorded:
> 
>    Bert Wijnen:
>    SNMPv3 can send a coldstart trap, but this does not mean it addresses
>    the call home problem.
> 
> I was reacting to Keith's comment on "cold start" and the question of
> "who would initiate the session". 
> First, I think keith also brought up that an agent can send a "cold
> start" today and then the manager can start communicating with the agent.
> And with SSH such might not be possible/easy.
> 
> And so my comment was to make clear that if in the current SNMPv3 world,
> if an agent is behind a NAT, then it can send a (UDP) "cold start".
> But the Manager can still not setup a "connection" or "manage" the
> device behind the NAT, because it may still (certainly not after a
> while) be reachable from the manager. So my point is: it is not a
> new problem specific to SSH. I agree that SSH may add additional
> aspects to the problem.

Or subtract depending on how we handle session initiation.

I'll amend the minutes to include your comment, assuming no violent
objections.

Eliot

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