[Call-home] coming to a drafts directory near you...

Eliot Lear <lear@cisco.com> Mon, 03 October 2005 08:50 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMM2F-0001bs-5q; Mon, 03 Oct 2005 04:50:59 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMM2D-0001bn-8c for call-home@megatron.ietf.org; Mon, 03 Oct 2005 04:50:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12869 for <call-home@ietf.org>; Mon, 3 Oct 2005 04:50:55 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMMAd-00009Q-TH for call-home@ietf.org; Mon, 03 Oct 2005 04:59:41 -0400
Received: from sj-core-5.cisco.com ([]) by sj-iport-5.cisco.com with ESMTP; 03 Oct 2005 01:50:47 -0700
X-IronPort-AV: i="3.97,166,1125903600"; d="scan'208"; a="216508529:sNHT24221362"
Received: from imail.cisco.com (imail.cisco.com []) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j938oj4V012666 for <call-home@ietf.org>; Mon, 3 Oct 2005 01:50:45 -0700 (PDT)
Received: from [] (rtp-vpn1-91.cisco.com []) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j9392947001375 for <call-home@ietf.org>; Mon, 3 Oct 2005 02:02:10 -0700
Message-ID: <4340F0E4.3080708@cisco.com>
Date: Mon, 03 Oct 2005 10:50:44 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.4 (Macintosh/20050908)
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=478; t=1128330130; x=1128762330; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:coming=20to=20a=20drafts=20directory=20near=20you...| From:Eliot=20Lear=20<lear@cisco.com>| Date:Mon,=2003=20Oct=202005=2010=3A50=3A44=20+0200| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=Fvj43NjYBx3YWkzat1o8AWSHXeTjj3TLT1ZnOgNPBXT7BjUHOmqqoabVjmmYKl4HX5d0JJ9M ougfgYdN75Ia4pxup/nn2ZAA67TTS6Bj1JhRDUWxHtTKPfrhQy46xMAR2MwwlxD4Vc9V5QFcGph j1Rhz3v4LsE55nYcr4gX/RKg=
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: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: [Call-home] coming to a drafts directory near you...
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


I've attempted to better describe when CH is useful and when it's not. 
I've also added some additional examples.  I wonder if people would like 
to comment on the following:

  - call home is there already for naturally p2p unicast protocols
    such as BGP and file sharing.
  - call home requires some sort of protocol operation in client /
    server cases
  - from a non-session or atomic transaction standpoint call home's
    applicability is limited if there at all.  Same for multicast.

See the draft for details when it comes out.



Call-home mailing list