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

"Romascanu, Dan \(Dan\)" <> Wed, 12 October 2005 08:58 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1EPcRT-0000Om-6z; Wed, 12 Oct 2005 04:58:31 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1EPcRR-0000OI-Lt for; Wed, 12 Oct 2005 04:58:29 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id EAA08138 for <>; Wed, 12 Oct 2005 04:58:26 -0400 (EDT)
Received: from ([]) by with esmtp (Exim 4.43) id 1EPcbi-0003Tx-49 for; Wed, 12 Oct 2005 05:09:07 -0400
Received: from (localhost []) by (Switch-3.1.2/Switch-3.1.0) with ESMTP id j9C8teGO016233 for <>; Wed, 12 Oct 2005 04:55:40 -0400 (EDT)
Received: from ( []) by (Switch-3.1.2/Switch-3.1.0) with ESMTP id j9C8tcGO016194 for <>; Wed, 12 Oct 2005 04:55:38 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Call-home] last call for a Call Home BoF
Date: Wed, 12 Oct 2005 10:58:22 +0200
Message-ID: <>
Thread-Topic: [Call-home] last call for a Call Home BoF
Thread-Index: AcXPBOepqi0u5P7YSVOU7Nqax/hPcgABJVCQ
From: "Romascanu, Dan \(Dan\)" <>
To: "Eliot Lear" <>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: quoted-printable
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion of issues relating to &quot; call home&quot; functionality and firewall traversal" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

I believe that the problem that this BOF tries to deal with is very
real, has architecture and deployment implications, and it would be very
useful to have this BOF at the Vancouver IETF. 

BTW, the first phrase in the long description is broken and fuzzy in not
showing who is the client. It would be useful to re-write it, and maybe
include also the explication in the I-D about what is 'call home' (  '
Many devices make use of so-called "Call Home" functionality in order to
be managed or updated, or to otherwise establish outbound
communication in the face of NATs, firewalls, and mobility.') 



> -----Original Message-----
> From: 
> [] On Behalf Of Eliot Lear
> Sent: Wednesday, October 12, 2005 10:13 AM
> To: "ops- nm";;
> Subject: [Call-home] last call for a Call Home BoF
> 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.
> Eliot
> 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:
> 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

Call-home mailing list