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

"Sumanth Channabasappa" <sumanth@cablelabs.com> Wed, 12 October 2005 15:19 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPiNw-0007wX-QT; Wed, 12 Oct 2005 11:19:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPiNw-0007wR-51 for call-home@megatron.ietf.org; Wed, 12 Oct 2005 11:19:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27783 for <call-home@ietf.org>; Wed, 12 Oct 2005 11:19:12 -0400 (EDT)
Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPiYE-0005ad-SU for call-home@ietf.org; Wed, 12 Oct 2005 11:29:57 -0400
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.13.4/8.13.4) with ESMTP id j9CFJ44n011758 for <call-home@ietf.org>; Wed, 12 Oct 2005 09:19:04 -0600 (MDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.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 09:19:04 -0600
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804FF20B0@srvxchg.cablelabs.com>
Thread-Topic: [Call-home] last call for a Call Home BoF
Thread-Index: AcXPNIeTj6BNQBd6Q5eCBgI5ab4SYgAC5eFA
From: "Sumanth Channabasappa" <sumanth@cablelabs.com>
To: <call-home@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: quoted-printable
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

Eliot,

I concur with the others as this is a problem space that needs to be
addressed. Personally, I would be interested in feedback related to the
management protocols (SNMP, netconf) in this regard.

- Sumanth
  

-----Original Message-----
From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com] 
Sent: Wednesday, October 12, 2005 7:53 AM
To: Eliot Lear
Cc: call-home@ietf.org
Subject: Re: [Call-home] last call for a Call Home BoF

Eliot,

I think it is important to discuss this problem space, as there are a
number of completely different approaches already being developed,
including STUN/ICE/whatever and IPsec with NAT-T.  Whether the proposed
approach is a good addition to the set is something that could clearly
be discussed in a BOF.

--Pekka NIkander

On Oct 12, 2005, at 10:12, Eliot Lear wrote:

> 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@ietf.org
> https://www1.ietf.org/mailman/listinfo/call-home
>
>


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


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