[Call-home] Call Home BoF @ IETF 64

Eliot Lear <lear@cisco.com> Mon, 31 October 2005 16:20 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWcOE-0004FH-Gm; Mon, 31 Oct 2005 11:20:06 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWcOC-0004ER-KQ; Mon, 31 Oct 2005 11:20:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18157; Mon, 31 Oct 2005 11:19:44 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWccM-0004v8-TP; Mon, 31 Oct 2005 11:34:46 -0500
Received: from sj-core-5.cisco.com ([]) by sj-iport-3.cisco.com with ESMTP; 31 Oct 2005 08:19:52 -0800
X-IronPort-AV: i="3.97,270,1125903600"; d="scan'208"; a="358935399:sNHT26591902"
Received: from imail.cisco.com (imail.cisco.com []) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j9VGJn94010211; Mon, 31 Oct 2005 08:19:50 -0800 (PST)
Received: from [] (ams-clip-vpn-dhcp4447.cisco.com []) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j9VGTSP9020636; Mon, 31 Oct 2005 08:29:29 -0800
Message-ID: <43664424.6020406@cisco.com>
Date: Mon, 31 Oct 2005 17:19:48 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.4.1 (Macintosh/20051006)
MIME-Version: 1.0
To: call-home@ietf.org, ietf-announce@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1853; t=1130776170; x=1131208370; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:Call=20Home=20BoF=20@=20IETF=2064| From:Eliot=20Lear=20<lear@cisco.com>| Date:Mon,=2031=20Oct=202005=2017=3A19=3A48=20+0100| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=Hr6HyBxDciWTIwceQCddNZFTEynZEqNhl7r65mta6N/yhLJUEcZZ/X1ByhrGt4+QH/vTTpGl mpDQT/pCzcX5qnCB2CAwAPzJaThqjOHTe1i7P0bA7d0tsGeB07fXpf8WqeCkI5WLHSdro3SLST7 yTG2M+/mYwxp6qL6Ii1UcYBY=
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Subject: [Call-home] Call Home BoF @ IETF 64
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 much deliberation and some discussion there will be a Call Home 
BoF at next week's IETF.  Here is the proposed agenda.  If you wish to 
discuss the topic, please feel free to join the mailing list, which is 
call-home@ietf.org.  To subscribe follow this URL:


Here is the proposed agenda for next week's meeting:

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-03.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

We will also look at other existing work in this space including ICE,
STUN, and generic tunneling approaches.

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.

Agenda bashing - 1 minute
Applicability, solution methods, examples (Eliot Lear) 15 minutes
Generic Architectural Approaches, ICE, STUN, MIDCOM (Jonathan Rosenberg) 
10 min
General Architectural Approaches to tunneling (Pekka Nikander) 10 min
Application to SNMP and open areas - 10 min
Discussion including architectural issues - 10 minutes
Moving Forward Options  - 5 minutes

(The astute will note we plan to run over by 1 minute).


Call-home mailing list