[Call-home] bof at vancouver?

Eliot Lear <lear@cisco.com> Sun, 09 October 2005 09:59 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOXyD-0002nA-0u; Sun, 09 Oct 2005 05:59:53 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOXyB-0002jm-D7 for call-home@megatron.ietf.org; Sun, 09 Oct 2005 05:59:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06199 for <call-home@ietf.org>; Sun, 9 Oct 2005 05:59:49 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOY7q-0006b6-Fr for call-home@ietf.org; Sun, 09 Oct 2005 06:09:51 -0400
Received: from sj-core-3.cisco.com ([]) by sj-iport-5.cisco.com with ESMTP; 09 Oct 2005 02:59:38 -0700
X-IronPort-AV: i="3.97,190,1125903600"; d="scan'208"; a="218433348:sNHT28663868"
Received: from imail.cisco.com (imail.cisco.com []) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j999xXVt003810 for <call-home@ietf.org>; Sun, 9 Oct 2005 02:59:33 -0700 (PDT)
Received: from [] (ams-clip-vpn-dhcp61.cisco.com []) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j99AAcl6020982 for <call-home@ietf.org>; Sun, 9 Oct 2005 03:10:39 -0700
Message-ID: <4348EA06.6080900@cisco.com>
Date: Sun, 09 Oct 2005 11:59:34 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 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=1776; t=1128852639; x=1129284839; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:bof=20at=20vancouver?| From:Eliot=20Lear=20<lear@cisco.com>| Date:Sun,=2009=20Oct=202005=2011=3A59=3A34=20+0200| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=V488IWI9UhBAczND9Ua9asXYbAFZ9ORpqc8qTrY6MhPIy9mIYWKVUz+9SRHDR7XQv8fLssuy FmyxuHMj1+byqfCsyJ2X6lCbRXlbKmWSYB5xrIGR3953IgYp2Rg1kDMBeaVfH36QaB2rcRwo7Hc 96VT1lC10B/kumVsFQLjmXa8=
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: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Subject: [Call-home] bof at vancouver?
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


Could you signify your interest in a BoF at VC?  I've placed a request 
with Bert, and he would like to understand whether there is interest.

Here is a draft agenda.  We're looking for another chair as I believe I 
would end up presenting.


Request for a BoF:

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