[Call-home] last call for a Call Home BoF

Eliot Lear <lear@cisco.com> Wed, 12 October 2005 08:13 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPbjg-00037A-4z; Wed, 12 Oct 2005 04:13:16 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPbjd-00036k-4U; Wed, 12 Oct 2005 04:13:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04583; Wed, 12 Oct 2005 04:13:10 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPbts-0001xP-2R; Wed, 12 Oct 2005 04:23:50 -0400
Received: from sj-core-1.cisco.com ([]) by sj-iport-1.cisco.com with ESMTP; 12 Oct 2005 01:13:01 -0700
X-IronPort-AV: i="3.97,205,1125903600"; d="scan'208"; a="665368836:sNHT25667928"
Received: from imail.cisco.com (imail.cisco.com []) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j9C8Cwub016879; Wed, 12 Oct 2005 01:12:59 -0700 (PDT)
Received: from [] (ams-clip-vpn-dhcp148.cisco.com []) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j9C8Nop3016722; Wed, 12 Oct 2005 01:23:50 -0700
Message-ID: <434CC589.2020608@cisco.com>
Date: Wed, 12 Oct 2005 10:12:57 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.4.1 (Macintosh/20051006)
MIME-Version: 1.0
To: "ops- nm"@ops.ietf.org, isms@ietf.org, call-home@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1932; t=1129105431; x=1129537631; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:last=20call=20for=20a=20Call=20Home=20BoF| From:Eliot=20Lear=20<lear@cisco.com>| Date:Wed,=2012=20Oct=202005=2010=3A12=3A57=20+0200| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=HMPtSMIPPWVMgx4ahNPbMftO4YsS9yKsA+ZDiZlJdx6RwtaI9Wj9b0d5wYdqMod6ePUVuPSZ fEFQeNuTzrCdYdnjaWs/kB8vmIchiBtdSut4JDaWphIT26DiRmcq2TrBoKslZ24lK5uGrizhU9d 1PBWHqy4yWKP9xtBUbsBCR9E=
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Subject: [Call-home] last call for a Call Home BoF
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

After all of the mail last month, Bert is considering allowing a BoF on 
the topic of Call Home.  I initially posted a note to the call-home 
mailing list announcing the possibility of a BoF.  Response to that note 
was - well - underwhelming.  If you are interested in seeing one, could 
you please reply to this email, CCing the call-home mailing list.  Here 
is a draft agenda.  It is subject to your input.

If we do not see much input, I'm going to drop the request to Bert.


Title: callhome
Period of time: 1 hour
Area: ops-nm
Expected # attendees: 40-60 (small room)
Don't conflict with: ISMS, ops-area, netconf (if there is one)

Short Description: Discussion of Architectural Issues Concerning
            protocols that could benefit from reversing
            of roles

Long Description:

Certain protocols, and in particular management protocols where
devices on either end of connection take client server roles may
be able to take advantage of "Call Home" functionality, when
traditional roles are reversed, and a server connect to a client.
Examples of existing protocols that make use of call home include
SMTP [ETRN] and COPS.  At this BoF we will look at extending such
functionality into other protocols, as well as any architectural
issues this raises.

This work stems from efforts in ISMS to extend SNMP to run over SSH,
as well as work as work that has gone on in NETCONF.

We will begin with a discussion of 
draft-lear-callhome-description-0[1,2].txt, which contains a description 
of call home, what problems it can solve, and what some of the 
architectural issues are.  During the BoF we may identify additional 
such issues as well as protocols other than management protocols that 
could benefit from this work.  An additional potential question should 
be whether a generic standard or process should be used to implement 
call home, such as rules for SSH.

There are three possible outcomes: a working group to add "call home"
functionality to existing protocols such as SNMP/SSH and NETCONF/SSH,
use of existing working groups for this purpose, or nothing.

Chair: Eliot Lear (or tbd)

Agenda bashing - 1 minute
Presentation of draft-lear-callhome-description-00.txt 19 minutes
Application to SNMP and open areas - 10 minutes
Discussion including architectural issues - 20 minutes
Moving Forward Options  - 10 minutes

Call-home mailing list